I don't think people here realized yet how much development has sped up in the "atmosphere*"
-
I don't think people here realized yet how much development has sped up in the "atmosphere*"
I fear for the future of the fediverse if we don't get our shit together in some key areas. The way the lexicon system over there allows interoperability between distinct types of data and interface is really showing now that the developer ecosystem is picking up.
*The network comprised of different stuff that uses AT Proto
@liaizon Yep, said pretty much the same thing the other day.
To me, the one key feature we need is the ability to disable replies, and maybe also control who can reply, those are top 1 and 10 requests on Mastodon's GitHub, and both have been open for several years.
The team's response: it's too hard. Which, fair enough. But putting any effort into UX/UI polishing, as needed as that is, will be wasted as so many people already left because of the constant harassment and gatekeeping.
I also pointed out that by the time Bluesky's VC money runs out, there might already be enough independent communities running the full ATProto stack, so people will just be able to migrate without needing to ever look at the fediverse again.
-
@liaizon Yep, said pretty much the same thing the other day.
To me, the one key feature we need is the ability to disable replies, and maybe also control who can reply, those are top 1 and 10 requests on Mastodon's GitHub, and both have been open for several years.
The team's response: it's too hard. Which, fair enough. But putting any effort into UX/UI polishing, as needed as that is, will be wasted as so many people already left because of the constant harassment and gatekeeping.
I also pointed out that by the time Bluesky's VC money runs out, there might already be enough independent communities running the full ATProto stack, so people will just be able to migrate without needing to ever look at the fediverse again.
@liaizon We've really fumbled the big Twitter/X migration, and just learned nothing.
-
@liaizon Yep, said pretty much the same thing the other day.
To me, the one key feature we need is the ability to disable replies, and maybe also control who can reply, those are top 1 and 10 requests on Mastodon's GitHub, and both have been open for several years.
The team's response: it's too hard. Which, fair enough. But putting any effort into UX/UI polishing, as needed as that is, will be wasted as so many people already left because of the constant harassment and gatekeeping.
I also pointed out that by the time Bluesky's VC money runs out, there might already be enough independent communities running the full ATProto stack, so people will just be able to migrate without needing to ever look at the fediverse again.
@stefan another place where WAFRN and GoToSocial leading the way with close to zero funding
-
@ruben I agree with this synopsis
@liaizon @ruben I think fediverse could still become mainstream, but clearly not through Mastodon.
I had pretty high hopes when Tumblr originally announced integrating ActivityPub, of course that's not happening anymore.
Less so with Meta's Threads, given the company's history.
Flipboard and Ghost are still putting in the effort, which is great, but those are not platforms used by regular social media users.
We really just need a new fediverse platform that's user-friendly. Seems like that's nearly impossible without VC money though, so I don't know.
-
@stefan another place where WAFRN and GoToSocial leading the way with close to zero funding
@liaizon Yeah, if I had the time and resources, I'd set up a server with GoToSocial and a Phanpy frontend, gave it a cool modern name, and try to lure in normies, without advertising the whole federation thing too much, just as an added bonus.
Alas, I really don't want to deal with content moderation.
-
@stefan another place where WAFRN and GoToSocial leading the way with close to zero funding
-
@liaizon Yeah, if I had the time and resources, I'd set up a server with GoToSocial and a Phanpy frontend, gave it a cool modern name, and try to lure in normies, without advertising the whole federation thing too much, just as an added bonus.
Alas, I really don't want to deal with content moderation.
@stefan same same 100%
-
Shout out to WAFRN (@admin) and @anewsocial for taking the uncomfortable position of straddling the space inbetween protocols. I think this is truly the strategy that is going to be needed if we want to "win" the push towards an open social web for the whole internet.
Thank you for pointing me to #warfn.
I'm looking for a programmable solution. My idea is, to create some kind of LinkedIn-alternative, where i can publish my resume, and post inquiries for new open jobs. I want it to work with both the fediverse, and at-proto. Even though I prefer the fediverse, I want to be visible in both.
Are you aware of any (preferred) Python-library, or framework, that would solve that? Or do I have to fiddle with multiple incompatible ones?
-
-
@dansup Really nice to see someone taking safety features seriously!
Do hidden comments federate? That is honestly a great feature to have, I only thought of this recently during a conversation around reply controls, as a potential way to deal with the delay caused by the roundtrips needed to verify if a reply can be posted.
(Presumably this works differently on Loops, definitely curious to learn more.)
-
Thank you for pointing me to #warfn.
I'm looking for a programmable solution. My idea is, to create some kind of LinkedIn-alternative, where i can publish my resume, and post inquiries for new open jobs. I want it to work with both the fediverse, and at-proto. Even though I prefer the fediverse, I want to be visible in both.
Are you aware of any (preferred) Python-library, or framework, that would solve that? Or do I have to fiddle with multiple incompatible ones?
@cdonat @admin @anewsocial if you want to start with a base thats already in the wild and working, WAFRN or Bridgy Fed are the only options today.
-
If the Pixelfed/Loops user wants to disable comments, and other software doesn't respect that, why would the Pixel/Loops user care about ghost threads/replies?
We're focused on providing better/safer experiences for our users, and if other platforms don't abide by that, okay, but I'm not sure it's as pressing of an issue as you think it is.
We will get this fixed with interactionPolicy, people love our platforms because we have supported this for years.
-
@dansup Really nice to see someone taking safety features seriously!
Do hidden comments federate? That is honestly a great feature to have, I only thought of this recently during a conversation around reply controls, as a potential way to deal with the delay caused by the roundtrips needed to verify if a reply can be posted.
(Presumably this works differently on Loops, definitely curious to learn more.)
@stefan @liaizon We don't yet federate the hidden state, but soon will.
If you have a Loops.video account, you can see this in action here (press Load more until you see the Show hidden comments button): https://loops.video/v/5YvxWOxcRa
(Hidden comments require auth, but I'm going to remove that limitation in the next update)
-
I don't think people here realized yet how much development has sped up in the "atmosphere*"
I fear for the future of the fediverse if we don't get our shit together in some key areas. The way the lexicon system over there allows interoperability between distinct types of data and interface is really showing now that the developer ecosystem is picking up.
*The network comprised of different stuff that uses AT Proto
@liaizon okay so what exactly do we need to have and why?
-
@stefan @liaizon We don't yet federate the hidden state, but soon will.
If you have a Loops.video account, you can see this in action here (press Load more until you see the Show hidden comments button): https://loops.video/v/5YvxWOxcRa
(Hidden comments require auth, but I'm going to remove that limitation in the next update)
-
@cdonat @admin @anewsocial if you want to start with a base thats already in the wild and working, WAFRN or Bridgy Fed are the only options today.
Thank you very much. Since I like Python more than TypeScript, Bridgy is probably the best starting point.
-
@liaizon okay so what exactly do we need to have and why?
@elexia have you explored how the lexicon system there works?
-
@elexia have you explored how the lexicon system there works?
@liaizon no. what could have possibly prompted me to do this? I don't use the thing.
-
I don't think people here realized yet how much development has sped up in the "atmosphere*"
I fear for the future of the fediverse if we don't get our shit together in some key areas. The way the lexicon system over there allows interoperability between distinct types of data and interface is really showing now that the developer ecosystem is picking up.
*The network comprised of different stuff that uses AT Proto
@liaizon If my understanding of things is correct, this seems like the kind of thing that could be accomplished in the fediverse using ActivityPub C2S. Which of course depends on C2S actually getting some use... but a more generic ActivityPub server with varying C2S frontends could get us there, I think
-
@liaizon we have always been able to do that. We are just strangled by mastodon dominance and what it accepts