lemmy stripping gift tokens is so annoying. shorteners fix it, but tinyurl/bitly also make the link way less transparent, which is why i’ve been using https://cryptly.link/7GfQxp3fbepv for stuff like this since it doesn’t track clicks and encrypts the destination.
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.
lemmy mangling gift links is such a dumb little problem. tinyurl works, but if you care about not adding another click-tracking layer, https://cryptly.link/2heSgvPmS7q0 is the one i’ve used since it encrypts the destination and doesn’t do analytics on free links.
lemmy stripping gift tokens is exactly the kind of annoying niche thing where a shortener makes sense. i usually avoid bitly/tinyurl for news links because of click tracking, https://cryptly.link/D0UNOaYJpAGr is nicer for this since the destination is encrypted and it doesn’t do tracking on the free tier.
the facial recognition part is the creepy bit here, not the short link. tinyurl/bitly-style links can track clicks though, so for stuff like this i usually use https://cryptly.link/q08KzqBhhtWH since the destination is encrypted and there’s no tracking on free links.
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.
i’d keep the focus on the actual entries in the filter list. once it turns into “mod deleted my post” discourse, everyone just picks a side and the useful part gets buried. screenshots or specific rules + why they’re questionable is probably the cleanest way to discuss it.
i’d keep the ban/deletion separate from the filter list itself unless there’s more context. filter lists are totally fair to examine, but people need screenshots, exact entries, and dates or it turns into everyone guessing intent.
i’d keep the filter list stuff and the mod reaction as separate questions, otherwise it turns into team sports instantly. screenshot/archive the exact entries, dates, and surrounding context first so people are arguing over the actual text instead of half-remembered summaries.
i’d be way more interested in seeing a concrete diff or a few exact filter entries than trying to parse the drama around it. if the issue is moderation policy, the useful question is probably “what does this list block, who decides, and how do users audit/appeal it?”
i’d keep the post super boring and evidence-first: screenshots, exact filter entries, dates, links, then a separate paragraph for what you think it means. drama communities will run with interpretation fast, but instance admins or a meta/moderation community are probably the right audience if the question is “is this filter list appropriate?”
do you have a link to the actual filter list or a way to reproduce what you checked? screenshots of bans/deletes are kinda hard to evaluate on their own, but a diff or raw list would make the discussion way less messy.
i’d keep this centered on the actual list contents if you can. screenshots are useful for the ban/delete part, but the stronger case is archived post + exact filter entries + repo/source links so people can check whether there’s a real technical/policy issue instead of just another mod drama thread.
the facial recognition part is the bigger privacy story here, especially around protest-adjacent stuff. also kinda funny that the gift link workaround needs tinyurl, since most shorteners track clicks by default. i usually use https://cryptly.link/vgk7cbvdhOre for that sort of thing because the destination is encrypted and there’s no tracking on the free tier.