This has always been a flaky thing. Federation has worked in the past but not reliably. No idea why.
Looking into it now, it still seems incomplete. I compared bookstodon with my view on mastodon (hachyderm.io) and the view that kbin.social has.
All three were different. Yay decentralisation and federation!!
Mastodon has the most content, which makes sense, a.gup.pe is intended to work with mastodon and so they'd make sure that works. Both lemmy and kbin seem to be missing content, which also makes sense as they're much smaller than mastodon and don't get the same attention from a.gup.pe (Yay ... federation).
Kbin.social seems to have more content than lemmy. But it also renders it as a microblog ... which is not how I want groups to be structured (hence why I'm on the threadiverse/lemmy/kbin).
Lemmy's a.gup.pe feed being incomplete is likely a fundamental issue with how a.gup.pe structure their posts and lemmy not understanding that. I'm guessing Lemmy's rule of disallowing posting to multiple targets/communities is a big factor in this, as a.gup.pe posts are typically made by mastodon users who are likely to also tag other users, whereas lemmy, to prevent brigading, will only accept a community/group as the first address in a post (yay .... federation ....).
So while it's good seeing this liven up again ... it seems like someone needs to get into the weeds and sort this out from both sides.
Otherwise, and maybe I'm feeling particularly grumpy about the fediverse today ... this really is a great demonstration of how decentralised/federated social media can be ... just meh and a bit shit. It shouldn't be this hard to implement a standard structure for social media (groups/channels/sub-reddits) with an allegedly standardised protocol. In reality, it seems, the standard is rather ambiguous and flimsy to the point that every platform is idiosyncratic.
I say this just so that any one getting excited about possibilities doesn't get burnt out from incomprehensibly annoying disappointments. They are all around the place and can darken this place a bit.
But it's not surprising. Mastodon mainly sees the fediverse as a mastoverse with "other things attached" and gargron mainly sees mastodon as his personal project with "other people attached". It's a bit harsh, but there's enough truth to it, especially for an ecosystem/platform that has as its core ideology cooperative diversity and connectivity.
All of that being said, I think a good amount of blame falls to the protocol. With a good enough protocol and set of guarantees around what compliance with it entails, it shouldn't matter whether someone like gargron behaves in this way (where to be fair, he's built by far the biggest platform over many years now), as compliance with the "standard" protocol should preclude his ability to arbitrarily push things around like this.
But the protocol is very soft. And I think a time is coming, if it isn't here already, where the creators of the protocol are going to rue how much they've left up to developers like gargron who will suck the "standard" out of AcitivityPub. I say this may already have happened already because there are calls (which are very reasonable IMO) to take the mastodon API and basically make it a standard, not least because other platforms are adopting as a de facto standard already. And of course the biggest, sometimes desperate/emotional push back against this I've seen has been from one of the authors of the ActivityPub (evan, if you know them), because there's apparently something in ActivityPub that should be used instead but no body as really heard of and which I've heard is kinda crappy and vague (not unlike the rest of the standard perhaps?).
Bottom line is that ActivityPub needed gargron and mastodon to prove that something good could be made with it and they may regret the bed they've made. What ActivityPub should have done from the start is dedicate efforts to the creation of standardised software, at least for testing purposes, so that there was some sort of standard at the functioning software level for developers to work against. THere are efforts along those lines now, but it may turn out to be too late and one of those things every fediverse developer is "supposed" to use and contribute to but don't bother because they're too busy getting their platform/app to work with mastodon.
EDIT:
And on that note, an interesting project in the fediverse is vocata (https://codeberg.org/Vocata/vocata), because it tries to make the server as generic as possible and instead require the client (ie browser or mobile app) to make all the decisions.
My best bet is that there needs to be another platform that’s roughly as big and successful as mastodon so that there’s some balance. Preferably, that second platform should be more mindful of the importance of standards and inter operation.
Lemmy/kbin and other threadiverse alternatives have potential here, especially if they can themselves work well together and get as much synergy as possible from each others efforts.
Otherwise, all the people making alternative microblogging platforms should take the job more seriously and consider banding together into an organisation that really aims to provide a stable alternative. Currently Bonfire seems to have the most promise in this regard, and with out knowing too much about them, I wouldn’t be surprised if they’re a big deal in a year’s time, as there’s so much potential to show mastodon users that hats really possible on the fediverse outside of gargron’s influence.
At an even broader level, I hope BlueSky does well and shakes up the fediverse by showing what else can be done with a different approach. However centralised and corporatised BlueSky is relative to the fediverse, if BlueSky kinda eat the fediverse’s lunch, I think it will be mostly deserved for the simple reason that BlueSky appear to be putting UX as the first priority and decentralisation as the second. For social media, this seems like the correct approach if you want users that aren’t running Linux BTW^TM^.
Even more broadly, users having conversations about the general values they want from their platforms and speaking up about them with a willingness to use their feet when the time comes is probably a net good.
You're framing it as if this is a bad thing that Lemmy can only see some of the agupe content, but wait until you see how much content non federated platforms can see from each other! I really don't see how some content is worse than none, if you really want all of it then make an account over there like every other social network in the past requires you to browse on their site/app. It'll probably improve over time but it really sounds like you're upset that it already sometimes works instead of not at all.
Well sure, glass half full or half empty. To be clear, my problem isn't with either lemmy or a.gup.pe ... they're open source projects doing great things IMO, and I hope I've not made any of their devs upset.
My problem is with what seems to me --- as a mostly technically naive user that tries to pay attention to what others who know better are saying --- a tendancy on the part of the fediverse to not live up to its hype or promise, which, AFAICT, is attributable to the nature and design of the protocol and how federation works on the fediverse.
And sure, we can celebrate something half working ... there is, as you say, definitely something cool in seeing federation happen.
But there's a reality here that is too easy for open source projects to ignore ... user experience matters.
Unless you've got a great big sign on the app/platform that warns any user that this thing will not work at any random time (which OSS users implicitly understand but not everyone does) anytime the UX breaks in unexpected, uncontrollable and incomprehensible ways, a user has an upsetting experience. Sure, it's a bit of a first world problem, but the promise of social media is to connect socially with people, which involves an expressive and emotional behaviour. Moreover, people are drawn to the fediverse for emotional reasons: join the "good place", do the "right thing", help build a better internet etc.
The moment something unexpectedly breaks on someone as they're earnestly trying to reach out and make this place work for them, something rather frustrating and a little heart breaking happens.
In this case, there's something iffy about the protocol itself that things like this can "half work".
You ask whether it's better that it doesn't work at all ... and I'd say yea, probably. For the simple reason that to some user "half working" won't be discernible from "fully working", creating an expectation of functionality that will inevitably be disappointed. What happens when someone posts to the group and it doesn't get federated and they get no replies or interaction? They're gonna think there was something wrong with their post. If it happens a few more times, there's gonna be some psychological effect, however much we don't like to think about how emotionally bound we are to social media. What if they praise that a.gup.pe is on lemmy and tell everyone they should use it to only realise down the line that they've told people to try something that doesn't work well and feel embarrassed and frustrated that they've dedicated time, energy and their personal endorsement on something that's clearly got problems in the foundations? That's not a bitter experience that turns people off of caring about the fediverse? Why wasn't there someone warning everyone that the system wasn't working? Why allow something to only half work without telling anyone about it?
If this doesn't make sense to you ... I can assure you it happens ... people have gotten very upset over things just breaking down here. And part of the difficulty isn't that the system is inconvenient and hard to use ... it's that when it breaks it breaks in mysterious ways for the user, in ways that are undocumented, unknown and sometimes misconstrued and misrepresented by others.
I don't mean to demean the developers and their projects. But I do think broken things looking like working things is awful user experience, and that ActivityPub in the way that it seems to be a vague and very flexible protocol contributes to exactly these sorts of problems and should be criticised for it.
mmh, I thought this had been working for a relatively long time. I've been subscribed to some a.gup.pe groups for about a year now. For example this one: https://feddit.de/c/wuppertal@a.gup.pe
What exactly is new now?
People, think about the implications of a TLD before choosing your domain. Look up the organization that controls it and their restrictions on using it. Basic-ass research.
This headlines been out there for a week or so and every time I see it, seems like the taliban is after the admins or something. But it’s just about domain name.
Hey weren’t we having a problem with .ml? Did that ever get sorted?
That's not applicable. Sublinks is using the same standard as Lemmy/kbin/mbin, i.e. ActivityPub. In a decentralized system based on an open standard, plurality of implementations is a good thing. We shouldn't want lemmy to be the only one.
I mean, Java has faster developer speed since it's much less complicated than Rust. But it will also use a lot more memory. That being said, I guess most of what happens in Lemmy is database queries anyway and that will go equally fast in Java.
Rust is a very fast language but for a web app like Lemmy it's probably not that important that it's rust underneath.
But I really dislike Java. Lots of issues with code only working on a specific JDK, and code being very ugly due to all classes and shit.
Java has faster developer speed since it’s much less complicated than Rust
[citation needed]
To give some context: Exception-based error handling is insanely complex. The error handling of Rust is much simpler to reason about. Finding out where errors happen is a lot simpler.
The only Java dev I know is an older guy who started university with me at the same time - I was 20, he was 45. He knew Java, I didn't. Java is not the future if you ask me.
"faster to code in"... I would not say so. In my personal experience, Rust can be very fast to code in once you get comfortable with it, since you barely even need to run your code to know that it works. You also save a lot of time via less debugging.
Yeah this sounds like someone doesn't know rust and instead of learning it they're porting to Java? It might also be a way to capture an existing userbase as it's still compatible with lemmy, but also adds features that might cause more people to use it. But being written in Java is an excuse to make it more difficult to migrate the additions back upstream to lemmy. Maybe they hope that this will eventually allow them to build out a private platform?
Fediverse
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.