trynn

What a dumb article. Sounds like an old C graybeard who’s never understood the point of proper type safety or readable code. None of the performance gains the author talks about actually matter, whereas the entire point of clean code is to make it easier to read and maintain by other programmers. Let’s also not forget this important quote from Donald Knuth: “premature optimization is the root of all evil”.

Simply put, unless you’re working in extremely resource-constrained systems, or have some code snippet being run an incredibly large number of times over a humongous amount of data, these kinds of performance optimizations simply don’t matter and you get more benefit from writing the code in a way that reduces bugs and is easier to read. Heck, most of the time compiler optimizations make this entire argument moot anyway.

This looks like a Lemmy issue, not a /kbin one. Perhaps find a Lemmy development community somewhere to ask.

The impractical/implausible reason is likely because different groups of people are writing the different fediverse software and have different opinions about how objects are identified in their software. ActivityPub already requires objects to have unique IDs, so this isn’t a protocol issue. But good luck getting every single developer for every single fediverse application to agree on one way to internally represent data in their apps. That’s just never going to happen for a variety of reasons.

Sounds like someone doesn’t understand what the fediverse is about.

It works from a Lemmy instance to see a /kbin magazine. It does not work the other way (from /kbin to see a Lemmy community).

Using !community notation is a Lemmy-only thing. Not everybody is reading this from Lemmy, and this particular community and the OP are both on /kbin. Providing direct URLs is a more generally useful way of linking to communities in the fediverse.

I don’t think this is a good idea. Keep in mind that different instances have different policies, moderators, and users. This leads to different rule enforcement, culture, and federation status. Even if a magazine/community has the same name and the same discussion topics does not mean it’s the same group of people reading those posts (some might be, due to cross-instance federation, but not all will be). In short, they are different groups and cannot be treated as the same without pissing off people.

The proper solution is to let each community just evolve until one naturally emerges over time as the go-to community or they all differentiate themselves enough to be considered different (albeit with similar names). Adding a bot to cross-post content just slows that process down and makes the problem persist for longer. If a topic is truly small enough that getting enough people for critical mass is difficult (like your DIY cobbling example), then it shouldn’t be hard to start a discussion in each of the separate communities to suggest assigning one as the “main” one and then just stop using the others. This is something that should be driven by the communities, not the software.

This article kind of misses the forest for the trees. While I agree with many of the author’s points, that’s not why the #TwitterMigration failed. It failed because Twitter/Mastodon isn’t really a social networking site, and Mastodon didn’t provide the same service that Twitter does. At its core, Twitter is about small numbers of (usually famous or important) users communicating with large audiences of followers. #TwitterMigration failed because not enough of those famous and important people moved from Twitter to Mastodon, so the average user had no content they cared to read. Seeing posts from your friends about what they had for dinner last night is all well and good, but the stuff people actually want to see is famous person A throwing shade at famous person B while famous person C talks about the new movie they’re in and important organization D posts a warning about severe weather in the area. You don’t go to Twitter to have discussions, you go to Twitter to get news and gossip direct from the source.

In contrast, sites like Reddit and kBin/Lemmy are about having group conversations around a topic. Interacting with famous people is neat but not the point. Think of Reddit/kBin/Lemmy as random conversations at a party whereas Twitter/Mastodon is some random person on the corner shouting to a crowd from a soapbox. #RedditMigration has a much better chance of succeeding simply because the purpose of the site is different. As long as enough people move to kBin/Lemmy to have meaningful conversations (aka content), it will have succeeded.