• 1 Post
  • 58 Comments
Joined 1 year ago
cake
Cake day: July 19th, 2023

help-circle
  • SJ0@lemmy.fbxl.nettoFediverse@lemmy.worldSelf hosted instances
    link
    fedilink
    English
    arrow-up
    5
    ·
    11 months ago

    I’ve found the biggest thing isn’t any real resource. My instance runs on a core 2 duo with 4GB of RAM, and I really try to get it to waste memory and barely fill the 4GB.

    The thing is your instance will be blasted by all the other instances you subscribe to. If you subscribe to too many big communities you might find you’re locked out during peak times, but it should be just fine as long as you’re not crazy with follows like I am lol


  • SJ0@lemmy.fbxl.nettoSelfhosted@lemmy.worldNotes taking app
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 months ago

    I don’t think its too bad, but it probably depends a lot on a lot of factors.

    Since I first started my hardware got a lot stronger, and nextcloud, php, and mariadb have all improved and so my experience has gotten pretty decent.

    Remember though, there’s a ton of biases here, so I could be wrong…



  • Friendica is interesting because it’s fundamentally different than a lot of the others. It supports ActivityPub, but also other protocols. The view is fundamentally threaded. It supports groups so some parts of the threadiverse can federate with it in that regard and presumably it could too. It also supports RSS, so you can get content from outside the fediverse.

    I liked it, especially with a custom skin I set up. My big problem was that it has a php back-end and I needed something way lighter for my tiny at the time server, so I went with pleroma.







  • I think it depends a lot on the federated service.

    For mastodon, you follow individual users, so if there’s a million users or ten million or a hundred million, their instances will only be contacting other intances they’re federating with so it’s quite scalable.

    For Lemmy, you follow communities, so every server pulls all the posts and comments the common community. This means that for an instance like lemmy.world hosting lots of different big communities, every new server hammers the one central instance.

    A strategy for improving the situation I think would be to spread the load. Instead of everyone piling into megacommunities, if people spread out into smaller more tight knit communities over many different instances. Of course, this isn’t really compatible with the purpose of having communities like that.

    It does seem to suggest that ActivityPub isn’t necessarily the most appropriate protocol for this purpose, even though it’s what was used because it’s the de facto standard on the fediverse.









  • Besides lacking spaces and some rooms not letting you join, (and the lack of admin tools) the only big issue I find is that you plan to run something other than Element as the interface, you’ll have to test it because many matrix clients expect synapse or dendrite and won’t start with anything else. I’ve run fluffychat, I think kchat(whatever the kde matrix client is), and nheko, they all worked well with conduit.


  • My experience has been that dendrite and synapse totally maxxed out the server I ran it on (100% cpu utilization for days on end), so I run conduit.

    The one downside of conduit is it’s a bit behind, so it doesn’t support all the latest rooms, and it doesn’t support spaces yet, and it has minimal admin tools so you’ll want to create all the accounts you need then close logins because bad actors will try to create logins and get you banned from half of Matrix. That said, I can tell you that even on my piddly little server (an Intel Atom D2550), it runs Conduit, ejabberd, nostr, and lotide, and the server basically sits idle. I can’t speak of bridges, unfortunately, because I don’t really use them.

    This is the guide I used, it worked well to set things up:

    https://gitlab.com/famedly/conduit/-/blob/next/DEPLOY.md