Web developer. Lead developer of PieFed

  • 85 Posts
  • 332 Comments
Joined 3 years ago
cake
Cake day: January 4th, 2024

help-circle




  • I can’t work with or communicate with the PyLova people. I have too much trauma from the bullying campaign they continue to operate.

    I’m giving away code. It’s a gift. Giving that gift does not put me under any obligations including talking with anyone else, especially not with groups which attack me and disparage me whenever they can.

    The way I build PieFed is not intentionally incompatible with Pylova - that happens as a side-effect of me not talking to them and me never looking at their code.
















  • I’m not sure but my guess it’s an attempt to deal with the problem where sometimes federation activities arrive in the wrong order (especially after an instance has been offline for a while) - by making a GET to the origin server you can be sure you’ve got the latest version of the content. There are probably better ways to achieve that, though.

    PieFed prioritises efficiency over correctness so it just accepts whatever is sent to it. In 3 years no one has complained about seeing stale content although I’m sure it happens occasionally.


  • Lemmy does this to itself, too - when you create a post it federates out and then every Lemmy instance that receives it makes a GET request to retrieve the post from the original server. Even though it just received the exact same data. Some other fedi software is even worse - Akkoma does a GET of the id of every activity it receives, not just for posts but for Likes too.

    It’s insane.

    Anyway, proper caching at the reverse proxy / Cloudflare level solves it. The same kind of caching setup would do the same for sites serving HTML, like NPR too.