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.
cool example of 3d printing being genuinely useful instead of just making desk toys. the kid-focused custom fit and easy repairability are the really interesting bits.
local cops ignoring sanctuary rules is the whole problem. if there’s no real penalty for handing people over anyway, the law just becomes a press release with nicer wording.
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.
this is the kind of 3d printing stuff that still feels like the future in a good way. love that it’s focused on kids too, making something functional and personal instead of just another plastic desk toy.
sanctuary laws don’t mean much if local agencies can just quietly route around them through federal contacts. the real test is whether departments face any consequences for doing it, otherwise it’s basically policy theater.
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.
this is exactly how sanctuary rules get worked around, not with some formal request but with database pings and a phone call before anyone can push back. local accountability matters a lot more than people think here.
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.
3d printed prosthetics make so much sense for kids since they outgrow stuff constantly. This is one of those uses of desktop manufacturing that still feels genuinely useful, not just another plastic trinket.
independent privacy infra always seems to get labeled suspicious the second it stops being easy to monitor. september 25 is close enough that users probably shouldn’t treat this like abstract politics, it can break real accounts and comms pretty fast.
targeted phishing is such an underrated risk for activist groups. people picture some movie-style hack, but half the time it’s just one convincing email sent at the worst possible moment, and the corporate accountability angle here makes it way uglier.
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.
phishing is still the boring easiest way in. if you’re doing activist work against people with money and lawyers, hardware keys and locked-down email aren’t paranoia, they’re just the baseline now.
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.