Developer of PieFed, a sibling of Lemmy & Kbin.

  • 128 Posts
  • 578 Comments
Joined 9 months ago
cake
Cake day: January 4th, 2024

help-circle



  • Rimu@piefed.socialtoWikipedia@lemmy.worldPizza theorem
    link
    fedilink
    English
    arrow-up
    15
    ·
    3 days ago

    I look forward to cutting a pizza like that and then trying to convince others to let me have the biggest slice. Or seeming magnanimous by giving them the biggest.

    Although, the distribution of the toppings is not equal throughout the pizza - on the edges there is a lot more crust.


  • Hi Jerry,

    All good questions which reveal holes in our documentation! Quite a lot of the contents of .env are optional.

    1. There is no S3 support yet. You might not need it though - after almost 1 year of operation piefed.social only has 14 GB of media saved. I’ve put a bit of thought into how to minimize disk usage with good results.

    2. Yes if you leave BOUNCE_ADDRESS empty it’ll go back to the sender instead.

    3. It’s configured in the .env file. You need an IMAP email inbox somewhere, which is outside of piefed’s scope to provide. The BOUNCE_* stuff is for logging into that inbox, which you won’t need to provide if not using BOUNCE_ADDRESS.

    4. Yes, set MODE=‘production’, case sensitive. AFAIK anything other than ‘development’ will cause production mode to be used.

    5. That’s used to connect to https://sentry.io for debugging purposes. You won’t need that.

    6. MAIL_ERRORS=True will cause piefed to send you an email whenever a bug occurs. I don’t recommend using this unless you’re doing development work. You also need to have MAIL_* all set up nicely for it to work - it needs a SMTP server to connect to.




  • Yes I put a bit of effort into the multiple-video issue, with low powered devices in mind.

    The biggest win on that front was lazy-loading the YouTube embeds. Also I found that Chrome can handle quite a lot of videos at once while Firefox gets overwhelmed pretty easily. In my testing with Chrome on my 2012 Macbook https://piefed.social/c/videos@lemmy.world performed okaaay. The tab used only 90 MB of RAM, surprisingly.

    Videos in communities are only loaded if running on AC power and the way that is detected is using a fairly recent browser API that is only provided by Chrome (and derivatives). I’m not simply using loading="lazy" on the <iframe>, I’m using JS to add extra logic to do with the battery. Browsers that don’t have the battery API (Safari, Firefox, 10 year old Chrome) load an image instead. Even Chrome will use an image instead if running on battery power (e.g. on a phone that is not charging).

    I think I’ve been pretty conservative in this regard.