A big thank you to those who contributed to making this release, translating, writing documentation, providing emotional support and promoting PieFed! None of this would happen without you all.

New hotness

• Pronouns - when you put pronouns into Extra Fields on your profile that is used as a flair in all communities where you haven't set a flair yet
• Private communities - no federation, only certain roles (depends on the community) can invite new people. Posts inside are only visible to members.
• Mastodon can now quote-boost PieFed posts
• Plain http web UI (no SSL required) with SSL used during federation - see http://retro.piefed.com
• Downvotes can be turned off completely in a community, not just instance-wide
• Admins can sticky a post on the home page, not just mods in their communities
• Auto-delete of replies on remote instances when reply author has been blocked by parent content author (only works in PieFed communities due to a ActivityPub limitation)
• On home page when showing number of replies a post has, calculate the sum of the replies on all cross-posts and display that
• New users can only do 3 posts in their first 24h, to reduce floods of posts by that guy who keeps deleting his accounts and making new ones

More good stuff

• Improve emoji federation compatibility
• Change order of emoji in picker to present most-used ones first
• Daily time limit on usage to help people use PieFed less (released in 1.5.2)
• A way to report posts that need to be tagged as AI generated
• Better accessibility
• Improved handling of bold and italics in markdown parsing
• Don't accept votes from people the author has blocked
• Admins can resend email address verification email
• Admins can add notes to instances to keep track of defederation reasons, etc
• Search form has been simplified
• Option for admins to disable the em-dash detector
• Multiple minor bugfixes and security enhancements

To upgrade from 1.5.x

git pull  
git checkout v1.6.x  

At this point you might see an error message about a merge conflict with compose.yaml. To preserve your custom compose.yaml you will need to copy it somewhere else, then git checkout compose.yaml then git pull again. This time the pull will succeed so after that copy your custom compose.yaml it back, overwriting the one from git.

Then,

./deploy.sh or ./deploy-docker.sh

If you had to do the compose.yaml fix up earlier then you might want to compare what you have with https://codeberg.org/rimu/pyfedi/src/branch/main/compose.yaml and manually copy and paste some improvements in particular the command: part of the db container which tunes postgresql for performance. Adjust the numbers for your system.

This time the database migrations will not take long.

Donations

PieFed is free and open-source software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features.

Donations can be made via Patreon, Liberapay or Ko-fi.

Nice. Thanks for the hard work. PieFed is great.

Always in awe at the speed of development of this project.

Thank you for all your hard work.

FYI https://retro.piefed.social/ has HSTS enabled, so browsers refuse to load it

@die4ever@retrolemmy.com I assume this is your instance?

Great updates, especially the pronouns!

Downvotes can be turned off completely in a community, not just instance-wide

@snoopy@tarte.nuage-libre.fr as you requested a while ago

no, it'd be part of piefed.social, likely just a different frontend

No it's a subdomain off piefed.social and is linked to above, it's rimu's i assume

Oh right, read too fast. Sorry for the ping!

That makes sense, thanks

no problem, I'm always on here anyways lol

And it's always nice to see you around! 😄

Sorry the correct link is http://retro.piefed.com. I'll update the post. Beware your browser will try to switch to https instead because they prefer it so you probably won't get the full rawdogging PieFed experience unless you change your browser setting to stop that.

My fingers are used to .social! I also own the .com to stop someone else nabbing it but couldn't use retro.piefed.social because of SSL on piefed.social...

Always getting better, by leaps and bounds. Thank you, devs, for all the hard work and great ideas!

I'm glad I made piefed my daily driver. Thanks for all your hard work.

I still need to finish the Dillo theme, which will make PieFed compatible with roughly Firefox 3+. That'll compliment the http mode nicely. This is super niche so just something I potter away on occasionally.

Thank you for all your work. 1.5 is just three weeks old. Impressive how much development happened since then.

Testing custom emoji :face_with_rolling_eyes: :sweat_smile:

Cool news about private communities! I'd love to unlock inter-compatibility between instances so that can finally be federated... lots to do in between then and now.

Hopefully we can work together on that soon?

I couldn't think of a way to federate privately, when we don't know which software is at the other end. In the current political environment there are going to be groups of people who simply can't take the risk.

For example with mastodon's followers-only notes - that only gives some privacy because there is massive social pressure on any fedi implementation that doesn't follow the gentleman's agreement we have to hide those notes. That fails when implementations have bugs, are under the control of ICE, or whatever.

It's tricky! Happy to bounce ideas around on it sometime. Maybe encryption...

mmmm. private communities are nice but without federation it means they have to cajole anyone they want to join to make an account on a particular server.

heck if I had an instance I would limit new accounts to not posting for a week or a month if I could. I don't get people feeling the need to start posting like crazy.

User intake would drop through the floor at that point. It's fine to make a welcome post or a post in a community you're interested in, but 3+ posts in a single first day is sus as hell - and Lemmy's ongoing problem here prompted this.

I woul really prefer people I block to not see my stuff as if they blocked me so that they could not vote. I don't block people needlessly but if I do I sorta want them out of my federated life.

