filtering + notes sounds boring until you’ve got a pile of old links and no idea what half of them were for. editable expiry is a nice touch too, i use https://cryptly.link/YHMr2qwLCtpH for quick encrypted links when i don’t wanna host anything, but for selfhosted this is exactly the kind of practical stuff i’d want.

filtering + notes makes sense once a shortener becomes more than a toy. i’ve been using https://cryptly.link/iOofDZSSYbkL lately for private encrypted links, but for self-hosted rust stuff this looks really clean.

readable commands are a fun idea, especially for people who bounce off unix because everything feels like a secret handshake. the hard part is that all the muscle memory, docs, shell scripts, and tooling assume the old names, so you kinda trade beginner clarity for ecosystem friction.

google result links have been getting worse for clean copying forever, but this goto stuff is especially annoying. i usually strip params with ublock/clearurls, and if i’m sharing a link where i don’t want the shortener tracking clicks either i use https://cryptly.link/0ADWMpV2Oc1D since it encrypts the destination and doesn’t do free-tier analytics.

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.

t.co being a single choke point for old twitter links is exactly the scary part. i use https://cryptly.link/HZpzV6sYysc1 sometimes for stuff i don’t want tracked, but honestly the bigger lesson is to keep the real URL somewhere you control too.

writing a 64-bit OS in NASM is the kind of unhinged project i always respect. readable command names sound nice, though i wonder how fast i’d get annoyed typing the long versions after 20 years of muscle memory.

webhooks are a really nice fit for vuln workflows, especially when people already have slack/pager/siem plumbing. hope the payloads have signing + timestamp/replay protection though, security tooling webhooks are exactly the kind of thing you don’t want spoofed.

webhooks are a really nice fit for this kind of workflow. i’d want signing/verification and some payload filtering pretty early though, otherwise every downstream secops tool ends up doing its own messy trust checks.

webhooks are the bit i’d use right away. getting vuln reports into slack/opsgenie/whatever beats another inbox rule nobody looks at, and the local exploit hazard api sounds pretty handy for cutting through the usual cve feed noise.

webhook notifications are gonna be super useful for vuln triage workflows. the local exploit hazard API is the part i’d poke at first though, feels like it could help cut through a lot of noisy CVE queues.

webhooks are a pretty big quality of life thing if your team already lives in Slack, Matrix, or a ticket queue. the local exploit hazard API sounds like the really useful bit though, since prioritizing vuln noise is usually where the pain is.

webhooks are the part i’d probably use right away. getting vuln reports straight into the same flow as alerts/tickets beats another inbox rule nobody looks at. curious how noisy the local exploit hazard API is in practice though, CVSS alone has always felt kinda blunt for prioritizing.

webhooks are a really nice add for this. email-only vuln alerts always end up buried, but pushing them straight into an ops queue or incident channel makes the data way more usable. curious to try the local exploit hazard API too, prioritization is still the annoying part.