Professional software developer and all-around geek in Seattle.

  • 0 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle


  • 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.



  • Yes, they will continue to coexist for the foreseeable future. There’s a reason why people choose one or the other since they each have their pros and cons, and the fact that they do federate with each other (even if it can be buggy at times) means people will continue to be able to pick whichever one they prefer without having to lose out on most content from the other.

    As for your experiences with federating, you do need to make sure federation is getting triggered. For instance, I created a magazine on kbin.social a few days ago but it was taking forever to show up on lemmy.world (I have accounts on both). I had to specifically search for the magazine URL in the lemmy.world community search before it triggered federating that magazine and created the mirrored community on lemmy. Once I did that, it showed up just fine. From what I’ve seen, federation of new communities/magazines doesn’t happen automatically. It only occurs if someone specifically searches for it by URL in the other software. Hopefully that’s a bug and will be fixed at some point.









  • 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.






  • Yep, you’re absolutely right. I think my main point is that switching to only offering a cloud-streamed OS as their only offering would kill off a massive market where they have market dominance (enterprise desktops). It doesn’t make business sense for them to leave that market. If the demands of that market change, then you’re right – they’re going to do whatever is most profitable. But we’re nowhere near there yet.


  • Perhaps I’ve just read too many Microsoft business documents (I used to work for them years ago), but that’s not how I interpret that slide. It looks more to me like they want to “cloud-ify” functionality that could be used either from a desktop install or from a cloud streamed version. The key phrase in that slide to me is “Use the power of the cloud and client to enable improved AI-powered services and full roaming of people’s digital experience”.

    That kind of fits with what they’ve been doing by moving Windows login to use a Microsoft Account by default (which I hate, btw – I’m one of those local account people), as well as integration of OneDrive as default file save location. It’s the same kind of thing Apple’s been doing with macOS for the past few years, adding iCloud integration with everything. If you move that functionality for desktop installs to mostly be cloud-based, it also allows you to create a more viable cloud-only offering. But it doesn’t mean there’s a reason to stop selling a desktop-installable version.

    Microsoft is still a business, and they’d lose a ton of market-share by killing off desktop installs, especially in the enterprise sector, which is their bread and butter. They’re looking to expand into other markets, not kill off large existing ones.


  • Many people don’t quite grasp the concept of the fediverse or different instances, and just landed somewhere after following an article or guide talking about Reddit replacements. We shouldn’t be surprised that such people interact with their instance like it was a monolithic Reddit alternative.