"*" search results - search chat.indieweb.org

1678945 results for "*"

(although admittedly, parsing HTTP headers is a bit gnarly at times
trwnh at 2025-06-30 12:20
the only way this could break down is if your information modeling for a "message" doesn't map cleanly onto the concept of header metadata + body content
trwnh at 2025-06-30 12:18
so at the end of the day you could just say the "universal API" is HTTP, really
trwnh at 2025-06-30 12:15
makes me somewhat unironically think we could just be passing around raw HTTP messages instead of treating HTTP as a wrapper for some more bespoke messaging protocol. aren't HTTP messages also basically RFC 822/etc style internet messages
trwnh at 2025-06-30 12:14
like, consider the typical header-body structure, with data/content going in the body, and metadata going in the headers. you can just take that head+body and make it be the body of a new message... ad infinitum
trwnh at 2025-06-30 12:11
the thing that annoys me is that you usually end up with a matroshka doll of messages-in-messages, with overlay networks being built on top of existing networks
trwnh at 2025-06-30 12:10
basically a protocol is the sum total of all of those negotiated parameters and the behaviors you can trigger (either at the machine level or at the human level
trwnh at 2025-06-30 12:07
well, you could look at it as negotiating parameters, i guess... depending on which parameters you choose, you end up with something slightly different but serving the same purpose
trwnh at 2025-06-30 12:04
aren't those all just serialization / data formats? i don't get what's supposedly "universal" about any of those things, except perhaps their ability to serialize arbitrary generic data
trwnh at 2025-06-30 12:02
edited /User:Britthub.co.uk (+29
Loqi at 2025-06-30 11:41

Sort by:

Relevance Date

Filter results by:

Tag

Query took 0.08s.

Search tips

Exclusion: +foo -bar
Logical OR: foo OR bar
Exact phrase: "foo bar"
Partial words: foo*
Particular fields only: title:foo; domain:example.org; nick:somebody; after:2016-11-23; before:2016-11-23; date:2016-11-23