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.
trynn
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).
My network mostly uses NPC and summon names from Final Fantasy XI, because I played that game for many, many years and can associate the personalities of those characters with specific roles the host needs to have. I've also considered using Pokemon names for similar reasons, and with over 1000 current Pokemon species it'd be hard to max out in a home environment.
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.
Just saw your edit and comments to others and something really doesn't make sense. "East Seattle near I-90" is basically either Mount Baker or Leschi. Both of those are primarily neighborhoods without much in the way of businesses and mostly comprised of houses rather than apartments. It's also a rather expensive area, since it's in central-Seattle and right on the lakefront. I have a hard time believing that there's a company in that part of town that's big enough to relocate a candidate. Did you perhaps mean the Eastside instead? That's a very different thing. The Eastside is everything east of Lake Washington and is outside of the Seattle city limits. The Eastside near I-90 would be south-central Bellevue (Factoria and Eastgate area) and Issaquah. There are large companies and quite a lot of places to live near there. Recommendations for where to rent on the Eastside near I-90 will be very different than recommendations for where to rent in Central (or East) Seattle. The Seattle metro area is split in two by Lake Washington, and while it's possible to bike across the I-90 floating bridge (I have a coworker who does), it's probably not going to be done in less than 45 minutes and is probably going to be rather unpleasant for part of the year.
It really would be helpful if you gave us a better idea of where you'll be commuting to (like, the cross-streets, or the name of the neighborhood, or a nearby landmark, or the name of the company if you're willing to reveal that info -- lots of us in this area have worked for the major tech companies or have friends who have, and know where all their campus buildings are), as well as what your budget is. Budget is really crucial since rent varies a lot based on location. For instance, doing a quick search it looks like average rent in Factoria is about $1800 per month. Average rent in Lake Union (where Amazon is) is almost double that at about $3200 per month. And if you think even $1800/mo is expensive then I've got some bad news for you about your desire to not commute by car for longer than 1.5 hours.
Idk. I was told to avoid it, unless I like to hear gunshots.
People who say that tend to be people who don't ever visit Tacoma and don't know what they're talking about.
A counterpoint is this article that came out yesterday, listing Tacoma as the third-best place to live in the country (according to Bankrate.com): https://www.king5.com/article/news/local/tacoma/tacoma-named-best-places-live/281-53273688-2959-4ea0-ad45-46a48331084e
Every big city has crime. The Seattle metro area is safer than most.
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.
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.