trynn

You're applying the political science definition of 'federation' and not the computer science definition. They are different. Federation in CompSci terms has to do with networking providers using standardization to interoperate, which is exactly what the fediverse does.

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.

High interest in something isn't the same as bubble. Where's the overvalued assets that are out of touch with reality? The guy quoted in the article even referenced Google losing value after the lackluster launch of Bard, which is kind of the opposite of a bubble. The dotcom bubble wasn't a bubble because everyone was talking about the Internet... it was a bubble because companies were severely overvalued for putting literally anything on the web without having functional business models. The businesses were the bubble, not the Internet.

Could AI become a bubble? Possibly. But we're nowhere near anything like that at this point in time. It's just got mindshare, not overvalued assets.

Some of us use our phones for work and letting other people have access to work content would violate NDAs.

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.

The super secret conference room is a maybe. Factories though? If you're going to be wiring up factory machines, you can easily just add one more cable for ethernet and it'd probably be cheaper and just as secure. We'd have to be talking about machines/devices that are in a large warehouse-like space and frequently moved around (thus requiring wireless networking) and that require either the security or bandwidth benefits of Li-Fi (most don't). That limits the applications significantly.

Kinda curious what the actual use cases for this are. It's not going to replace consumer wi-fi, since walls exist. And we already have light-based transmission within cables (fiber-optic networking). So, is this supposed to provide fast networking to locations where installing fiber isn't feasible? What's the effective range on this?

It’s the first change to the Office default font in more than 15 years.

Man, I remember the change to Calibri, and now I feel really old.

The easiest would be to unsubscribe from two of them. Or even better, if people could stop cross-posting.

Except cross-posting has a purpose. In that example, one of the posts was to beehaw while another was to lemmy.world. Beehaw defederated from lemmy.world so users on beehaw are only going to potentially see two of the three cross-posted posts. If they also defederate from lemmy.ml, those users would only see one.

So yeah, the solution is to unsubscribe from two of those communities because they're essentially 3 completely different groups that just happen to have the same name and general focus. Either that or just get used to it.