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
  • 0 Votes
    1 Posts
    13 Views
    Every major version is a milestone, and 8.0.0 is no exception. Your WordPress blog just became a two-way street in the Fediverse. Visitors can like and boost your posts directly on your site. Media from federated replies is handled more reliably, and new block patterns make it easy to drop ActivityPub features into your pages.Like and Boost, Right From Your BlogThe Fediverse Reactions block now has optional Like and Boost action buttons, inline with each reaction group. When a visitor clicks one, a modal opens where they can enter their Fediverse handle or copy the post URL to interact from their home server.The plugin remembers the visitor’s profile in their browser, so the second time around it’s even faster. And for folks who aren’t familiar with how the Fediverse works, each modal now includes a collapsible “Why do I need to enter my profile?” help section that explains the open social web in plain language.This dramatically lowers the friction for cross-platform engagement.Block Patterns and TemplatesSetting up a Fediverse-ready profile page used to mean manually assembling Follow Me, Extra Fields, and Followers blocks. Not anymore.We’ve added a “Fediverse” block pattern category with four pre-configured layouts:Author Profile with Follow, a compact profile card.Fediverse Follow Page, a full-page follow experience.Author Header with Follow, great for author archive headers.Fediverse Sidebar, drop it into any sidebar or widget area.If you’re running a block theme on WordPress 6.7+, there’s also a new Author Archive (Fediverse) block theme template ready to go.Publish Smarter With Post Format SuggestionsA new pre-publish panel now analyzes your post content and suggests an appropriate post format when your object type is set to “Post Format.” Got a post that’s mostly images? It’ll nudge you toward the Image format. A video post? Video format.This matters because media-focused Fediverse platforms like Pixelfed and Vernissage display Notes differently than Articles, so choosing the right format means your content looks its best everywhere it lands.Community SnippetsWe’ve added a snippets/ folder to the GitHub repository, a home for lightweight, community-contributed extensions that don’t belong in the core plugin but are too useful to lose. The first batch includes:FediBlog Tag, automatically adds #FediBlog to standard blog posts for better Fediverse discovery.Locale from Tags, derives post locale from taxonomy tags.Bot Account, marks your profile as automated and displays a “BOT” badge in the Fediverse.Blockless ActivityPub, renders Fediverse reactions as pure server-side HTML, no JS required.Photon CDN, serves cached remote media through Jetpack’s Photon CDN for faster delivery.Got a snippet of your own? Check out the snippets folder and send a PR.Smarter Media CachingUnder the hood, we’ve rebuilt how the plugin handles remote media, avatars, emoji, images, audio, and video from across the Fediverse. Instead of importing everything into the WordPress Media Library at insert time, media is now wrapped in custom blocks and cached lazily at render time.What does that mean for you? Faster processing of incoming content, less disk usage, and better rendering of audio and video attachments. Original remote URLs are preserved in block attributes, so caches can be regenerated without data loss. If you’re using Jetpack’s Site Accelerator, that works too, the new system is built filter-first.For site admins, there are new CLI commands to keep things tidy:wp activitypub cache statuswp activitypub cache clearMinimum PHP 7.4With WordPress 7.0 deprecating PHP 7.2 and 7.3, we’ve raised the minimum requirement to PHP 7.4. This lets us clean up compatibility polyfills and use more modern PHP features going forward. If you’re still on an older version, update your PHP before updating the plugin.ChangelogAddedAdd a help section to interaction dialogs explaining the Fediverse and why entering a profile is needed.Add a notice on the Settings page to easily switch from legacy template mode to automatic mode.Add a pre-publish suggestion that recommends a post format for better compatibility with media-focused Fediverse platforms.Add a Site Health check that warns when plugins are causing too many federation updates.Add backwards compatibility for the ACTIVITYPUB_DISABLE_SIDELOADING constant and activitypub_sideloading_enabled filter from version 7.9.1.Add bot account snippet that marks ActivityPub profiles as automated accounts, displaying a “BOT” badge on Mastodon and other Fediverse platforms.Add Cache namespace for remote media caching with CLI commands, improved MIME validation, and filter-based architecture.Add federation of video poster images set in the WordPress video block.Add Locale from Tags community snippet.Add optional Like and Boost action buttons to the Fediverse Reactions block, allowing visitors to interact with posts from their own server.Add pre-built Fediverse block patterns for easy profile, follow page, and sidebar setup.Add snippet for blockless fediverse reactions.Add wp activitypub fetch CLI command for fetching remote URLs with signed HTTP requests.ChangedImproved active user counting for NodeInfo to include all federated content types and comments.Improve language map resolution to strictly follow the ActivityStreams spec.Superseded outbox activities are now removed instead of kept, reducing clutter in the outbox.The minimum required PHP version is now 7.4.FixedAccept incoming activities from servers that use standalone key objects for HTTP Signatures.Fix a crash on servers where WordPress uses FTP instead of direct file access for media caching.Fix a crash when receiving posts from certain federated platforms that send multilingual content.Fix automatic cleanup of old activities failing silently on sites with large numbers of outbox, inbox, or remote post items.Fix comment count to properly exclude likes, shares, and notes.Fix follow button redirect from Mastodon not being recognized.Fix modal overlay not covering the full screen on block themes.Fix outbox invalidation canceling pending Accept/Reject responses to QuoteRequests for the same post.Fix QuoteRequest handler to derive responding actor from post author instead of inbox recipient.Fix reactions block buttons inheriting theme background color on classic themes.Fix reactions block layout on small screens and remove unwanted button highlight when clicking action buttons.Fix signature verification rejecting valid requests that use lowercase algorithm names in the Digest header.Fix soft-deleted posts being served instead of a tombstone when the post is re-saved.Improve compatibility with federated services that use a URL reference for the actor’s public key.Improve handling of all public audience identifiers when sending activities to followers and relays.Prevent private recipient lists from being shared when sending activities to other servers.Get ItDownload from WordPress.org or grab it on GitHub. Remember to check your PHP version first — 7.4 or higher is now required.A huge thank you to everyone who contributed code, testing, bug reports, and ideas to this release. Special thanks to @kraft, @jeremy, and @futtta for their snippet contributions.Update, try out those Like and Boost buttons, and let us know what you think — what’s the feature you’ve been waiting for? What would you like to see next?
  • 0 Votes
    1 Posts
    11 Views
    It's our birthday today. 🎉Two years ago today, we filed the paperwork for Mirlo to officially become a legal entity. We're so grateful and humbled by everyone who has contributed to the experiment since then. Here's to many more years making music together on the internet! 🐦‍⬛🐸🎺 #Music #Musicians #OpenSource #Mirlo #Fediverse #FediMusic #Birthday
  • 0 Votes
    2 Posts
    17 Views
    My favorite #fediverse platforms are #snac and #GoToSocialChange my mind.
  • 0 Votes
    4 Posts
    24 Views
    @fox Not if activity-connect is run by someone else