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

  • 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

    In /admin/communities, the far right column has an Edit link. 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):

    checkboxes

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


Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • upcoming fediverse events

    Fediverso fedidev fediverse
    35
    0 Votes
    35 Posts
    188 Views
    @wakest@public.mitra.social interesting to see that the reaction federated across
  • 0 Votes
    1 Posts
    9 Views
    Wäre es nicht super, wenn man sich mit sei­nem Mast­o­don-Account ein­fach für eine Ver­an­stal­tung anmel­den könn­te – so wie das frü­her bei Face­book mög­lich war? Der­zeit geht das noch nicht. Aber es gibt ein paar hoff­nungs­vol­le Anzei­chen, dass sich das ändern könnte.Ich habe es im letz­ten Arti­kel ange­teasert: In der Sprech­stun­de hat André Men­rath (@linos) ein paar inter­es­san­te Din­ge erzählt und wir haben uns über die gene­rel­le Situa­ti­on von Ver­an­stal­tun­gen bei Word­Press und im Fedi­ver­se unterhalten. Bei Plug­ins für Ver­an­stal­tungs-Kalen­der bin ich wirk­lich kri­tisch. Ich habe damals das Ein­ga­be­for­mu­lar für den Ver­an­stal­tungs­ka­len­der bei kiel4kiel.de ent­wi­ckelt. Wenn man jeden Monat 1000 Ter­mi­ne ein­ge­ben will, sieht man zu, dass man da kei­nen ein­zi­gen Klick zu viel macht, weil das immer x1000 geht.Ich habe noch kein For­mu­lar für Ver­an­stal­tun­gen gese­hen, das so prak­tisch war, wie unser User-Inter­face damals. Das fängt damit an, dass Ver­an­stal­tun­gen NIE um 00:00 Uhr anfan­gen. Die Zeit­aus­wahl steht aber bei jeder Soft­ware auf 00:00 und die­ser Stan­dard­wert lässt sich nicht konfigurieren.Events bei WordPressIch bin der Mei­nung, dass es kein ein­zi­ges gutes Event-Plug­in für Word­Press gibt. Auch kein kom­mer­zi­el­les. Ich ken­ne kei­nes. Die meis­ten sind mit Fea­tures total über­la­den, die dafür auch noch schlecht zu bedie­nen sind. Dazu kommt, dass alle Kalen­der schei­ße aus­se­hen und man sie nicht anpas­sen kann – selbst wenn sie sich ein eige­nes Tem­p­la­te-Sys­tem über­legt haben.Beim Web­Mon­tag brau­che ich ein ein­fa­ches Plug­in bei dem man Datum und Uhr­zeit und eine Adres­se ein­gibt. Außer­dem soll man sich an- und abmel­den kön­nen. Ich habe das vor lan­ger Zeit über einen Cus­tom-Post-Type erle­digt, den ich um Datum und Loca­ti­on erwei­tert habe. Außer­dem habe ich die Kom­men­tar­funk­ti­on dort so „gehackt“, dass das Text­feld aus­ge­blen­det wird. So mel­det man sich an, indem man einen Kom­men­tar ohne Text abgibt. Des­we­gen bekommt man auch kei­ne Benach­rich­ti­gung und man kann sich auch dar­über nicht abmelden. Das funk­tio­niert. Aber ich hät­te trotz­dem eine etwas kom­for­ta­ble­re Lösung. Bei Gather­Press arbei­ten wohl gera­de eini­ge moti­vier­te Ent­wick­ler an einem neu­en Plug­in für Events. Das sieht auf den ers­ten Blick sehr auf­ge­räumt aus und scheint sich an den moder­nen Para­dig­men der Word­Press-Ent­wick­lung zu orientieren.Events im FediverseAuch im Fedi­ver­se gibt es Ver­an­stal­tun­gen. Mobi­li­zon ist eine Lösung dafür. Auf so einer Instanz gibt es dann nur Ver­an­stal­tun­gen. Ich ken­ne mich damit nicht so gut aus. Aber super wäre es natür­lich, wenn ich einem Account bei Mobi­li­zon bspw. von Mast­o­don aus fol­gen könn­te und wenn mir dann eine Ver­an­stal­tung durch die Time­line läuft, kli­cke ich auf „teil­neh­men“ und bin ange­mel­det. Das geht aber noch nicht. Es gibt aber wohl Über­le­gun­gen bei Mast­o­don, Ver­an­stal­tun­gen bes­ser zu unter­stüt­zen. Fri­en­di­ca, Hub­zil­la und Ple­ro­ma kön­nen das schon – zumin­dest teilweise.Auf der Sei­te von Word­Press arbei­ten And­re Men­rath und Mat­thi­as Pfef­fer­le (@pfefferle) an einer Bridge für die bestehen­den Event-Plug­ins ins Fediverse.Die­se The­ma ist lei­der noch nicht ganz so kon­kret wie die grund­sätz­li­che Unter­stüt­zung für Arti­kel von Word­Press in Mast­o­don. Es sind eini­ge Puz­zle­tei­le, die ein inter­es­san­tes Bild ver­spre­chen, wenn sie jemand klug zusammensetzt. Ich fänd es cool, wenn ich eine Lösung hät­te bei der Men­schen den Ver­an­stal­tun­gen des Web­Mon­tags bspw. auf Mast­o­don fol­gen und sich anmel­den könn­ten. Zusätz­lich wäre es aber natür­lich nötig, dass man sich auch wei­ter­hin unkom­pli­ziert ohne Account anmel­den könn­te. Ein Ter­min-Plug­in, bei dem ich eine Stan­dard-Start­zeit ein­stel­len kann, weil der Web­Mon­tag immer ab 19 Uhr sei­ne Tür öff­net; einen Stan­dard-Ver­an­stal­tungs­ort, weil wir meis­tens in der Star­ter­kit­chen sind. Eine öffent­lich ein­seh­ba­re Teil­nah­me­lis­te, aus der sich Leu­te auch auf Wunsch aus­blen­den kön­nen und die sich nach ein paar Mona­ten von allei­ne löscht und nur die zusam­men gerech­ne­te Zahl der Anmel­dun­gen behält.Dar­auf muss ich wohl noch ein wenig war­ten. Aber Vor­freu­de ist ja auch etwas Schönes.
  • 0 Votes
    1 Posts
    22 Views
    I've gone live!Fireside Fedi - Episode 50 - Jaz-Michael King - IFTAS#owncast #streaming #interview #fediverse #fedi #people #show #firesidefedi #FsFhttps://stream.firesidefedi.live
  • 0 Votes
    12 Posts
    54 Views
    I suppose, although in that scenario theoretically one could add as:sensitive to mark the status as CW'd? I don't think CW logic is even run for non-Notes at the moment, though I could be mistaken.