NodeBB-ActivityPub Bridge Test Instance

@trwnh TIL but for «things I learned» instead of «today I learned»

@trwnh oh good point, so if it's done by GET it *must* include the query parameters in the URL. And yeah, now I can see better why POST would be a better choice.

@trwnh hm I'm not convinced. The main issue is that neither POST nor PUT are conceptually appropriate. Among the methods defined by HTTP, GET is the one that's conceptually closest. OTOH, those *are* problems with using a query string. Maybe they could be reduced by other means, such as additional headers or body payload (GET *can* have a payload)

@trwnh doesn't that kind of depend on the type of form? Classically for a something like a search GET would be a more appropriate method than POST or PUT …

@trwnh am I reading it correctly that it sounds a bit like how the eDonkey network works? You can connect to any server, and then search for resources (file hashes in that case) and you'll get a more or less uniform view of the network anyway, modulo massive netsplits?

@trwnh OK, but the ID still needs some crytographic element to allow keys to prove controllership of id? Or how would a key be used to prove control?

@trwnh this BTW is also why I'm not to fond the RNS idea (same issue as with DOI and PLC), unless again it's “distributed first” (hence the Kademlia idea). I'm not sure why you're opposed to keys as IDs, but whatever the choice is, it should still provide some key information simply to ensure validity.

@trwnh sorry, I didn't meant it like that, I meant it in a way similar to how DOI works in the sense that the URI could exist without the doi.org domain, and the doi.org domain is essentially a proxy to resolve doi: URIs into HTTP URLs. I think the DID idea could work in a similar way, which is what I think the PLC DID from BS is intended to be, but I'd like it to be “decentralized first”, with the HTTP proxy only useful for the transition.

@trwnh I think that's part of the reason for the choice to go with a different protocol. I guess you could still have some kind of proxy service like there is for DOIs: you have an URI that is doi:prefix/suffix and then you have the HTTP proxy https://doi.org/prefix/suffix that redirects to the known HTTP URL of the document. We could have a similar scheme, but only as long as alternative resolution mechanisms are also provided.

@trwnh if you want resource identifiers to remain valid, you have to decouple their URIs from any specific HTTP URL. You don't necessarily need a centralized system, though. The Portable Objects proposal https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md introduces a new URI that includes a “gateways” parameter that acts as location hint (multiple ones may be present) piggy-backing on DNS. But that's probably too big a change.

@trwnh at least two out of three would be fixed by

https://wedistribute.org/2024/03/activitypub-nomadic-identity/

@bmordue @trwnh

Also, none of them does what I would like, which is to use a database only for speed, but actually store the objects as .json files on disks, ideally with an actual XML RDF counterpart to go with them, but that's a different matter.

@bmordue @trwnh I think it's faster to tell you what they DO have that I like.

Streams has a way to effectively implement nomadic identities on top of ActivityPub. But until/unless the FEPs to standardize it <https://wedistribute.org/2024/03/activitypub-nomadic-identity/> gain wider adoption, it's the odd one out with it.

Vocata is exactly what I would expect from an AP server: completely content agnostic, simply fills the graph. But it has no UI.

GoToSocial seems to be the simplest to self-host for single users.

@trwnh I have a similar issue. I really want to self-host, but I'n not satisfied by anything that exists today. I'd need something like a cross between Vocata, GoToSocial and Streams

@trwnh that's essentially how “quote boosts” are supposed to work, and was the idea behind ping backs and webmentions

@trwnh @erincandescent @thisismissem @helge it always comes back to being strict about what you produce and liberal about what you accept

@trwnh I've seen some of the samples later (sorry for forking the thread), and it seems most of that stuff you want to do is actually supported natively by AsciiDoctor, but I think I see your point. I'm not familiar with goldmark, but I'm getting the impression that it's something similar to what Jekyll with their {% %} escapes, except that this happens “during” rendering with a callback to Go or something like that? Yeah, I can see how that's a feature one wouldn't like to go without.

@trwnh wait shouldn't it be the other way around? It's up to Hugo to support asciidoc as a rendering engine? I don't use Hugo but last time I checked the docs while looking for an alternative to Ikiwiki I think I read it did support it? Or am I missing something?

@trwnh (ah, and this is NOT a “you should be using AsciiDoc BTW” post, BTW 8-D)

@trwnh FWIW, personally I'm getting quite tired of Markdown limitations, and have been using AsciiDoc(tor) more whenever I can. Of course It has its own set of limitations, but for example it has this generic “span” markup that allows thematic customization (e.g. one can do [.strike]#x# and define a CSS class for strikethrough —could even be more semantic than HTML's <s>).