I sat down with @snarfed.org to talk about his work around the #fediverse, the #indieweb and the #atmosphere including (fed.)brid.gy and @anewsocial

I sat down with @snarfed.org to talk about his work around the #fediverse, the #indieweb and the #atmosphere including (fed.)brid.gy and @anewsocial

Connecting Decentralized Social Networks and Rethinking Interoperability

Join Matthias Pfefferle as he chats with Ryan Barrett, the mastermind behind Bridgy and BridgyFed, bridging decentralized networks like IndieWeb and Fediverse.

Open Channels FM (openchannels.fm)

#podcast #activitypub #atproto #bluesky

@pfefferle @snarfed.org @anewsocial hi, just fyi: this broke my Mastodon timeline, as the quoted post contained the complete transcript.

@janeckhoff what client do you use?

@pfefferle Very interested in this interview!

I have a consistent problem w/ WP blogs using the AP plugin where they return a JSON representation when requested in the browser. Is there anything i can do about this?

@pfefferle IceCubes on iOS

@pfefferle @snarfed.org @anewsocial

Posting sentire novels on the Fediverse is not a good idea.

The quoted post is like fifty screens long. Posting like that is hostile to the reader.

@ted this is a caching issue. should be fixed now.

@seindal true, but not properly handling "novels" as a client is hostile to the reader too... the fediverse is not only microblogging!

I will work on improving the handling, but I plugins do unpredictable things sometimes. like for example adding trasnscripts to the content through a filter.

@pfefferle Thanks! Out of curiosity is there a root cause to it? I've had this issue several times w/ Laurens Hof's connected places site as well.

@ted wordpress caching does not support content negotiation by default. it caches what was requested and returned. if mastodon requests the page content in JSON after it was federated, the cache would take this response and cache it. so either you disable caching or you disable content negotiation for user facing sites.

@pfefferle ahhh i get you. that's a bummer. Thanks for the info!

@ted you're welcome

It is not always easy to deal with the WordPress beast

@seindal this sounds like your reader needs fixing / a "Show more" feature.

Seriously. There is nothing in the spec that says "must not use more than 500 characters" or something. This is one of the *strong* points of the Fe*diverse*.

@janeckhoff I will check with them to maybe truncate the quotes!

the weird JS output is already fixed and will be published with the next release. I will also how to limit the podcast episode to the summary!

sorry about that!

@seindal https://github.com/Automattic/wordpress-activitypub/pull/3065

@pfefferle that sounds great, thanks — I honestly didn’t realize you were exactly the right person to address this bug at its root tbh, I merely thought that maybe you want to edit your post if you‘re made aware of this problem

@janeckhoff

@pfefferle @snarfed.org @anewsocial excited to listen now!

fyi heres how your post looks in @phanpy / the latest version of mastodon

WordPress sometimes returns JSON to a Webbrowser instead of the HTML page. · Issue #580 · Automattic/wordpress-activitypub

Quick summary Sometimes and for some users WordPress returns a JSON object to a regular browser request interested of the normal website. This (sometimes) persists on reload Steps to reproduce No idea 🤷 What you expected to happen The no...

GitHub (github.com)

…and to clarify, that was the default behavior, but afaik the plugin was updated to support both caching and content negotiation together.

on a related note, content negotiation sucks https://snarfed.org/2023-03-24_49619-2

@quillmatiq you should post about this on the @anewsocial account!