Comment

Comment on Unified Fediverse App - a browser solution?

I've seen this ask come up a number of times now -- and to a certain extent, the Piefed and Mbin frontends do kinda to it already in that you can have your microblog and threaded content in the same UI. But before taking that further with pixelfed/loops integration as well, ask whether it's really a good idea. There's a reason why Twitter, Facebook, and Reddit are separate sites, and why none have tried to implement the UI or feature set of the other. I would make the case that the fediverse would really benefit from a portable user IDs auth system that could be used between different services or instances (which Nostr kinda does, and there are other zero-knowledge proof-based services that could be integrated), but with regard to content display and just interacting with content, having 3 different tabs open with the 3 different kinds of content/conversations just makes a lot more sense to me.

source

Sort:hotnew top

rglullis@communick.news ⁨1⁩ ⁨day⁩ ago

There’s a reason why Twitter, Facebook, and Reddit are separate sites, and why none have tried to implement the UI or feature set of the other.

Yes, the reason is that corporations can not profit from an unsiloed web of data, so they all created their own walled gardens and successfully fooled users into believing that the UI needs to be tightly coupled with the data they host.

having 3 different tabs open with the 3 different kinds of content/conversations just makes a lot more sense to me.

What would be stopping us from having these tabs using the same data from the social graph?

source
- Coopr8@kbin.earth ⁨15⁩ ⁨hours⁩ 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.
  
  source
  - artifex@piefed.social ⁨15⁩ ⁨hours⁩ ago
    Maybe a browser plugin/extension would be better in your case then? That would actually probably be not too hard to vibe-code if you're so inclined.
    
    source
    Coopr8@kbin.earth ⁨13⁩ ⁨hours⁩ ago
    Yes, basically a browser plugin and a skin would do it. Someone just commented that push notifications at the desktop level handle this for them, and that was an aha moment. The extension could just be a push notification log woth the ability to filter for a group of designated sources.
    
    source
Coopr8@kbin.earth ⁨1⁩ ⁨day⁩ ago
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?

source