I used to be @ambitiousslab@lemmy.ml. I also have the backup account @ambitiousslab@reddthat.com.

  • 1 Post
  • 9 Comments
Joined 1 month ago
cake
Cake day: January 11th, 2026

help-circle
  • I like the idea and also want to support independent journalism, but in the UK context, I don’t think a separate community makes sense. I had a look at !uk_politics@feddit.uk and !unitedkingdom@feddit.uk and I think most (70%+) of the posts from my unscientific sample would count as independent (in the sense of “free from government and corporate interests, and not controlled by a major media conglomerate”).

    I wonder if it would make sense to set up a bot to automatically crosspost articles from allowlisted domains from these general news communities? And if unknown links were found, there could be a mechanism to add them to the allowlist?

    These were the sources I found:

    • The Guardian
    • Al Jazeera
    • Novara Media
    • The Canary
    • Socialist Worker
    • Morning Star
    • Democracy for Sale
    • BBC
    • Politics Joe
    • ITV
    • New York Post
    • Metro
    • The National
    • Associated Press
    • Big Issue
    • London on the Inside

    A lot depends on the definition of independent, and I’m focused on the text rather than perhaps the intent of the definition. If that was stronger, a lot of these could be excluded and a separate community might make more sense.


  • I agree with you, and I think there’s a tension between the technical solution (meeting users where they are) and political solution (persuading the users to come to our way of thinking).

    The technical solution is an unequal fight. We have to provide a familiar and equally good experience - integrating everything into these easy-to-use everything apps, on a shoestring budget compared to the proprietary apps. And, without the “education”, users will converge on particular instances because that’s what’s most convenient, giving a lot of power to particular players in the network.

    If we can persuade people to prioritise freedom over convenience, then we end up with a much more resilient userbase who will go help with the existing networks.

    I don’t know how we can make people care, though. The free software movement has been trying for 40 years to make regular users care, but the message only really lands with developers. There’s certainly more interest in taking down big tech nowadays, but convenience still seems to come first.


  • Searching for a single Discord alternative may be asking the wrong question however. Discord itself is an extensive bundle of functions smashed together: real-time chat, persistent forums and documentation, voice chats, events and even games. Rather than replicating that bundle in a single app, the open social web may be converging on a different model entirely, where specialised services handle specific functions while sharing identity and social connections across protocol boundaries. These individual services themselves do not have to share the same protocol underneath, and may actually work better if they don’t, with each protocol handling the part it is best designed for.

    This is the most interesting part to me. Can users be persuaded to have different expectations from the proprietary apps they’re used to?

    Whenever these sudden migrations happen, the alternatives that win seem to be the ones that look and behave as similarly to the proprietary app as possible, as the people switching don’t care about decentralisation, and are much more sensitive to any changes in experience.

    I think we need to create separate experiences, backed by the same protocol, for people who care about decentralisation and freedom (and discover the fediverse naturally, outside of these big migrations), and those that show up during the big migrations.

    For the first group, we want software that’s easy to self-host, customisable, spreads users between instances, ultimately empowers them to have the exact experience they want. For the second group, we should just copy the exact experience of the proprietary networks as much as the protocol allows.

    Of course, the risk is that we get even larger influxes of people who never had to learn the community norms. Is that worth it? - I’m not sure.







  • I get you. I can never think of anything that would be interesting to post or ask in the more discussion-oriented communities, let alone choose a specific one to post in. I definitely find comments easier, as well as posting to more niche communities. I feel the scope is usually better defined there.

    Would you say it’s about not knowing if your post would be accepted in the community, or just finding the best place for it? If it’s the latter, AskLemmy could be good for general questions, or failing that, any of the casual chat communities such as !chat@beehaw.org.

    As long as your post meets the rules of the community/instance, I feel it’s better to post somewhere than not at all - people can always crosspost it elsewhere if they like.


  • Now, I’m not asking companies to open-source their entire codebase. That’s unrealistic when an app is tied to a larger platform. What I am asking for: publish a basic GitHub repo with the hardware specs and connection protocols. Let the community build their own apps on top of it.

    I agree with this. I think the most important thing is not necessarily the original company releasing their proprietary code (although that would be nice), but it being easy (and legal!) for hackers to reverse engineer and/or build on top of the platform.

    The irony is that, since most such products will have some GPL’d code in there somewhere, most products already basically have such a requirement, thanks to the section requiring complete corresponding source including installation instructions. Hopefully, the Vizio case will establish the precedent that users, as well as copyright holders, can take action against such companies.