I've always considered this an interesting discussion, sop I've written out a very thorough answer here: https://www.thepaperpilot.org/garden/guide-to-incrementals/defining-the-genre/
I don't hate apple. Especially from a privacy record, they actually have a far superior history than essentially every other hardware manufacturer out there.
I think they're overpriced and I don't agree with some of their design decisions, and in general feel like they could give the consumer more control over things, which is why I don't personally have an iPhone or iPad etc., I use them at work and have nothing against them in general)
Nostr does some interesting things! What I mentioned here is actually just the identity part of what I think could be a significantly improved version of the fediverse. I have ideas on how to support subreddit style communities and decentralized moderation and things like that that make the whole idea a bit different from nostr.
Yeah, I disagree with that part as well. I think it's fine for servers to store the content and provide endpoints for specific queries/sorts, and expecting the clients to have all the posts is a tad extreme.
In this case, yes the data needs to live somewhere, but that's the nature of having data be retrievable.
I agree with this take, and recently I actually read this article that criticizes how server centric fedi is as a whole. If it's hard and expensive for a layperson to self host, but you need to have an account associated with a specific server, then you're going to end up with a system where you're under the whims of a instance owner still. Not to mention the whole pick a server step severely hurts our adoption rates.
I like the idea of having an account just being a public and private key pair. Theoretically you could make one client side, use it to sign your messages, and servers could verify the signature and distribute your post without needing to have an explicit account for you. You could send every message to a random instance and it'd still work. You wouldn't have to worry about links to the "wrong instance" and you wouldn't have to attach your identity to a instance that might shut down or be bought by a bad person. The server would be essentially irrelevant.
For matrix specifically, I recommend fluffy chat on mobile and cinny for web/desktop. Most notably, they both support the not-yet-official spec on custom emojis and stickers, which I think is important for any slack-like.
For the server (since you want to self host), you'd probably want to do Synapse - it supports not being federated as well as SSO. Also it wasn't mentioned by mp3, but xmpp is another protocol that's used by many large companies for internal chat systems as well.
Honestly, these use cases all sound very cool, but I'm highly concerned about the idea of federating information that could effectively tie you to your physical location with a bunch of random servers. Even if all they see is a pseudonymous activitypub id.
To answer honestly, it's because the first sentence only uses common and easy to spell words.
I honestly think that philosophy is fine. Before the major social media sites all came about, the Internet was filled with much smaller communities that didn't need to be profitable or scalable - they could be run by an individual as a hobby project. I think returning to that (possibly with the use of federation so these small communities still have a good amount of content) could keep things free, ad free, and privacy conscious
view more: next ›
Glad the website could get you started on a whole rabbit hole of interesting reads 🫡