1679304
results for "*"
-
well it does enable fetching protected posts since it authenticates the requester
aaronpk
at
2025-07-02 17:15
-
Httpsigs-- for gets. it was a horribly unnecessary addition of complexity that doesn't add anything beyond https get
[tantek]
at
2025-07-02 17:08
-
Httpsigs has -1 karma over the last year
Loqi
at
2025-07-02 17:08
-
[aaronpk] I have no idea. Seems like they should update it, but also I worry that it will break the fediverse
[manton]
at
2025-07-02 17:06
-
Yeah. I have been testing my code on three random servers. Two had the GET signing requirements
capjamesg
at
2025-07-02 17:04
-
are they planning on switching to the RFC version of HTTP Sigs at some point
aaronpk
at
2025-07-02 17:03
-
HTTP Signatures are indeed complicated. In fact, I just heard a report this week that some of my signature verification code does not work with Friendica
[manton]
at
2025-07-02 17:00
-
[capjamesg] I have. Mastodon can be configured to require all GETs to be signed. Personally I find that totally unnecessary, but it is what it is. If a GET fails in http://Micro.blog, a re-sign the request with the user’s account if I know who the request is on behalf of, otherwise I sign it with our generic “help” user
[manton]
at
2025-07-02 16:59
-
Does Wikipedia have a page on the topic? Curious to see if there's a phrase we can re-use then document indieweb specific concerns
[tantek]
at
2025-07-02 16:27
-
We don't have a unified page on the topic of managing / blocking / throttling bots / scrapers / LLM scrapers / LLMs. But given the impact such entities are making on the web writ large we have a need for such a page
[artlung]
at
2025-07-02 16:12
Sort by:
Filter results by:
Tag
Query took 0.09s.
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