PieFed 1.6 is released - pronouns, private communities, quote posts and much more
PieFed Meta
78
Posts
25
Posters
82
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.
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.
-
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.
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.
-
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.
-
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 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.
-
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.
-
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.
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 :)
-
That has serious down-the-line consequences 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.
-
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
This system exists on Reddit, and this is an example of how it can be gamed.
-
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.
Now at !fediverse@lemmy.world
The password was publicly available until xylight deleted the comment.
-
I meant people will block to echochamber themselves
This system exists on Reddit, and this is an example of how it can be gamed.
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.
-
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.
Looks like a great update. Very cool that communities have the granular ability to disable down votes.
-
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.
-
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.
-
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.
-
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.
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.
-
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.
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.
-
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.
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/
-
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
-
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...
probably a whitelist of instances (by hostname) is the only way? each community has its own whitelist set by its mods?
Gli ultimi otto messaggi ricevuti dalla Federazione
-
https://discuss.tchncs.de/u/devtoolkit_api https://lemmy.world/u/albert_inkman https://feddit.org/u/arnoldnakamura ~~https://lemmy.world/u/james_bond1 ~~ https://lemmy.world/u/epstein_bot https://lemmy.world/u/humanobserver https://lemmy.world/u/cyberb https://thelemmy.club/u/insightseeker
-
Deploy PieFed on Elest.io and get a working dedicated instance in less than 3 minutes. You can Relax knowing that we are taking care for you of install, configuration, encryption, backups, software updates, os upgrades, live monitoring, alerts, live migrations without downtime ... and more!
-
@povoq@slrpnk.net okay, yes. This is true, once it leaves the local server there are no guarantees.
However I'd have to ask whether there is an acceptable tradeoff in risk of content exposure.
After all, even in local private groups, things could get leaked via copy-paste, screenshots, etc. The weakest link is the social element.
-
At a guess, private piefed communities don't federate because once content federates, you can't control who can see it. All you can do is hope that the remote instance will follow the privacy settings, but you can't enforce them.
Private lemmy communities don't federate because they don't exist.
-
Because once it leaves the server there is no guarantee that the remote server understands or even respects the notion that it should be private.
Lemmy doesn't have private communities yet afaik.
-
Is that different for Lemmy? If so, why is PieFed's approach to private communities different from Lemmy's?
-
Ah true! NodeBB doesn't support emoji reactions yet.
Thanks for reminding me of yet another way we're behind Piefed :muscle:
-
Emoji reactions are a big one - rather than voting you can apply an emoji, which is a much richer expression.
Every community can have different settings for who can downvote. Here are the options:
If you downvote more than you upvote, pretty soon you can't downvote anymore.
