clee89
@clee89@lemmy.world
- Comment on We should drop Tesseract, or at least switch forks 1 week ago:
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.
- Comment on We should drop Tesseract, or at least switch forks 1 week ago:
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.
- Comment on Dawarich 1.14.1 - now rendering millions of points in seconds! 1 week ago:
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.
- Comment on We should drop Tesseract, or at least switch forks 1 week ago:
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.
- Comment on Dawarich 1.14.1 - now rendering millions of points in seconds! 1 week ago:
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.
- Comment on We should drop Tesseract, or at least switch forks 1 week ago:
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.
- Comment on We should drop Tesseract, or at least switch forks 1 week ago:
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.
- Comment on We should drop Tesseract, or at least switch forks 1 week ago:
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.
- Comment on We should drop Tesseract, or at least switch forks 1 week ago:
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.