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

For anyone who has to install Windows 11; download the full ISO then use Rufus. You’ll be able to disable some of the enshittification.

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

Everyone should be able to do a hello world without IDE

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.

And also the importance of APIs. It’s the only reason why there’s so many Lemmy clients compared to Kbin.

Right? Like, my app is definitely not ready yet its source code is available for all to see. And since I’m currently inactive, you could even fork it and get a bigger following than me if you wanted to.

These people just think too highly of themselves.

No rationale provided.

Put your Git host’s runners on them and you now have free-ish CI minutes!

Yeah, the discovery process is shite on IPFS. You kinda have to cheat it to get it to work with something like .

Idk if it’s inefficient with large data, but it’s inefficient with compressed storage, as it does block-level deduplication, which is very cool.

There’s no shame in being a play-button corporate programmer who’s in it only for the money! In fact, most employers prefer this kind of people.

Even if we wanted to solve that problem, right now there is no way to cross-post on Lemmy. There’s a cross-post button, but it actually does a repost. I think we should think about that when Lemmy implements a cross-post feature in the first place.

“Other people” are what’s wrong with me. People don’t use linters/formatters/type annotations when it’s optional and produce dogshite code as a result. Having the compiler itself enforce some level of human decency is a godsend.

And I fucking love it. Thank you Go!

It only matters if you want to be able to use the commit tree and actually find something. Otherwise, there’s no harm in using merges.

Keeping communities separate is the simplest way to go, tbh. Sharing karma could lead to weird brigades, like r/ScreenshotsAreHard cross-posting from every picture of screens on the Fediverse and then mass-downvoting from there.

To me, the best solution would be to implement multireddits. That way, you can have your cat multilemmy of 100 communities without affecting your main feed, but you could also do the same for related or identical communities. Plus, moderators could create a multilemmy and display it prominently in their sidebar.

Being able to subscribe to a multi would solve that issue