Just passing through.

  • 1 Post
  • 130 Comments
Joined 6 months ago
cake
Cake day: April 24th, 2024

help-circle



  • I’m sure the Irish call it football when they speak English, but what about in Irish? If Google translate to Irish is trustable,

    English to Irish Football = Peil

    But also Soccer = Sacar

    So maybe there’s two accepted variants. But where does Pail come from anyway? Let’s translate it back to English:

    Peil = Very big potato

    So most of the world plays football, some strange corners of it play soccer, and the Irish play very big potato.

    I’d love if a native speaker could confirm this. #Irish #Gaeilge #football @gaeilge@a.gup.pe @football@a.gup.pe



  • I think this sounds like a good idea. A problem when starting a community is that one wants to find a stable home; it might make sense to set up camp at, say, hardware.watch, but without knowing who operates it it might feel more uncertain than lemmy.world.

    And then, as a result, if lemmy.world ever disappears or has problems, it’ll take way too many communities with it.

    If these topic-specific instances had some sort of collective ownership, I guess we could more effectively guarantee for their continued survival, and it might be more tempting for existing communities to move over there.

    I’d be interested in hearing the thoughts of some admins - would !football@lemmy.world be interested in moving to !football@soccer.forum, given the right organization?

    And a piece of constructive feedback: Vague community names like !main@soccer.forum is probably less likely to attract attention than something specific like !nba@nba.space - when searching for a community, people look up the community name rather than the domain.




  • There’s quite a few people who think the social web is a good term for what this is; websites talking to each other, allowing for two-way communication across platforms.

    Not everybody loves the word “Fediverse”. And then for those who like it, the connotations might be somewhat different.

    You can’t really do anything right in this field, as there are thousands of people ready to cry their hearts out at any given decision. But calling communication between web platforms the social web is not extremely controversial, and it’s a bit easier to sell to a wider audience (government agencies, media outlets, people who don’t know what HTML is) than going on an on about some obscure Fediverse. Different uses.







  • A lot of people use Mastodon as an RSS feed where they can leave comments. This would basically allow you to subscribe to the content of a writer, and get it full-form straight in your feed.

    I could also imagine following artists on Pixelfed, throwing money in their tip jar to keep posted on their newest creations.

    I think there’s a lot of potential here. But monetisation is always tricky on the internet, of course.




  • Yeah, the pitchfork crowd manages to shut down everyone who tries to do something genuinely good for the community, while leaving all the bad actors running wild in the background.

    I mean, we always knew loud voices in the open source community were toxic as fuck - that’s obvious enough from the Linux mailing list. Giving these people their own social network to ruin was wildly optimistic from the beginning. It’s a wonder it hasn’t gone worse.

    It’s amazing how computer nerds posting on the fucking fediverse can be so sceptical of seeing their content leave the platform they’re currently on. Like that’s not the whole goddamn point of posting here in the first place.

    Also, Bridgy.fed rules. Anyone out there on Mastodon or Bluesky: Please opt in! :)


  • If I understand correctly, there’s a central pump running behind the scenes in any AT implementation. You feed content into the central hub, and it pumps it out to everyone connected to it. Bluesky itself provides the one major pump that feeds its network right now.

    So in that sense, Bluesky is a centralised network with decentralized users.

    Frontpage is building a different pump, spreading different kind of content to a different type of platform. So there’s no obvious connection between the Bluesky pump and the Frontpage pump - that’s why they’re talking about bridging in the post.

    It almost seems a bit silly - in order for two AT hubs to talk, you need to build a bridge for them. At that point, you could might as well have built an AP protocol and made it work with Bridgy.fed.

    Furthermore, all “instances” running Frontpage would process data through the same central hub. If that goes down or they run out of funding, it’s all over.

    I’m applauding the Frontpage crowd for trying something new. But I’m not entirely convinced I see the benefit compared to what we’re doing over here.