• 6 Posts
  • 116 Comments
Joined 1 month ago
cake
Cake day: November 10th, 2025

help-circle
  • My understanding is that the content is essentially self-hosted, so content removed from relays still exists on the posting user’s client and can be accessed directly, just like a website sending out RSS. So saying it “still exist on the network” is technically true, but only in the same way that you would say that about say bittorrent or the open web. What people host/post is present raw, what is amplified/“curated”/relayed is filtered. Client settings/config sets default and custom user content interaction, like a browser which can have adblock or not.

    In principle, this seems like a decent solution, but I can see why different users prefer different protocols, differing to moderation takes a burden off of the user to vet inbound content. The same can be achieved via relays but the culture of “curation” seems weaker because the pressure from the userbase is lower to optimize it, as users are not solely reliant on any one relays. An odd network effect, but a truly invested curation/admin team could just as easily build a well “curated” relay as a well moderated instance.






  • Client-side curation sounds like whitelisting effectively, if you follow only the curated feed and the curated feed resigns all events posted by selected keys, that’s a whitelist and seems like a decent solution for casual users so long as they can find trusted curators and clients that enable them to be easily discovered and subscribed to. What client is best for this currently?

    On the flipside, if those “curators” were able to export and import lists of keys to automatically exclude from feeds, that would be very useful for the curators who have to manually or automatically sort events and new users to build their feeds. Is that feature currently available? Eliminating known bot accounts from feeds seems like minimum viable feature set for new curators in the current state of play.





  • The question is why is this the case? The simple answer is p2p solutions struggle with asynchronous communications due to variable uptime of consumer devices. That said, that can be overcome by various means.

    Establishing a user base for any communications platform is a challenge, largely adoption is driven by user experience and project narrative. There is no reason a p2p project couldn’t meet these criteria, they have before many times for file-sharing.

    In fact, I think a self-hosted cloud storage solution with a communications platform built on it could be a great way to get a network of this type established. I know various file-sharing platforms like Soulseek have had these features, but I wonder if you slapped a WhatsApp clone UI onto it and push it as “own and share your files securely, no one you don’t specifically share the file with ever holds the files” if that wouldn’t pick up some steam.












  • DEX is actually pretty good when used with a keyboard and external monitor. I also dont love thr Samsung walled garden, but I end up buying their products because I use my phones for several years at a time before replacing them so top end hardware specs are a priority and especially cameras.

    I would go Sony but the data band support in the US is incomplete, and I can’t get caught out by poor cell service while traveling.

    I am considering going Pixel next but Graphene hasn’t been announced for Pixel 10 yet so I’m a bit on the fence, I guess I could buy an older model and give it a try wifi only for a bit to see how I like it.