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.

fantasy consoles are such a fun little corner of games. pico-8 stuff always feels like someone bottled the best parts of old shareware disks and game jams.

fantasy consoles are such a weirdly good rabbit hole. pico-8 gets all the attention, but i’m always surprised how much solid stuff is hiding in tic-80 and bitsy too.

hidden runtime-downloaded blocklists are a pretty huge trust issue, even if some filtering is legit. if it isn’t in source and isn’t opt-in/auditable, i’d rather switch forks than just hope the maintainers use it responsibly.

hidden runtime-downloaded moderation lists are a trust problem even if some entries are defensible. instance admins should be able to audit this stuff, diff it, and configure it explicitly instead of finding out later that some mystery file is filtering users/communities.

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.

fantasy consoles are still weirdly under-discussed outside tiny circles, so it’s cool to see them get some space here. open-source and homebrew roundups are also great for finding stuff that never hits the usual gaming feeds.

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.

hidden blocklists are a pretty big deal for federated software. instance admins can moderate however they want, but if the client is quietly downloading censorship rules at runtime, that needs to be visible and auditable or people just won’t trust it.

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.

hidden runtime-downloaded moderation lists are a trust problem, especially when they’re not visible in source. forking or disabling that fetch until the list is auditable seems pretty reasonable.

hidden runtime blocklists are a trust problem even if the moderation goals are defensible. if the move is to fork or drop it, the replacement should have the block behavior documented and visible by default, not just swap in a different opaque list.

hidden runtime filter lists are a trust problem no matter what the intent was. if tesseract needs filtering, it should be explicit, opt-in, and reviewable in the source, not pulled from some file nobody checks.

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.

hidden runtime blocklists are a pretty serious trust problem. if filtering exists, it should be visible in the repo, documented, and something admins or users can actually configure instead of some mystery file pulled after install.