I’m looking for input on how well Piefed responds to occasional downtime of up to a few days, specifically regarding how federation recovers after such an event.

Basically looking to know how amenable it is to selfhosting via reverse proxy from dodgy setups which are the best some of us proles can manage. I try to run some services where I can but my situation inevitably results in an event or three per year, on average, with some days down.

  • ThorrJo@lemmy.sdf.orgOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days ago

    I’m not specifically looking for options in that regard (yet), but I’m mulling the idea of running my own server with closed signups just to have a place to potentially slurp in RSS feeds and such for people who want to subscribe to them. I haven’t touched PieFed yet but I’m definitely interested in it because I’m more familiar with the Python ecosystem than Rust.

    • wjs018@piefed.wjs018.xyz
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 days ago

      Piefed doesn’t currently natively support setting up an rss feed to populate a community (though there is an issue for it on the codeberg, so hopefully soon). However, we do have an api at this point that is feature complete enough to cook something like this up without too much trouble.

      As for self-hosting piefed, it is pretty comparable to lemmy. They both are dockerized and I have a personal instance of both of them. Resource-wise, for a personal instance, I haven’t really noticed a difference, though my VMs are well enough provisioned that I doubt I would run into any bottlenecks for a 1-user instance.

      I’m more familiar with the Python ecosystem than Rust

      This is basically how I have ended up becoming a piefed contributor. There were features that weren’t in lemmy that I was frustrated by, but don’t know a thing about rust. So, I just started implementing things in python…and have just kept doing it.