Mama told me not to come.

She said, that ain’t the way to have fun.

  • 0 Posts
  • 597 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle



  • What’s that about Gitlab? I use it hosted, and it can be self-hosted, so I’m not sure what the issue is.

    Honestly, I don’t find a lot of value in the fediverse generally. I guess it’s kinda cool that things connect together, but URLs also get the job done pretty well, and cookies and password managers handle logins and stuff between platforms. The real value is in being an alternative to the big, centralized services.

    I’m not here because of the fediverse, I’m here because Reddit pissed me off almost a year ago and this is a suitable-enough replacement. Seeing my posts on other platforms is honestly a little odd (in theory) because having a post from one context (say lemmy) appear in another (say git hosting) is often not wanted. So I want separation between different types of social media (e.g. I avoid Mastodon because I don’t like that form), not more sharing. But that’s not a real concern, it’s just not why I use it.

    That said, I have no idea what kind of social media project you’re working on, so maybe federation is the perfect fit. The fediverse is certainly a good way to quickly build an audience and generate content.

    Note about my project

    For my social media project, I’m looking at p2p, because I’m more worried about scaling and longevity. Lemmy can get expensive to host due to duplication, so a big instance going down due to funding can fragment communities (though old data will live on any instance federated with that community).

    My project will use user devices for most data storage and retrieval, and a handful of (hopefully community funded) storage instances for availability and backups. There’s a lot less duplication, so hosting will be a fraction of what Lemmy costs since most data will be served by people near you.

    The only infra I’ll need is:

    • relay nodes to connect people - mostly short-lived STUN connections, but TURN will be supported for people behind CGNAT
    • backup storage nodes - I plan to only store less popular, older content

    And since I’ll only be handling text at first (pictures and whatnot will just be URLs), it should be really cheap.

    And that’s it. If I lose interest, someone probably already has their own storage nodes (lots of data hoarders out there) and can easily take over.



  • self-sustaining

    I’m hesitant about that. It’s still run by volunteers, and that’ll end when the volunteer gets tired of paying the bills for whatever instance.

    I think Lemmy needs to find a way to disassociate instance hosting from some individual kindly paying the bill. It doesn’t need to be profit driven, just a way to get people to donate enough to keep the servers going.






  • I really like the spoiler text block.

    My reasons
    • I can explain what’s hidden
    • without spoiling anything
    • and users can decide to look out not

    It’s just triple colon and description, then your message, then close with another triple colon. If you forget, click the spoiler button (at least on Jerboa, probably on web as well).

    Inline spoilers would be nice too, and there’s room for both.


  • Yeah, that would work within lemmy, and it would make it easier to detect whether a link is to lemmy or something else (look for /c/<community chars>@<hostname chars>/<rest>). But you’ll still have the issue of clicking a link elsewhere (say, a blog post) to an instance that’s not yours, so you still wouldn’t be able to directly comment w/o copy/pasting part of the URL to your instance.

    That said, that change alone would reduce a lot of friction for users. My point is that it still doesn’t fix the root of the problem. I guess we could use a browser extension to auto-redirect to your instance of choice, but that’s just yet another barrier for users.


  • No, I’m pretty sure that’s a quirk of how the fediverse works. Posts, comments, etc are in two places:

    • the instance the community is hosted on
    • your instance (i.e. unique to users of your instance)

    You’ll want the first (the permalink) for general posting, and the second for your own use. However, lemmy doesn’t handle the first very well, so both options kinda suck.

    I honestly don’t think there’s a good solution to this. We can make improvements though, such as lemmy figuring out that a link is a lemmy link, either through special syntax (like @user@instance or !community@instance) or checking a list of known instances, but the real problem is that users need to be aware of instances, and that’s poor UX imo.

    I’m working on an alternative to lemmy that solves this (and has a bunch of other drawbacks that I hope are acceptable), but I hope it’s not necessary and someone more clever than me can solve it.