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

378668 results for ""a""

XML-RPC when used as a write protocol, creates security problems
[tantek] at 2025-06-30 17:42
To trwnh's point, XML-RPC is a great example of "you could have just used HTTP"
[tantek] at 2025-06-30 17:41
[snarfed] I think the "designed to be machine readable" is a trap because format that has strings ends up with user visible strings in it (which is where JSON fails i18n)
[tantek] at 2025-06-30 17:37
XML-RPC is going to be with us for a loooong time. 🙂
[manton] at 2025-06-30 17:37
I think it's less interesting as a technology "Universal API" and more interesting that it's encouraging more open API development
[aciccarello] at 2025-06-30 15:53
yeah, that's what I find. press release lists, certain kinds of groups of written pages generate rss. I've added a few more patterns for platforms / rss feed urls at https://smorgasborg.artlung.com/?filter=rss
[artlung] at 2025-06-30 15:46
It does remind me a lot of the Web 2.0 days of the early "open API" wave where everything was going to have an API
aaronpk at 2025-06-30 15:19
Yeah it's definitely a stretch to call it a universal API, but one thing that could come out of it is more things having APIs in the first place
aaronpk at 2025-06-30 15:18
(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

Sort by:

Filter results by:

Tag

Query took 0.03s.

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