No, the https://www.w3.org/ns/activitystreams#Public is just there to indicate that it's ok for receiving instances to display this publicly, nothing actually gets sent to it. See the spec for more details.
Alice can't make a post to B, but I assume you mean a community on B, let's call it foo. When Alice makes a post it first goes through A's local API and creates the local (and canonical) version of Alice's post. Once A has finished processing Alice's post, it will create an ActivityPub representation of Alice's post to send to B.
ActivityPub is basically a bunch of assumptions laid on top of JSON. An ActivityPub 'file' can be divided into broadly 3 types, Object, Activity and actors.[^note1] These types then have subtypes; for example, both Alice and foo are actors but Alice is a Person while foo is a Group.
A second important assumption of ActivityPub is the concept of inboxs and outboxs, but, for Lemmy, only inboxs matter. An inbox is just a URL where Lemmy can send activities and it's something all actors have.
So when instance A is finished processing Alice's post, it will turn it into a Page object, wrap that in a Create activity and send it foo's inbox.
Now instance B will then receive this and do the same kind of processing A did when Alice created the post via the API. Once it has finished, it will turn the post back into a Page but this time wrap it in an Announce activity. B will then look at all the actors that follow the foo (i.e. are subscribed to it) and send this Announce to all of their inboxs. Assuming a user on instance C follows foo, it will receive this Announce and process it like A and B before it, creating the local version of Alice's post.
Edit: I made a small mistake, I said that foo wrapped the Page in an Announce, when it actually wraps the Create in an Announce.
[^note1]: Technically, Activity and actors are themselves objects, but they're treated differently. There's also Collection's which are their own type, but Lemmy doesn't really utilise them.
We recognise that this Annual Report for 2023 is arriving later than we had intended. Going forward, we plan to release our Annual Report for 2024 in Q1 of 2025, where we will establish clear and ambitious goals for 2025 and beyond. This adjusted timeline allows us to provide more timely insights and better align our reporting with our ongoing growth and development.
They don't strip out the markdown on the bluesky side, so posts are just full of junk. Weird choice given the focus on 'seamless' integrated between the two.
It's because YouTube puts a bunch of JavaScript at the start of the file (1MiB) before the opengraph tags and Lemmy only fetches the first 512 KiB (a fix was merged a couple days ago).
It seems the bridge didn't see the reply. Might be something worth making a bug report about. (Also, ignore the update profile entry, I clicked the icon by accident)
It has an algorithm that puts content in front of you, unlike Mastodon where it only puts what you ask for in your feed. I'm convinced that if Mastodon populated people with low following count's feed with random posts it wouldn't have bled as many users as it did.
You can go to the trouble to learn Rust, and then fight with them to get your modifications accepted or...
Can you actually point to any instances of the devs dragging their feet on accepting changes or is this just conjecture? I've contributed to Lemmy, and plan to do so in future, and my experience is that they're fairly accepting of changes.
We could do what I think you’ve done, and regex the details of the attachment into ! [] ()
To be clear, this pull request doesn't use regex, it's just JSON deserialisation and string interpolation.
I’ve never actually seen a Mastodon user try to add an image to something that ended up as a Lemmy comment, tbh, so it’s not something I’ve thought too much about.
The pull request actually includes one, the main KDE account tags !kde@lemmy.kde.social and includes pictures in their threads regularly. It's just hard to tell from our side as you can't see what's missing.
.ml is running the beta branch that actually started to apply image size limits to thumbnails, your app is probably using the thumbnail URL instead of the main URL and thus getting the compressed image.
This is straight up misinformation, Dorsey was on the Bluesky's board, but left in May. As far as I'm aware, he's never even invested in the company (but he has given money to the nostr devs).
No, the
https://www.w3.org/ns/activitystreams#Publicis just there to indicate that it's ok for receiving instances to display this publicly, nothing actually gets sent to it. See the spec for more details.