You can see something like this result set at octothorp.es/explore?o=demo which ingests octothorp.es/get/everythi.... Result sets are represented as MultiPasses docs.octothorp.es/blog/introdu...
You can see something like this result set at octothorp.es/explore?o=demo which ingests octothorp.es/get/everythi.... Result sets are represented as MultiPasses docs.octothorp.es/blog/introdu...
The whole point being to have protocol-as-an-endpoint. Want your results as RSS to use in a client that can understand that? cool. Want them in Semble's lexicon, to use in a client that can understand that? cool. ActivityPub, sure. lather, rinse, repeat
We do support webrings docs.octothorp.es/webrings/ but I think this data is hashtag based. But "a group of sites sharing a hashtag" is just an ad-hoc webring. It's all just graph relationships!
That goes into a big RDF graph. Right now it comes back out in fairly conventional ways (blogrolls, search results, RSS), but Publishers will be like Harmonizers for getting data out. Both are vocabulary definitions, and so are lexicons. So we're looking at ways to natively support them.
Thanks! So our protocol, OP, lets you point any URL you control at it and define a what to track as metadata (hashtags, or octothorpes, being a basic element), using a Harmonizer docs.octothorp.es/harmonizers/
u talkin about reticulum?
new strategy to motivate QA: post about features from the next next round
API response showing transformed graph data into json conformant with Semble's lexicon, purple and blue text on black background
this is unfair, because Publishers won't be released until our next, next version (which is still pretty soon) but it was very fun to throw the lexicon from Semble at our graph data and get something with a, uhh, semblance to it out via a custom Publisher. How's it look, @semble.so
Signage for "Excel Church"
"You know who else pivoted a table?"
worth noting that the frogs in the original experiment only behaved that way because they had their executive functions removed by the people running the experiment www.mmmx.cloud/after-xoxo#f...
that baby knows this blog is a real piece of shit
there are some real sloppy stakes to contend with here
Also, we are #halfbaked4lyfe but it should be noted that an _enormous_ amount of baking has happened since that dingdong's quote.
This made our day! guess we should be following the #octothorpe octothorpe more closely :)
this sweater is cool af
if you like protocols, might we recommend Octothorpe Protocol. Takes two lines of HTML and then you can start sharing tags and links with other independent sites. We're going to bridge to AT soon, so we can race to see who gets there first.
@anildash.com has written something excellent about this. www.anildash.com/2026/01/09/h...
fantastic! this will come in handy
On the other end of things, we have work on the roadmap to make OP output user-transformable in the same way, and standard.site is going to be one of our first demos on the way to ATProto integration. github.com/stucco-softw...
Thanks! we love what @standard.site is doing. That said, OP is format agnostic, so you can "adopt OP as a standard" without changing your html using harmonizers. docs.octothorp.es/harmonizers/
Also Good Internet Magazine is now on Octothorpes octothorp.es/domains/http... Was easy to add #octothorpes to @ghost.org
We're delighted to be part of the new issue of Good Internet Magazine and will be boosting any posts about GIM we see to celebrate. goodinternetmagazine.com/octothorpes-... #goodinternetmagazine
I think it's time. #soon
where my freaks at usin #bombadillo
@standard.site love what you're doing but are the definitions listed in plain text somewhere obvious I'm not seeing on the site? The definitions section is unbookmarkable and full of comments. I dug through your repo to find one to work from, but would be nice to have up front.
Basically harmonizers are user-defined mappings to normalize input to an adapter that never needs to care about the source material because it always runs it through a harmonizer.
Ah I see. Yeah, I mean do you have to rewrite your config. You might be interested in some of our tooling that we built for a similar purpose. docs.octothorp.es/harmonizers/ It's just a repackaging of RDF vocabularies, which feels relevant to Lexicons
But do you have to manually rerun the mapping?
V cool! What happens if the shape of your frontmatter changes?
everything has a json endpoint, so if you wanna cram that into a PDS we can provide a lot of the up front tooling