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

Just an occasional reminder that disabling replies is the #1 requested feature from Mastodon.

Fediverso
51 21 266

Gli ultimi otto messaggi ricevuti dalla Federazione
  • @jonny@neuromatch.social honestly good for you for investing the time to critique this knowing it's AI (adjacent or wholesale) involvement.

    read more

  • @julian @PortaFed
    giving a further read: I can't really imagine a case where someone would a) regularly be creating signed backups and also b) know in advance where you wanted to migrate to to set the destination_did. Like if this is for the case where the instance has shut down, you might have some signed backup, but you probably haven't planned in advance where you would want to migrate, and if the instance is down you wouldn't be able to create the migration object after the fact.

    the validation strategy for the export is sort of mystifying to me. if the whole object is signed, then why would you need a merkle tree for objects and also an object count? if the contents of the object have changed post signing, then the signature validation will just fail and those are irrelevant.

    true to form for LLM generated documents, several critical things are left undefined, like what last_accepted_sequence is or how that works.

    probably the most important problem is that it's not really clear how all other instances are supposed to handle this, which is the entire hard part of a migration spec. Like, if the purpose here is to preserve identity, then you would need to have all the other instances come to see the new identity as being equivalent to the old identity, and there's no discussion of how that process works for third-party instances at all. like e.g. in FEP-1580 i had to spend a long time gaming out scenarios for how third party instances would handle a move event.

    so without that it's not really an account portabiltiy spec, it's an account export/import spec, which is fine, just not really needed since signing objects and collections (which this spec should use anyway) is already described by other specs.

    read more

  • @silverpillThank you , these are important corrections and I appreciate you taking the time.
    You're right on both points. I'll update the spec to reflect that FEP-ef61 authority is not actor-rooted in the way I described, and that migration is possible via outbox export-import. I was overstating the gap.
    The distinction I was trying to draw is narrower:

    read more

  • @PortaFed

    I have a couple of comments regarding the spec https://codeberg.org/portafed/portafed/src/branch/main/portafed-spec/spec.md

    It contains a comparison with FEP-ef61, but it is not quite correct:

    - FEP-ef61 identity is not actor-rooted. The closest equivalent of FEP-ef61 identity in normal ActivityPub is a server with a domain name. A single FEP-ef61 authority can manage multiple actor documents.
    - FEP-ef61 does not lack a migration flow. Strictly speaking, it doesn't need one, because data is not attached to a server and can be continuously synchronized between multiple servers. But a more familiar migration flow is also possible via outbox export-import.

    @lutindiscret

    read more

  • @benpate That would be great and happy to contribute wherever it fits.
    My guess on the scope decision is the same as yours: hostile-server recovery is genuinely harder, and a cooperative spec is already a lot to get right. Makes sense to tackle it separately.
    Take your time reading. I'll put together a short write-up of how MigrationProof could slot into the existing spec easier to react to something concrete than to an abstract pitch.

    read more

  • @jonny@neuromatch.social tracks doesn't it 😝

    read more

  • @julian
    @evan @benpate @PortaFed
    Can't make heads or tails of this one

    read more

  • Warm up the fire! We're LIVE!

    Summer in Winter: Norcal Gma 2's Journey with her Dog - E79

    #owncast #streaming #interview #fediverse #fedi #people #show #firesidefedi #FsF

    https://stream.firesidefedi.live

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    5 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
    7 Views
    Should posts with images without alt text be excluded from Trending Posts?#Polls #AskFedi #Mastodon #PixelFed #Fediverse #Trending #Images #Photos #NoAltText #Survey #Poll
  • 0 Votes
    8 Posts
    28 Views
    @stefano I guess it's Tatsuya Tanaka!
  • 0 Votes
    6 Posts
    38 Views
    In general that's a good idea because you should never trust content coming from somewhere else (even in an S2S context) For reference, NodeBB literally sanitizes the bejeezus out of what it gets from anywhere. All classes are removed, all attributes are removed. I want it as close to semantic HTML as possible, and classes/attributes mean absolutely nothing because: I don't use the same CSS classes Attributes may not follow my own rules for when and where they are added. For example, Mastodon messes with any URL it federates out. It chops the anchor text in half, hides the rest behind invisible or something, and adds an ellipsis. invisible does something different in NodeBB, so there is a CSS conflict here. I strip everything and just show the URL as it was intended.