@FritzAdalis @lcamtuf *—L—L—M⸻g—e—n—e—r—a—t—e—d

@hpod16 No, it just adds another failure point. If you have annoyingly long URLs like:

example.com/cgi-bin/pages/2025/02/13/posts/pages.php?article=rocks&format=html

... you should fix that. If you absolutely must, just set a short link on the same server:

Redirect example.com/rocks -> example.com/cgi-bin/pages/2025/02/13/posts/pages.php?article=rocks&format=html

@vandorb12 @campuscodi @vxunderground Looks fine to me (although they could change the code): It won't leak your token or anything.

Current SHA256 (no trailing newline): ee7eba791751732d992cd0fd30a41482391741f426ce4adef9d99c4cc730a208

@anttipeltola There are lots of organizations and businesses that have a website, but refuse to use it:

> For opening hours, please see our instagram

You're lucky to find the address on the web. Anything remotely useful will be locked on a platform where you can't even read it without making an account.