Nato Boram

There’s also lots of people who made an account in multiple instances before realizing that you don’t have to do that

Clients can work around it by making a search on the home instance that filters by community id and submitter id. Something like this.

You can’t have content addressing because it’s mutable. On the other hand, UUIDs are made for that. There’s even multiple types of UUIDs made for distributed computing with namespaces and such.

Amazing. One feature that is desperately needed on Lemmy is to open a post in another instance, not just a community or a user.

Well, that reminds me that Mastodon has huge, unresolved problems, such as tags being part of the post’s body like Twitter rather than being a separate field like Tumblr.

Reading tweets with a hundred hashtags at the bottom seem really thirsty for attention, which is bad because Mastodon wants to fundamentally work with these, yet doesn’t have good in-post integration for them. It makes interactions less genuine, more performative.

Rome wasn’t built in a day, and Mastodon won’t be good tomorrow either. In the meantime, you can vote to make it better on https://github.com/mastodon/mastodon/issues/10743.

Tumblr is a blogging experience that’s similar to Twitter, but more focused on the user itself than on the central feed.

• You have your blogs and you post there. Yes, you can have many blogs.
• There’s global feeds with posts from all users, potentially including yours.
• Posts can have non-intrusive hashtags, meaning they are not #partOfThePost, but in a separate, smaller, dedicated section of the post.
• You can’t post stuff to someone else’s blog, but you can comment on their posts. Comments are tiny next to the post.
• You can quote posts, but that makes a duplicate in a blockquote rather than linking to the original post like Twitter

Yep. And clients would be able to participate to the seeding.

Servers software developers would still have a massive amount of work to do to implement IPFS integration, but it’s doable. IPFS also has work to do here to make IPFS work natively with cloud storage protocols (like Amazon S3), but it already exists.

One issue with open source software is that you often have to pick the least-effort solution to avoid burning out your free labour. Free time is limited, and if IPFS takes slightly too much work to add, then it’s off the table.

From what I’ve heard, you pay by viewing ads. Those can be blocked at the DNS level, though.

Since we’re doing meaningless comparisons:

• uBlock Origin is FREE
• ReVanced is FREE
• Infinity is FREE
• Jerboa is FREE
• Wefwef is FREE
• Leanish is FREE
• Slide is FREE
• Thunder is FREE

Am I doing that right?

Yeah, it does tend to end up like that x)

I don’t remember Kbin having an API, so that might explain why