Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

PieFed 1.6 is released - pronouns, private communities, quote posts and much more

PieFed Meta
78 25 82
  • 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.

    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?

  • 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.

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

  • 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.

    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.

  • 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

    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:

    admin screen

    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.

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

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

  • 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:

    admin screen

    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.

    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

  • 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.

    Thank you so much for your great work!

  • 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.

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

  • 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?

    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.

  • 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.

    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.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.

    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


Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • New Social Web Working Group at W3C

    Fediverse fediverse
    11
    1
    0 Votes
    11 Posts
    52 Views
    Oh I see. Yes, AP first apps would be great, but getting older apps connected via AP is important too. NodeBB predates ActivityPub (or came around the same time), and so we added it recently. It works quite well with our existing code. Not much of a compatibility layer.
  • 0 Votes
    5 Posts
    15 Views
    @tommi @ivan Oh wow. A me piacerebbe fare la stessa cosa con varese.social. Sto pensando di spostare l'istanza da masto.host su un VPS dedicato. Potrebbe essere una buon occasione per cambiare e passare a Bonfire.Sarei super curioso di sapere quanto sia fattibile!
  • 0 Votes
    1 Posts
    13 Views
    Tech people talk about tech too much. I really really REALLY want to use all the awesome privacy friendly FOSS (and similar) stuff, but I am not a techie person! I don't know how to program, nor do I want to. And every SINGLE time I try to find out even what thing (OS, program, app, service, etc) to use, let alone how, and I search for it... I get techie-focused answers. It's complete gibberish to me! Absolutely useless. It makes me feel actively unwelcome even though I really care about using alternatives to Windows, Meta, X and other dystopic nonsense. For example: I'm like "How do I start a non-enshittified group chat to talk about a thing?" and all the results are technobabble to me. I don't even know if the words they use are supposed to be normal english words or if they refer to orgs or groups or apps or some weird coding wizardry. I am so lost, every single time. I stick with it though. But like. I wonder if the tech people realise that this is happening???? Because they probably understand what they're talking about. And they seem to not realise that not everyone does. I'm not trying to blame or shame anyone or even complaining as such (a little bit complaining, ngl), mostly just giving feedback. This is not an issue with a singe thing but with ALL of it as a whole! Including #GNU #Linux the #Fediverse #Matrix and most #FOSS apps. My sincere wish: Give non-techie people an EASY TO FIND and easy to read and easy to understand and easy to implement guide about how to use the things as an alternative to using big corporation services, ie, "I just want it to work" and not have to worry about the technical side of things. (examples in thread)
  • Looking for federated NodeBB instances

    Fediverso fediverse
    5
    0 Votes
    5 Posts
    32 Views
    Oh, I'm sorry to hear that... unfortunately debugging server-to-server interactions is kind of tough. It should work though, so I don't know why it didn't... yet. It could be their version of NodeBB isn't up to date enough. cwsmith@community.darkscribes.com cwsmith@community.nodebb.org are you able to weigh in and let me know the NodeBB version? Could also be a privileges issue with the fediverse pseudo-user.