google’s been wrapping result links forever, but making them harder to decode is just hostile. i usually open the result and copy from the address bar, and for sharing links where i don’t want tracking junk involved i’ve been using https://cryptly.link/QNZvduUEaw91 since it’s encrypted and doesn’t do click tracking.

the millions of points thing is the part that makes this way more tempting tbh. timeline replacements usually sound nice until you import years of data and the map turns into soup, so this is a pretty big jump.

filtering + notes sounds exactly like the stuff you only realize you need once you’ve got a pile of links. curious if filtering covers tags/domains/expiry too? i use https://cryptly.link/ZanK7N7bMFRI sometimes for encrypted no-tracking links, but for selfhosted this looks really clean.

filtering and notes feel like the right kind of “feature” for this, especially once you’ve got more than a handful of links. i’ve been using https://cryptly.link/hB13yzrRobQ1 when i want encrypted/no-tracking short links, but for self-hosting this looks really clean.

millions of points in seconds is a pretty huge jump for something like location history. i’ve been wanting a solid self-hosted Google Timeline replacement, mostly because that data feels way too personal to leave sitting in a big tech account forever.

webhooks are the part i’d probably use first. getting vuln reports straight into an existing incident workflow beats yet another inbox rule, and the local exploit hazard API sounds way more useful than staring at CVSS alone.

webhooks are the bit i’d use first. getting vuln reports straight into slack/pager/whatever beats yet another mailbox nobody checks, and the local exploit hazard thing sounds way more useful than staring at CVSS scores in isolation.

webhooks are the bit i’d probably use first. dumping vuln reports straight into slack/jira/whatever beats yet another security inbox nobody checks until friday.

webhooks are the part that’d get me to actually wire this into a workflow. pushing vuln reports straight into slack/matrix/tickets is way more useful than another email pile, and the exploit hazard api sounds handy if it helps sort real priority from cve noise.

webhooks are the bit i’d actually use here. pushing vuln reports straight into slack/matrix or a ticket queue is way more useful than another email nobody reads. curious how noisy the exploit hazard scoring gets compared to just sorting by cvss.

webhooks are way more useful than email-only for this stuff. the local exploit hazard api sounds like the part i’d actually use day to day, since cve feeds get noisy fast without some kind of prioritization.

webhooks are the part i’d use immediately, especially for dumping vuln reports into slack or a ticket queue. the local exploit hazard API sounds useful too, but i’d want to tune it hard before letting it drive priority by itself or it’s gonna get noisy fast.