A little bit of computing and a little bit of neuroscience.
he/him/they
Lemmy federates pretty well with mastodon. From mastodon you can follow a community as you would any person/user.
There are two major problems though.
Also, you can just follow lemmy users on mastodon.
Some, maybe many, hope for the decentralised model of the fediverse to “take back the internet”. Each time a commercial platform “enshitifies“, there are then calls for the fediverse to replace it with a federated alternative, in part to take advantage of the moment of user agitation.
But, IMO, resources and financial support are a touchy topic in the fediverse. If such has lead to a mismatch between ambition and opportunity, and, capability, that may be worth addressing.
@weirdwriter @ajsadauskas @lemmyreader
Yes, forum platforms too (incl #nodebb of course).
I do get the (very vague) impression discourse is focusing on integrating well with masto to a good extent and so might not integrate too well with the other Reddit/forum platforms. If true, that might be a good enough reason to start with another base. OTOH, it’s a familiar platform to many devs so adapting it for stackoverflow like use could go well right?
Yep! It seems a good Threadiverse ecosystem could be on its way with lemmy etc, nodebb and discourse. Hooking a stack overflow alternative into that could make a lot of sense of kick starting it.
Though at some point UI differences could prove problematic(?)
Yep, yep and … yep!
Ha
AFAIU, two platforms other than mastodon (lemmy and discourse) have issues federating because at least one of them is trying federate well with mastodon (for obvious reasons). The mastodon quirk causing issues is, AFAIU, the way it kinda mangles articles and pages (long form formats in ActivityPub), which are appropriate for forums and link-aggregators like lemmy and discourse. So someone hints been done to work well with mastodon’s mangling, which hurts lemmy-discourse interop
Agreed (and said the same myself)!
As I’ve said it … alternative social has run its course in this post-musk-twitter moment. Everyone’s settled down where they ended up.
And yea, either more major disruption or some new killer features (rather than clones of big social) will be needed to shake things up. Neither seem particularly likely in the short term … your EU-meta smackdown is probably the best bet??
Comparatively, it’s definitely a lot more into shitposting vibes, for sure.
I think their biggest problem right now is they don’t have good community self-organising features (nor masto, but the boost culture corrects for that IMO), so those who want more serious sub-cultures aren’t getting much footing (and may never).
Feeds are interesting but not very fruitful IMO and hashtags are new, so it’s a bit flat community-wise there, and many users are “wait & see” I suspect.
Fair (kinda the simple explanation why I’m anti-threads-federation).
While I’m no BlueSky-stan, the idea/promise of the system is a hybrid, which I think is generally worthwhile (especially while things like twitter and threads *dominate*) but also interesting.
How hybridised it becomes (and can become) is the question though with *big* outstanding questions.
LOL … yea plenty right.
I’d forgotten about them (firefish/Misskey plugins) actually (we probably saw each other over on firefish “back in the day”).
The point though is that not all platforms had the problem, which means platform diversity would have lessened the significance.
Interesting! Cool to know that the actual number is higher than 7%.
In the end though how likely are Threads/Meta to *not* have hategroups?
Would it be a good idea to have a more accurate (and therefore higher) number on how many Threads defeds there are?
Perhaps a totally fair critique.
But for me the instance node in the Fedi binds many things together however much their governance aims to be democratic: username, platform, defed policies, moderation, user data (ie posts).
Yea this is the essence of the idea. Strip down the interop requirements as much as possible, relying on existing tech as much as possible, and allow software and norms to solve all the other problems, where, TBF, it seems that software is doing all the heavy lifting in the fediverse anyway, but also has to handle federation and the protocol.
@Aatube @1984 @mindlight @maegul@lemmy.ml
The key idea is that you can have a single unified identity on all the platforms you want. Signing into multiple platforms doesn’t require a new account every time. And cross posting from one platform to another, under your single identity is easy from every platform.
Then leveraging those features (and an open API), a good unifying client will make that easy.
There must be a way of doing that without fatal security issues or decentralisation.
@Aatube @1984 @mindlight @maegul@lemmy.ml
Yea I don’t know the best approach to that. Either a separate server for managing IDs. Or you always a principal server that manages authentication for its platform and others within the trusted “circle”. And then, should the principal server fail, you can switch to another server as your principal. Hubzilla/Streams has some process like that AFAIK.
Yep. Add a good aggregator client (hmmm, Google should make one) and you’re cooking.
Quick attempt at coming up with an alternative.
Something to bear in mind here is it’s my impression that federation creates difficulties that many struggle with. So while it might be over simplified, the scale for me is already weighed with the possibility that we over complication that may need to be remedied.
Also, that big instances (eg mastodon.social) seem to be a natural thing even on the Fedi, there’s clearly perceived value for many there.
@mick_collins @Subversivo @fediverse @fediversenews
I’m not familiar enough (or at all) with C#, but AFAICT, it could make an instance more stable, as firefish and misskey have struggled with handling a decent amount of users and C# could be a faster system for the server.
Also, a re-write sometimes is a good thing. And, developers have different preferences for languages, so having a C# project around enables C# devs to more easily contribute to the fedi.