PieFed 1.6 is released - pronouns, private communities, quote posts and much more
-
I’m super happy about the pronouns addition. It’s super convenient. Thanks a lot.
BTW if you have pronouns in your display name, as you have, the pronouns in the Extra Fields won’t be shown. No point showing them twice!
-
BTW if you have pronouns in your display name, as you have, the pronouns in the Extra Fields won’t be shown. No point showing them twice!
It might be an inter-instance thing, so it’s gonna get updated soon, but I changed my displayed name right after seeing this announcement to remove the pronouns from it. :3
-
It might be an inter-instance thing, so it’s gonna get updated soon, but I changed my displayed name right after seeing this announcement to remove the pronouns from it. :3
Oh yes, that’s it
-
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.xAt 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.yamlthengit pullagain. 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.shIf 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.
- 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)
- 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
Are these features at least optional on an instance-by-instance basis?
Edit: Didn’t mean to be negative, just had a couple concerns I clarified in a reply below and thought options could be helpful. I appreciate ongoing improvements to Piefed all the same.
-
- 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)
- 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
Are these features at least optional on an instance-by-instance basis?
Edit: Didn’t mean to be negative, just had a couple concerns I clarified in a reply below and thought options could be helpful. I appreciate ongoing improvements to Piefed all the same.
Currently, no. I’m not sure a block system could work properly with different rules per instance. (Yes, I realise the irony of Lemmy having a different system here too).
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
This is currently universal, but it will likely be added into a specific option at some point.
-
Currently, no. I’m not sure a block system could work properly with different rules per instance. (Yes, I realise the irony of Lemmy having a different system here too).
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
This is currently universal, but it will likely be added into a specific option at some point.
While increasing the impact of blocks could diminish the risk of harassment, it could also have the opposite effect of preventing users from responding to comments made about them by users who’ve blocked them.
While I personally think manual moderation is a better solution, if a system that blocks users in this manner is implemented, then there should also be an optional toggle for users to hide posts by users who’ve blocked them to avoid having posts that can’t be interacted with in one’s feed.
And while I can see the benefits of preventing potential spam from new accounts, it could also discourage new users from staying on if they are immediately limited in what they can share on the platform; Lemmy, Piefed, and Mbin don’t have enough users as it is to be risking losing anyone.
In terms of the other features, I think the addition of pronouns will help Piefed distinguish itself from Reddit by fostering inclusivity.
-
- 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)
- 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
Are these features at least optional on an instance-by-instance basis?
Edit: Didn’t mean to be negative, just had a couple concerns I clarified in a reply below and thought options could be helpful. I appreciate ongoing improvements to Piefed all the same.
People seem to assume that how things are now are how I want them to be. Like I made a decision not to provide some flexibility, intentionally.
It’s just easier and quicker NOT to provide an admin UI for every little thing, then document it, then have 95% of people will just leave it on the default setting anyway, then try to make an admin UI that isn’t cluttered and confusing because it’s full of all kinds of unimportant nonsense.
If you want something to be admin-changeable, have a conversation with us about it and we’ll see how many others want it to be changeable and how it could work. Then if a developer is interested enough perhaps they’ll write some more code for free, for the love of it, and maybe someone will write some documentation of that setting for free because they want to, etc.
That’s how this works.
Sorry if I’m overreacting to your question, there’s been a lot of accusatory questions lately.
-
While increasing the impact of blocks could diminish the risk of harassment, it could also have the opposite effect of preventing users from responding to comments made about them by users who’ve blocked them.
While I personally think manual moderation is a better solution, if a system that blocks users in this manner is implemented, then there should also be an optional toggle for users to hide posts by users who’ve blocked them to avoid having posts that can’t be interacted with in one’s feed.
And while I can see the benefits of preventing potential spam from new accounts, it could also discourage new users from staying on if they are immediately limited in what they can share on the platform; Lemmy, Piefed, and Mbin don’t have enough users as it is to be risking losing anyone.
In terms of the other features, I think the addition of pronouns will help Piefed distinguish itself from Reddit by fostering inclusivity.
While increasing the impact of blocks could diminish the risk of harassment, it could also have the opposite effect of preventing users from responding to comments made about them by users who’ve blocked them.
This is true.
While I personally think manual moderation is a better solution, if a system that blocks users in this manner is implemented, then there should also be an optional toggle for users to hide posts by users who’ve blocked them to avoid having posts that can’t be interacted with in one’s feed.
I mean wouldn’t this just mean blocking them in return?
And while I can see the benefits of preventing potential spam from new accounts, it could also discourage new users from staying on if they are immediately limited in what they can share on the platform; Lemmy, Piefed, and Mbin don’t have enough users as it is to be risking losing anyone.
In my experience, it’s very rare for a Day 1 account that isn’t a troll/spammer of some sort to make more than 3 threads in the first 24 hours. That said, yes, it should be an optional instance toggle here.
-
People seem to assume that how things are now are how I want them to be. Like I made a decision not to provide some flexibility, intentionally.
It’s just easier and quicker NOT to provide an admin UI for every little thing, then document it, then have 95% of people will just leave it on the default setting anyway, then try to make an admin UI that isn’t cluttered and confusing because it’s full of all kinds of unimportant nonsense.
If you want something to be admin-changeable, have a conversation with us about it and we’ll see how many others want it to be changeable and how it could work. Then if a developer is interested enough perhaps they’ll write some more code for free, for the love of it, and maybe someone will write some documentation of that setting for free because they want to, etc.
That’s how this works.
Sorry if I’m overreacting to your question, there’s been a lot of accusatory questions lately.
Didn’t mean to offend, just providing feedback. Thank you for your continued commitment to improving Piefed.
-
People seem to assume that how things are now are how I want them to be. Like I made a decision not to provide some flexibility, intentionally.
It’s just easier and quicker NOT to provide an admin UI for every little thing, then document it, then have 95% of people will just leave it on the default setting anyway, then try to make an admin UI that isn’t cluttered and confusing because it’s full of all kinds of unimportant nonsense.
If you want something to be admin-changeable, have a conversation with us about it and we’ll see how many others want it to be changeable and how it could work. Then if a developer is interested enough perhaps they’ll write some more code for free, for the love of it, and maybe someone will write some documentation of that setting for free because they want to, etc.
That’s how this works.
Sorry if I’m overreacting to your question, there’s been a lot of accusatory questions lately.
as a dev I get it, people always say “just make it an option!” to every little thing
but then they aren’t the ones who have to code, write tests, document, and do QA on the quintillions of permutations of options and keep maintaining them as new issues appear with certain combinations
and even if everything goes perfectly you still have a super cluttered list of options and then no one uses any of them because it’s too much to read through them all
