Aura's new e-paper 'Ink' could be the future for digital framestechradar.com1 ポイント·投稿者 tomsonj·9 か月前·0 コメント
Jackal's carapace – an LLM tar spout for the Anubis web application protectorgacki.protogen.world1 ポイント·投稿者 tomsonj·昨年·0 コメント
A shirt whose price increases by 1 euro with every purchasedriesdepoorter.be63 ポイント·投稿者 tomsonj·昨年·36 コメント
Updates to the Google Photos API: Read-Only Scopes Deprecateddevelopers.google.com30 ポイント·投稿者 tomsonj·2 年前·13 コメント
Building Your Own Product Copilot: Challenges, Opportunities, and Needsarxiv.org1 ポイント·投稿者 tomsonj·2 年前·0 コメント
tomsonj·昨年·議論It seems like the requirement to reproduce this copyright header alone, nevermind the validation hash, would be enough to scare off scrapers?
tomsonj·昨年·議論whoops didn't realize this would block requests from hn after some time but in retrospect it's not surprising
tomsonj·昨年·議論very cool - made me consider the contrasts with token-bucket rate limiting for log collection and stumbled across a interesting discussion https://github.com/open-telemetry/opentelemetry-specificatio...
tomsonj·昨年·議論implementations may request the metadata range at the end in this case, if the content length is known
tomsonj·2 年前·議論it can still be an https message, who cares what the path, query string, or headers look like? that is all encrypted
tomsonj·2 年前·議論chisel is a similar tool in this space https://github.com/jpillora/chiselI don’t get why headers and requests need to be spoofed if all traffic is over https?