glad you got it working for you (and I should probably update it to wildcard kbin.social, with that in mind)! I think your observation is right on the mark because my homepage is all, or /
Kbin does have tags for the language of posts, and they are accurately represented in these German posts, but I can't find a way to filter them without just blocking the server!
As a quick fix, a user script:
// ==UserScript==
// @name Kbin: delete articles in other languages
// @namespace http://tampermonkey.net/
// @version 0.1
// @description Auto-delete posts in languages you do not speak.
// @author luphoria (https://kbin.social/u/trent)
// @match https://kbin.social/
// @icon https://www.google.com/s2/favicons?sz=64&domain=kbin.social
// @grant none
// ==/UserScript==
(function() {
'use strict';
const allowedLangs = ["en", "es"]; // Edit this to all of the languages you can speak / want to see in your feed
let deleteUnwantedPosts = () => {
const postTags = document.getElementsByClassName("kbin-bg");
for (let i = 0; i < postTags.length; i++) {
let postTag = postTags[i];
if (postTag && postTag.textContent && postTag.textContent !== "OC" && !allowedLangs.includes(postTag.textContent)) { // OC tags are the only elements (i know of) with the same class.
// Delete element's parent's parent's parent
if (postTag.parentElement.children[0].textContent) {
console.log(`Removing post labeled \`${postTag.textContent}\`: "${postTag.parentElement.children[0].textContent}"`);
postTag.parentElement.parentElement.parentElement.remove();
}
}
}
}
deleteUnwantedPosts(); // on load
// for continuous feeds
let observeDOMChanges = () => {
const observer = new MutationObserver(function(mutationsList) {
deleteUnwantedPosts();
});
observer.observe(document.body, { childList: true, subtree: true });
}
observeDOMChanges();
})();
I'm also disappointed that we now have AI browsers, which is scary and not a good direction to go in.
Out of pure curiosity, why do you say this? In context of something like ChatGPT, it makes sense, but what do you think about stuff like local LLMs as assistants and embedded in browser infra?
You probably saw some (mostly fraudulent) ads. Dread is where most of Tor's public content can be found; but, yeah, crypto (specifically Bitcoin and Monero) are the standards there.
FHE solves that through and through, as has been documented widely, but that's overengineering when you could just use plain ZKP.
Zero-knowledge voting is here and has been for a while now.
The stuff listed in OP doesn't really seem like much concern. "What you put on the internet is there forever!" is completely true, and things like this should only make it more concrete that you can't rely on your service provider to delete information somebody else already archived.
With that being said, default privacy settings - at least on Kbin - seem pretty bad.
I thought votes didn't federate yet anyways... but, yes, it is possible, and i can come up off the top of my head with three or four potential implementations.