A lot of people in the #Fediverse are saying that Threads joining is a form of "Embrace, extend, extinguish" and IMO I don't think that's the case.
There's no need for Meta to kill this network or absorb it.
ActivityPub by design favors big servers like Meta's, it also not being nomadic (like BlueSky cough) means that users can't easily jump ship from a server they don't like.
I already see the #FediPact posts discussing leaving notable servers like Mastodon.social and it's silly IMO.
By design this whole network was built on shaky ground and when discussion of any Bluesky style improvements came up most users flipped out.
We'll be here again and again until those improvements come, if they ever come.
Reality is Meta knows they're king already and they don't need the regular users on the Fediverse.
IMO they want the WordPress profiles.
They want the illusion of freedom for celebrities and corporations.
An "open" data format they can use to get sites to integrate with their servers without signing up for an OAuth token or anything like that.
Facebook Connect used to be a big deal.
Major sites once let you comment on articles via Facebook only.
ActivityPub will let them pull that off again without the backlash of the past (no more "walled gardens").
I've already seen a few blogs that accept ActivityPub replies as comments.
Threads offering 130 million monthly active users puts Meta at the #1 spot for those comment sections now.
They could effectively ignore Mastodon, Friendica and the others and dominate by helping ActivityPub go more mainstream without making any changes or extensions to the spec.
Think about it, if ActivityPub becomes the HTML of the social web like the Mastodon community and #Fediverse as a whole dreamed of, Threads wins.
Getting linked on the mastodon network (tm). A few notes.
A while back, somebody linked to the honk manual. Within one minute, 76 mastodons retrieved the link.
I replied some time later. Within one minute, an additional 58 mastodons fetched the link.
For the day, it amounted to 150 hits, some arriving a bit later. I think not so bad, since it takes me about 200µs to serve this file from cache. It would be more problematic for a larger or more expensive file, however.
There's been some discussion of having the origin provide the preview, and the consequences of fake previews, but I think a reasonable compromise would be to have the origin check if there's a reasonable preview to be had. If the target is not a web page, tune the link so recipients don't try to generate previews.
Also, over the day, 152 hits from Pleroma and 142 from Akkoma, although those numbers are double since every GET is preceded by a HEAD. I'm not sure what happens after the head request, but that could be another way to avoid inflicting unnecessary load.
Does anyone know what #Friendica is missing to correctly generate post link previews on remote systems? #OpenGraph#Interoperability
When a Friendica post is linked on any social network, it is never possible to preview it (unlike what happens with Mastodon or Pleroma: perhaps does it depend on the absence of open graph tags?) · Issue #13959 · friendica/friendica
Potete darmi una mano, mettendo stelline a questa issue sulle anteprime dei link da messaggi Friendica?
Oppure facendovi venire qualche idea...
Infatti, i link che si riferiscono ai post #Friendica (purtroppo è anche un problema di #Misskey) non producono un'anteprima (probabilmente perché Friendica non è in grado di esporre i tag #OpenGraph, ma non sono certo al 100% che il motivo sia questo)...
Potete darmi una mano, mettendo qualche stellina a questa issue sulle anteprime dei link da messaggi Friendica?
Oppure facendovi venire qualche idea...
Come qualcuno di voi avrà notato, infatti, i link che si riferiscono ai post #Friendica (purtroppo è anche un problema di #Misskey) non producono un'anteprima (probabilmente perché Friendica non è in grado di esporre i tag #OpenGraph, ma non sono certo al 100% che il motivo sia questo)...
@hamatti@andreagrandi it's exactly that. ☝️
I added Open Graph metadata in my Pelican-based blog, and now different images show up in preview card when I share URLs ✨
You can read the HTML code from my home page as an example: 👇 https://www.paulox.net/
#Emissary is an #Fediverse client and #RSS reader. It uses page metadata (like #OpenGraph data and #MicroFormats) to make every page on the Interwebs work just like an ActivityStreams document.
It works like a cross between self-hosted #IndieWeb blogs and a Mastodon mega-instance, letting one hosting provider serve many individual sites that pool resources (like shared caches and worker queues) while remaining portable and distinct from one another.
I have a #markdown#blog where I want to use the thumbnail of a post also as #OpenGraph image for social link previews. Problem is I can't get it to work because of file path issues. This file is in the "src" folder.
Do I need to store a duplicate in the "public" folder to make this work? My blog post layout has pre-defined, optional thumbnail prop where I pass the blog posts thumbnail.
I'm interested in hearing from #ActivityPub developers who've successfully mapped #OpenGraph properties from <meta> tags in Web pages onto the Page type and its properties in AS2.
Overall, mapping to ActivityStreams was pretty easy. Sherlock is the key component in #Emissary that helps it participate in many different social webs.
Ha, it is only speculating, but Linked-freaking-In not showing the preview of @Tutanota article on choosing the best #browser (hint: #Firefox), makes me a bit suspicious of intent. Article has all the #OpenGraph data.
I dont want to be an annoying moaner, but please please please @dansup I know youre busy being brilliant but can you get a friend to correct the url for the og image property so I can tell all my FB friends how great pixelfed is when I share my photos?
Testing Pixelfed with Facebook linter. One of the best ways of publicising how good fedi apps are is to share them in other platforms - it shows their quality, unless of course it doesn't. Pixelfed.de has configured their open graph og:image correctly, but pixelfed.social has not. This is disappointing.
If you link out to most assets in #GitHub, be it a commit, issue, repo, pull request, etc., a custom #OpenGraph picture is generated for use in social media, and it looks really good, too!
There's a blog post about how they JIT generate it when needed. I'll try to find it.
Although today is not #caturday, I'm trying to test theory that an #opengraph images lighter than 300KB can break the "whatsapp sometimes doesn't share the image" curse.
Even #Facebook ❗
The only place where I and lots of people on [#stackexchange] get these problems is #Whatsapp.
Maybe the quickest fix would be to tell my friends to move to Signal :marx_thinking: