the remaining parts are boring and nothing new, build a frontend from the inbox and like the only difference is that instead of writing to the db you write to the PDS and like woww thats lame

in my own system i think ill put the info either in the did doc or a companion record in the user repo (itll be like uhh at://{did}/com.example.atpub.declaration/self or some other static aturi)

would be nice if theres a universally recognized way of marking an account as bridged from either side so that multiple "bridge" systems can interop

no you suck

got it working, somehow the body was undefined

i dont get it why is this not working isnt it a valid follow activity
atp.tools/at:/dw.whey....

I really only need the part where it builds views from received messages from the inbox, i dont need any of the communication parts i think

To achieve maximum apub compat i think all records need to be mirrored to AS2 form first before it gets distributed and then linked via declaration. imo the benefits of ditching AS2 is not worth the added complexity in compability with normal apub

Eh it breaks CID which is bad. I think parsing the entirety of the mirror declaration collection shouldnt be that bad, its all just backlinks right

this way the inlined data doesnt need to change, even if you create a new mirror of the same data, the only thing that changes is the mirror declaration record. all other mirrors dont need to be edited again

maybe a link to the mirror declaration record could be inlined inside all representations of the data? by making it bidirectional itll help with finding other representations of the same data and also would make it way easier to know if a record is the canon one or the mirrored one

the point of this is so that finding notes would be easier, you dont need to parse every record that contains an inlined note. also helps with resolution between representations. though it might be annoying to parse through multiple (or all) mirror declaration records just to find one link

so like instead of the ap object be embedded inside the post, it should be like a com.example.mirror.declaration record that states that a specific app.bsky.feed.post record as the canon one and a specific com.example.atpub.object.note is a mirror of it

or something like that