Skip Navigation

Posts
5
Comments
123
Joined
1 yr. ago

  • Yes, this is my point exactly. I want the 3 tabs, AND I want a unified inbox that opens those tabs when I interact with a relevant notification. Seems like there are some projects heading this direction.

    Ideally I dont want a new tab to open for every time I click on a different notification of the same type, just reuse the existing client tab that is open.

  • Remember the 4 H's, when someone is feeling upset they want one of four things from their listener, and asking up front "Which of the four Hs do you want right now" can really help get straight to supporting them.

    Hear - Just listen, dont comment or try to fix it. Brief supportive statements like "I hear you." and "That sounds eeally tough." welcome, but dont insert unrelated topics.

    Help - Give advice, including relating with a similar experience and specifically showing how it taught you something that applies to their situation.

    Hold - Usually just listening, but with the addition of physical touch, could be holding hands or full on cuddling.

    Hump (only for romantic partners) - cathartic release.

  • To take this further, a relateability sandwich really helps.

    Start with "I really relate to that because I had a similar experience." or similar

    end with "So I really sympathize with you, and I learned/still feel [insert summary of relevance to their situation]"

  • hmmmm interesting, a lot of this is news to me. I'll have to try and pull in some peertube accounts, I have never seen any posts showing them.

    I also admit I dont follow that many individual accounts, but I don't follow some and I've never seen a comment come through as a notification. I'll try following you and see if that changes.

  • Yes, we all want that for sure, and I'm definitely not convinced the ATProtocol solution is it.

    Ever hear of Solid by Tim Berners-Lee? It was an early approach to this single account for private data concept, seems like it might still be in development these many years later? https://solidproject.org/

  • I do use M.Bin, but I want Peertube, Pixelfed, Looped, etc. to feed notifications into my inbox, and I dont want the burden of development of that UI to fall on m.bin devs when they should probably just focus on continuing to optimize text content functions. Also I think it is totally possible someone will come out with something better than m.bin and it would be nice if that was just plug and play into my inbox rather than requiring a full migration.

  • I have two challenges to this take.

    Firstly, the theory that cross-propagation of media will lead to growth across multiple platforms starting with one as the "mainline" to recommend to new entrants heavily relies on Superusers who not only use multiple platforms for content discovery, but also then take the additional step to cross-post that media from one silo into the other, for example posting a peertube link into a miroblog post. For most people they will instead interact with the content in each silo, commenting on or favoriting the peertube post within the peertube client and leaving it at that.

    Secondly is the attention economy factor and platform inertia. Essentially social media platforms have successfully commodified/colonized a growing percentage of total attention hours for average users, and when interacting with content most users are passive consumers for a substantial percentage of the total content they are served. When entering a new platform, for it to serve as a viable alternative it must serve up an amount of content that allows them to both use the platform for an appreciable percentage of their total media consumption (otherwise the ratio of times checking the platform to reward for the check drops below acceptability) and provide them with a level of engagement that provides platform satisfaction, which typically starts close to where they were on average with the other platforms they use. Then you have this issue of content-fit which is a whole different issue to address, which we will leave aside for the most oart but it is worth pointing out majorly impacts the number of interactions a user puts in to the content as well as overall satisfaction.

    Unifying the inbox reduces one of the barriers to wider adoption by improving the ratio of number of times the platform is checked to the amount of content available for interaction, thereby making the fediverse a more likely source of overall content to be maintained in the user's set if options. Each platform individually will struggle with this until adoption passes a certain threshold. Each one individually feels "empty" to users when compared to their usual, which is a turn off for both consumers and creators, while in aggregate the picture is much better.

  • Awesome! Thanks!

  • Thanks, this is definitely the direction I was imagining, though it takes the tac of trying to be a primary browser with Fediverse features, rather than a Fediverse dedicated browser instance, so they will be forced to sacrifice UI streamlining for website-centric UI.

    What don't you like about the idea of you dont mind explaining?

  • Who said that? The browser still needs to be a browser in order to open links in posts. Similar to how Interstellar the client I'm using right now brings up a browser window when I click a link.

  • Yes, what I'm getting at is a way to create a notifications/inbox client that pulls from all the above stated API's but does not attempt to push any content to them, instead switching the user over to their preferred webclient when content interaction begins.

    Kind of like how an email client shows a title/headline, sender, and Metadata for each post but then expands a rich text / markup environment when you open the email. Or how some minimal RSS readers just pull headlines and a quick summary of each post but push you over to the original website when you click through to read the full post.

    I just want one place to see who has posted on what, and then use the front ends specialized for each piece of content to actually interact.

    I suppose there could be a side development to this, which would be the ability to associate accounts across multiple services and then filter only for them, for example if you know someone who posts on lemmy, Mastodon, peertube, Pixelfed, and loops, you could view all their posts of the day in one place. Or a team you are a part of. Anyway, once you can pull multiple services into one inbox the data sort potential is an obvious added benefit.

  • Aha, but you see my proposal specifically keeps the web clients for the specific content streams up to the user rather than baking them in. I like M.Bin so thats what I use for threads and microblogs, so thats what I would select as my service for that content within the browser.

    What I want is a unified inbox, with a move from each notification over to the webclient I choose to interact with the content. To be more specific I want a text-only inbox, but I want it to include headlines/captions/descriptions for multimedia content so I can have my Peertube, Pixelfed, Loops, Threads, Microblogs and whatever else all accessible from a single point of contact.

    I definitely agree on the portable account point, it always reminds me of Solid the private data project by Sir Tim Berners-Lee. Seems like ATProtocol may have been influenced by it?

  • Resisting them big plateau winds!

  • Meet my cousin Allonautilus scrobiculatus and his slimy shell.

  • Hello Fellow Kids

  • Looking great! I'd love to add this to my fedi-toolkit

  • Sounds a bit like Scuttlebutt

  • It is a "problem" if your goal is full ownership and control over your user interactions and data footprint. ATProtocol in principle achieves this, you can delete or move your account and all your user interactions will be deleted or follow you (meaning edit permissions, full access to all the posts/comments, follows, updoots, etc.). The cost of this is a very high data load for the host, though I'm still not clear on exactly why it is so much more data intensive, is it the size of lookup instructions between hosts in addition to the actual markdown?

  • [Edit: I see the problem, even with a self-hosted instance of 1, when you comment on posts in other instances that data is no longer held on your server, so you don't own it and can't control it directly, is that right?]

    So as I understand it the big "advantage" of ATProtocol is the account portability via DID, however this is at the sacrifice of actually hosting an ATProtocol being extremely data heavy.

    This has made me very curious about self-hosting ActivityPub (meaning an instance of 1 user), it would seem like focusing development on a client that makes it as close to as easy to self-host an instance as it is to join one would solve the issue of accountability portability, as you literally own all the data and rights when you self host. The Major challenge I see there is security, where experienced admins for larger instances should have some level of cybersecuroty expertise while the average use may have little to none. But then focusing group effort on auto-updating the client and the default settings of the client to maximize security would solve that issue it would seem?

    So what am I missing? Other than hosting costs, what else is deferring a self-hosted-first development approach for the Fediverse?

    Is it actually that AP development fundamentally believe moderation should be handled at the admin/instance level, and self-hosting makes moderation more difficult and less directly authority based?

    Publicly shared blacklists and whitelists would seem the natural fit for a self-hosted-first network, akin to adblock and horizontal.

  • Except Jaguars were actually an endemic species to the Everglades.