I would like to give an update on "federation" on Bluesky

[mcc@mastodon.social]

@erincandescent I have an entirely workable proposal for how to achieve that in a distributed system, which the mastodon dot social post length is too small to contain

[esoteric_programmer@social.stealthy.club]

@trwnh @lrhodes @mat @mcc @alter_kaker This is offtopic in a way, but oho, I didn't have to look too deeply to find this:
https://github.com/qwell/bsky-exploits
nothing extremely serious, but could be used for fishing campaigns and the like pretty easily

[ireneista@adhd.irenes.space]

@mcc @erincandescent we should sync up about that at some point, we've thought about it also and it'd be a shame to never turn it into a spec

[ireneista@adhd.irenes.space]

@mcc @erincandescent the historical answer to why atproto isn't using traditional PKI, as far as we can tell, is that the authors were under the impression DID is a lot more useful than it is. just a guess on our part.

[rakoo@blah.rako.space]

@trwnh

No, the bittorrent DHT has methods to update content sent in the DHT with no need for a PKI: https://bittorrent.org/beps/bep_0049.html

@erincandescent @ikuturso @mcc @jrose

[tylercook@mastodon.gamedev.place]

@mcc I do, yeah. So it's just one part of the stack. The complicated parts come later, eh?

[mcc@mastodon.social]

@mat @eniko There is already such a Wordpress plugin that publishes to ActivityPub. I believe publishing a Wordpress or other blog as a PDS would be even easier than ActivityPub. All the ATP single-link APIs are very simple and almost even well documented. So the fact this sort of thing (PDS frontend to legacy data source like Wordpress) does not exist is I think a testament to the fact most people in a position to create such things take a look at, and cannot see the benefit of, ATProto interop

[mcc@mastodon.social]

@mat @eniko Another thing to note. Posts on ATProto are 300 characters. The entire system is set up to mark "schema invalid" and wholly censor any post which is more than 300 characters. So what you'd have to do is put a 270 character summary of your post, plus a link to your real wordpress, into the PDS. (It's not a schema violation to contain *extra* data, so you could include a "full-text" field in the post blob, but no system in existence could read it— not even yours, you'd be publish-only)

[mcc@mastodon.social]

@mat @eniko So at that point, barring building an entire alternate Bluesky-like system for reading longposts— a system which would be redundant when ActivityPub exists— you're not mirroring your WordPress on Bluesky, rather you're using Bluesky as a funny kind of RSS feed, posting a short announcement of each post there… at which point, isn't it easier to just link your WordPress to a *regular* bluesky account, and use the API to auto-post summary+announcements for new posts?

Am I making sense?

[thisismissem@hachyderm.io]

@mat @mcc @eniko I think you'd be hard pressed to implement AT Proto in PHP tbh..

Edit, to expand on that: AT Proto requires a bunch of cryptography (for keys and dpop and such), and websockets for the sync part of the protocol (which is how relay's typically hear about your posts)

[silmathoron@floss.social]

@gunchleoc the Bluesky addon for Friendica is here [0], I haven't had time to check how it works... name suggests it would use the Bluesky PDS and I've seen issues about Bridgyfed on the issue tracker, so not sure whether that's what's used to post or not.
[0]: https://git.friendi.ca/friendica/friendica-addons/src/branch/2025.07-rc/bluesky
Do you have a link about Hubzilla? I haven't seen anything about ATProto compatibility
@gbargoud @mcc

[dalias@hachyderm.io]

@mcc @erincandescent I have a system that doesn't need blockchain. Instead it uses a "nocoin" (term I coined, pardon the pun) distributed notary system that doesn't have a ledger because there's no way to enumerate things that have been recorded, only to prove that a particular thing was seen by a notary at a particular time.

[mcc@mastodon.social]

@mat @eniko "but where are replies to those posts coming from in this setup?"

Short version: "You can't get them"

Long version: Currently the only ways to get replies to a post published in your Bluesky PDS are

- Run a "relay". This means (this is not a joke) receiving from Bluesky PBC a copy of literally every post made in the network, and filtering for ones that @ you.

- Log in to bsky.app (or a clone like blacksky) with your PDS username and password, and look in the notifications tab.

[gunchleoc@mastodon.scot]

@silmathoron @gbargoud @mcc Might ne Friendica only, I was writing from imperfect memory.

[mcc@mastodon.social]

@mat @eniko Now, that last thing is possible, and even easy. But at that point it's really, super unclear *why* you would architect your Wordpress server to *be* a PDS, rather than running the regular PDS software on the same box, and having the Wordpress server post to it from time to time using the external API. It's extra work, but there's no obvious advantage and there's barely even a difference.

[dalias@hachyderm.io]

@mcc @erincandescent The concept is that you intentionally preclude the possibility of detecting "double-spend" so that the system can't be used for exchanging things of value. As a bonus, this also precludes selling identities. It's impossible to prove you're not keeping hidden an earlier-dated transfer to a different new owner when you offer to transfer an identity for money.

[thisismissem@hachyderm.io]

@mat @mcc @eniko you could probably take the bluesky-social/pds repo, and add in endpoints that a wordpress plugin would call to automatically create records in it for social posts, if you just wanna distribute out a app.bsky.feed.post for each wordpress post.

That'd be pretty easy to do.

[mcc@mastodon.social]

@mat @eniko Isn't it convenient that Bluesky has architected an "open" system where the solution to every problem turns out to be "use Bluesky", and any other solution requires fighting incredible gravity?

[thisismissem@hachyderm.io]

@mat @mcc @eniko yeah, because you need sync, afaik. https://atproto.com/specs/sync

[mcc@mastodon.social]

@mat @thisismissem @eniko The continuous event streams are HTTP. Mine are being proxied through Apache