NodeBB-ActivityPub Bridge Test Instance

anyway some links to ones i found interesting or remotely noteworthy:https://datatracker.ietf.org/doc/rfc6648/ -- deprecates the use of "x-" and similar "experimental" prefixes, for causing more interop problems than they solvehttps://datatracker.ietf.org/doc/rfc2360/ -- guide for standards writershttps://datatracker.ietf.org/doc/rfc9205/ -- building protocols with http

@scott one strategy is to say it's always 200 OK for the document for the homepageanother strategy is to check for Accept headers and if it's a linked data serialization, then return 303 See Other and list all possibilities (me, my-homepage)there are other strategies and they mostly depend on how you want to configure your web server and where you want to store the backing files/documents

@xrisk before you get to that point, you might first ask for a Thing and then the server tells you "sorry, i can't serve you the thing itself, i can only serve you something related to the thing like a descriptor document" (this is what 303 See Other does)then you ask for the Other and the server tells you "oh i have this Other, but in multiple formats" (this is what 300 Multiple Choices does)using an HTTP Accept header lets you skip the second step but not the first

@djsundog @codl there are two additional ironies that i couldn’t include in the screenshot:1) this is one of those email notifications where a company reaches out like “hey we saw your profile and thought you might be interested”2) the company in question for this job listing is Indeed

ok i still have 9gb that idk where it came from. ncdu says this/var 18gb/usr 4.6gb/srv 4.5gb/swapfile 4gb/home 1.9gbmost of those are expected but /var is usually only 8gb or somy akkoma db is 4gb and its wal is another 4gb, so that looks kinda weird/var/lib/docker/overlay2 has 7.8gb which is also weird it's usually like 2.1

@codl look i just really like math even when it hurts me

@scott so on further reflection, in some ways, the thing i was shitposting about might actually come to pass sooner than 20 years.

@scott similarly, some other group might try to go off and do the equivalent of what XHTML was to HTML -- let's say "ActivityStreams with Schemas" -- and they could end up being about as relevant as XHTML is today. or not. who knows