29
We tried to hold back from coding new stuff in order for things to stabilize but it didn't work out. Maybe next month. Instead, we made a whole bunch of cool things:
rimu
- Detect offline instances and stop federating to them until they come back. feamon helped a lot with this.
- Private voting - see https://piefed.social/post/205362 for background.
- Remove moment.js to ease load on clients. We were using a quite heavy javascript library to format dates on the client side but removing the JS and doing it in Python on the backend instead more than halved the amount of JS we need to send (we're now down to 70 KB, gzipped).
- Post teaser redesign - the most significant visual change since the beginning. Image posts now have a much larger preview image and video posts can be played without going to the post itself. YouTube videos are lazy-loaded just before scrolling into view but only if running on AC power. Devices running off a battery (or like Firefox which do not support the battery API) will only load the video once you visit the post page, not while scrolling the feed.
- Use a connection pool for federation - rather than making a new network connection to send an Activity, PieFed will reuse an existing connection where possible. This has less overhead and results in faster federation.
hendrik
- Better notifications about comments buried deep in a thread
freamon
- Better federation of bans from remote admins.
- use HTML portion of Activity instead of Markdown. Lemmy sends Activitys as both Markdown and HTML. For a long time PieFed would use the Markdown and convert it to HTML for display but now it just uses the HTML that Lemmy provides.
- Image alt text federation
- Backfilling improvements especially with image posts.
- Many misc bugfixes
JollyDevelopment
- New theme - "card shadow" - this quickly became a favorite among the dev team and both freamon and myself use it. It's basically the same as the default except there are shadows behind things, giving a more 3D look to the interface and giving a bit more visual hierarchy. It's nice, try it - https://piefed.social/user/settings
- Admin page - instance administration - there is a table showing all the instances you're federating with and stats for each instance.
- Profile export - PieFed has had the functionality to import settings from a Lemmy profile for a long time but now it's possible to go the other way and export settings from PieFed to Lemmy.
- Add remote form - The form for adding a remote community used to require you to type the community as !whatever@instance.com but now you can give the URL as well, e.g. https://instance.com/c/whatever
--
As a free and open source project, PieFed receives no funding and developers are not paid. Any donations you can spare will help cover server and infrastructure costs - https://piefed.social/donate. Thanks!
Hi Jerry,
All good questions which reveal holes in our documentation! Quite a lot of the contents of .env are optional.
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.
Yes if you leave BOUNCE_ADDRESS empty it'll go back to the sender instead.
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.
Yes, set MODE='production', case sensitive. AFAIK anything other than 'development' will cause production mode to be used.
That's used to connect to https://sentry.io for debugging purposes. You won't need that.
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.