That has serious down-the-line consequences though.

You just posted evidence of yourself compromising an account that is not yours (logging in, and then changing the password).

I screenshotted your comment, which is now deleted. Let's have a chat on Matrix.

yeah I think its totally a personality thing so for me its foreign to want to engage before getting the lay of the land. Im not sure how long before I started posting on kbin. Now im a hypocrite to because the thing is that once you have been on the federation then it would get quite annoying if I moved to a new account for new hotness or maybe for censorship reasons and then could not post because I would not think of it as a new place but my account would be a newbie account. So yeah my thing was more like about feeling. I could do 24 hours standing on my head though :)

yeah its my pie in the sky want. I know its not easy but since two people can block each other I know its not impossible either.

I meant people will block to echochamber themselves

https://old.reddit.com/r/TheoryOfReddit/comments/sdcsx3/testing_reddits_new_block_feature_and_its_effects/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

This system exists on Reddit, and this is an example of how it can be gamed.

Now at !fediverse@lemmy.world

The password was publicly available until xylight deleted the comment.

Oh thats not the same. Its stops replies. I want it to be completely bilateral. I don't see their posts or replies and they don't see mine. It only stops replies because they would not see something to reply to. It would effectively make it so if someone blocks someone it effectively shadow blocks them from that person like they blocked them. Mutually assure blockstruction.

Yes, Reddit also blocks visibility too. You would see [unavailable] if someone has blocked you on Reddit. This can cause problems highlighted in that post.

ok because it sounded like it blocked replies which sounded like they still saw the content. I don't even see how they would make a reply to something they can't see. maybe im not getting the article. EDITED - you know I should say probably moderaters should not have content of their communities blocked to them but yeah now it sounds real complicated as you would need the shadow block flag but also some sort of mod override flag for posts to their community. actually now that I say it, it does not feel as bad as I thought at first. Still. more complication.

They wouldn't see posts by users that have blocked them, but the problem is that a malicious account could block people who would call them out and then post misinformation, safe in the knowledge that anyone who might challenge them are blocked.

Yes. The intended use-case is something like a community group that runs their own instance, or an admin team coordinating among themselves. Those people are going to be on the same instance.

Yeah sorry I edited quickly but you are responding quickly. The issue I see is the mods. Those are formal positions. I don't really see a problem with the blocking of people who are good at calling out. I guess when I envisioned it I just assumed mods could always see an admin level of a community that would be everything. Even stuff other mods removed.

Admins can sticky a post on the home page, not just mods in their communities

Nice!

We've been using the announcement field, but that doesn't show up for people on apps. This should be better :)

Swapped it out now: https://piefed.ca/

Odd, I can only see the pinned posts when signed in @rimu@piefed.social

Right now we have two pinned posts, one from lemmy.ca and one from a local only piefed.ca community. Both show up nicely when signed in, neither show up when signed out

probably a whitelist of instances (by hostname) is the only way? each community has its own whitelist set by its mods?

Merci, parfait ! i will desactivate downvote in most of my communities. I hate downvote with a deep passion. :)

New users can only do 3 posts in their first 24h, to reduce floods of posts by that guy who keeps deleting his accounts and making new ones

Alts Georg is an outlier and should not be included in the average alts per users figure

Auto-delete of replies on remote instances when reply author has been blocked by parent content author

I don't really understand this. So if I block Timmy@instance.net and then he replies to My posts on piefed.social, piefed.social will delete his comments? But instance.net won't?

This will be really useful for the soulist credit card number sharing group! /funny

Back when I was involved in sapphic partner abuse drama on Twitter, you could block someone but still reply to their posts, so you could put DARVO under all of their posts and they wouldn't be able to see it or respond to it or report it.

So NO THANK YOU to being able to block someone and hide your posts from them. Abusers would abuse it so bad.

The pinned posts still obey some of the visibility rules of any other post. So, in this case, piefed.ca has Popular as the default sort on the instance. That means that the community that is home to those posts must have the Posts can be popular box checked in the admin settings for that community:

I can't confirm that this is the issue, but I was able to confirm with a dev instance that local-pinned posts do show up for anonymous users using the popular sort when that box is checked and don't when it is unchecked.

DNS is not trustworthy enough, you’ll probably need something like a public / private key pair for each server to verify each other.

It could be, where would I find that setting? I didn't see it in the community settings.

I do see the "popular" column is ticked on admin/communities for those communities, but I don't see a page that has something like your screenshot

Thank you so much for your great work!

I don't understand what the purpose of the plain http is, can anybody explain to me please?

I don’t really understand this. So if I block Timmy@instance.net and then he replies to My posts on piefed.social, piefed.social will delete his comments? But instance.net won’t?

No. It means future comments by the blocked user would be deleted. This only matters when coming from Lemmy instances as on Piefed, a user being blocked disables that user from responding.

I don't know how you do, so much so often. Thank you for everything Rimu and other PieFed dev's who names I haven't memorised!

I still don't understand

It means that if you were to block a user replying to you from a Lemmy instance, any further replies they make to you in any thread would be automatically thrown out by Piefed.