PieFed 1.6 is released - pronouns, private communities, quote posts and much more
PieFed Meta
78
Posts
25
Posters
0
Views
-
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.
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 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 still don't understand
-
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.
-
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.
@skavau@piefed.social said in PieFed 1.6 is released - pronouns, private communities, quote posts and much more:
> any further replies they make to you in any thread would be automatically thrown out by Piefed.Padme: "for just you, right?"
Anakin:
-
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.
Oh, so if Timmy is a Lemmy user and blocks Me, and I reply to Timmy's posts on piefed.social, piefed.social deletes My comments?
-
Oh, so if Timmy is a Lemmy user and blocks Me, and I reply to Timmy's posts on piefed.social, piefed.social deletes My comments?
Yes, and for other piefed instances. It is due to underlying differences in how rimu interprets how blocking should work vs. Lemmy
-
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.
At least in our case we're divided about 50/50 between Lemmy and PieFed. I could force people to PieFed by deleting Lemmy, but that wouldn't be nice 😀
Private federation would be incredible but I've already heard you say it would be a large amount of work, so I'm not holding my breath!
-
Yes, and for other piefed instances. It is due to underlying differences in how rimu interprets how blocking should work vs. Lemmy
That's awesome! That means Piefed users can't follow a person around putting the same reply under all their posts. I wrote about that problem on My blog!
-
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.
I don't have enough background to understand what putting darvo would mean under posts but since its reportable I would assume its bad. I don't see how they could do this though because by blocking someone they would not be able to see their post or replies to put a reply under.
-
I don't have enough background to understand what putting darvo would mean under posts but since its reportable I would assume its bad. I don't see how they could do this though because by blocking someone they would not be able to see their post or replies to put a reply under.
DARVO stands for Deny, Attack, Reverse/Redirect Victim and Offender.
For example let's say your newest kitten isn't turning out to be as pliable as you'd hoped, and they're getting close to realising that your treatment of them has been less than consensual. If they tell the community, you're in trouble. But if you simply lie to everyone and say they pressured you into sex, and tell everyone not to listen to their side of the story, your reputation is safe and you'll get lots of sympathy. First to speak is usually believed. And if kitten tries to tell the truth, you can simply accuse them of DARVO. The sapphic community doesn't tend to verify claims of abuse in any way, so this stuff is rampant.
And on Twitter, there's a button you can press to view posts by someone you blocked. It won't show up in your feed, but you can go to their profile. If they haven't blocked you, you can spray your DARVO all over the place and they won't even notice.
I don't know if they patched that out since then, but it doesn't matter. You can unblock someone for five minutes, say your harassment, and then block them again. The only technical solution is to put time limits on reblocking someone after your unblock them. But a lot of people don't wanna do that, and I understand why.
-
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.
Fuck me, I've been on Piefed for literally 5 minutes and let me tell you, it's so relieving knowing that I can write (this comment included) without being traced right down to the marrow in my bones. Coming next month I'll start to donate, excellent work, guys
-
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/communitiesfor those communities, but I don't see a page that has something like your screenshotIn
/admin/communities, the far right column has anEditlink. That is where you have some additional settings, including checkboxes that can include/exclude communities from your instance's Popular and All views. You want to make sure that both of these are checked (they are down below the language settings):
-
Fuck me, I've been on Piefed for literally 5 minutes and let me tell you, it's so relieving knowing that I can write (this comment included) without being traced right down to the marrow in my bones. Coming next month I'll start to donate, excellent work, guys
Welcome!
-
Welcome!
❤️🔥❤️🔥❤️🔥 thanks
-
I don't understand what the purpose of the plain http is, can anybody explain to me please?
For really, really poor internet connections, http can be a lot more performant because it has a lot less handshaking that needs to happen. This kind of use case is something rimu cares a lot about since he has previously had to deal with super awful internet connections in the past. It is a very specific use case and outside of that kind of case, it wouldn't be recommended. You can see that both http and https versions of the site can coexist, so it is an option for those that need it.
-
For really, really poor internet connections, http can be a lot more performant because it has a lot less handshaking that needs to happen. This kind of use case is something rimu cares a lot about since he has previously had to deal with super awful internet connections in the past. It is a very specific use case and outside of that kind of case, it wouldn't be recommended. You can see that both http and https versions of the site can coexist, so it is an option for those that need it.
Ah, that makes sense, thanks!
-
DARVO stands for Deny, Attack, Reverse/Redirect Victim and Offender.
For example let's say your newest kitten isn't turning out to be as pliable as you'd hoped, and they're getting close to realising that your treatment of them has been less than consensual. If they tell the community, you're in trouble. But if you simply lie to everyone and say they pressured you into sex, and tell everyone not to listen to their side of the story, your reputation is safe and you'll get lots of sympathy. First to speak is usually believed. And if kitten tries to tell the truth, you can simply accuse them of DARVO. The sapphic community doesn't tend to verify claims of abuse in any way, so this stuff is rampant.
And on Twitter, there's a button you can press to view posts by someone you blocked. It won't show up in your feed, but you can go to their profile. If they haven't blocked you, you can spray your DARVO all over the place and they won't even notice.
I don't know if they patched that out since then, but it doesn't matter. You can unblock someone for five minutes, say your harassment, and then block them again. The only technical solution is to put time limits on reblocking someone after your unblock them. But a lot of people don't wanna do that, and I understand why.
if they did the unblock block thing you would get a notification (in the federation) and could still report it. Honestly it would be sorta a double report as you can point out they are abusing the blocking feature. I certainly don't think blocking should effect notification which is point in time. It should theoretically be impossible to respond to something and notification not going out. Even when someone deletes their comment I have the notification. Which I have come across.
-
if they did the unblock block thing you would get a notification (in the federation) and could still report it. Honestly it would be sorta a double report as you can point out they are abusing the blocking feature. I certainly don't think blocking should effect notification which is point in time. It should theoretically be impossible to respond to something and notification not going out. Even when someone deletes their comment I have the notification. Which I have come across.
if they did the unblock block thing you would get a notification
Hopefully on Piefed, but not on Twitter. I wouldn't chance it.
-
if they did the unblock block thing you would get a notification
Hopefully on Piefed, but not on Twitter. I wouldn't chance it.
Ah ok. I thought this was around piefed or better yet the federation doing it and you where just using twitter as an example why it could never work. Yeah it is definately something which if done has to be done right.
-
Ah ok. I thought this was around piefed or better yet the federation doing it and you where just using twitter as an example why it could never work. Yeah it is definately something which if done has to be done right.
I don't think we should risk the chance of doing it wrong on Piefed. We should stay away from that feature.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Oh so it is, I wasn't seeing it yesterday when I checked. Perhaps unpinning and re-pinning, or removing and re-allowing the ability to show on popular fixed it and I didn't notice it.
Nonetheless, thank you for all the help!
-
Ok, it seems to be working now then. Let us know if you continue to see weirdness with the pinned posts.
-
Oh we actually unpinned the main@piefed.ca post after I confirmed it was working and made that comment. It's the other one from main@lemmy.ca that is still pinned, but doesn't show up for users that aren't logged in
-
Welcome!
-
I mean I get you but the only reason it would be done wrong is if it was intentionally done that way. I mean the system already does notifications and as I said I have gotten them for deleted posts. They don't go away. The devs would practically have to intentionally have it not work that way. I really don't think its a risk at all. Also once something is done its not impossible to undue. The federation and in particular piefed devs are pretty earnest individuals and its not like a coporate system where managment would bury their heads and dig their heels on something bad. There is also no incetive to keep something that does not work out well for some sort of financial gain.
-
Even logged in and with filters so that the post is visible, I don't see the post in the piefed community as pinned. Could it have been unpinned when you did your db reload?
If it is pinned on your side, then it must be a bug of some kind.
-
It's so LGR can load a website other than google on Windows 9x /jk
-
Thanks! That fixed it for our piefed.ca/c/main community. The lemmy.ca/c/main community's post still doesn't show up, but we can plan our announcements to get around that in the meantime
