Thanks for the tip but I’m good. I’m not going to waste more energy fighting to read whatever CNN has to say if they take such issue with my “browser configuration”.
I got sick of some of the various Invidious instances taking 5+ refreshes to load a video, so ended up installing my own instance and its been a much nicer experience
I suspect one of the ways that Google detects the invidious instances is with the instance’s behavior: if a lot of different clients use a given instance, it makes it stand out.
Therefore using your own instance is a good way to get around that problem. I think I’ll try that as well.
Seriously worth a go, takes minutes to setup if you’re already ready for docker containers. Restart it often (dailiy is the official guidance, i find it doesnt need that with only me as user, i just do it when it starts to feel sluggish) - and I’ve put it behind a reverse proxy with auth to keep it to myself
damn, even with seeing the bot around here i forgot to try Piped these days
anyway, i’ve found a solution - i had “proxy videos through Invidious” turned on on Freetube (which was redundant since i’m behind a VPN). i’ve unchecked it and things seem fime now
The admin of Blahaj is openly interested in exposing trans people’s alt accounts and outing them on their mains. And somehow it’s the biggest trans instance. We need a community and admin reaction in favour of defederating people who do that.
If your goal is to “self-host” a password manager, you might as well use Keepass + SyncThing.
free software
master password protected
has organization and auto-fill features
can sync across multiple devices
Usually the downfall of rolling your own password manager is it’s easier to make mistakes and accidentally lock yourself out. Or if you don’t keep backups/replicas then you could easily lose your passwords.
Use kagi.com. By default it indicates pay walled sites and you can also block whole domains if you choose. Listicles are broken out separately and if you’re feeling ambitious Kagi supports regex-based redirects, so you could redirect paywalled domains to a paywall bypass website.
Im concerned that adopting kagi is just taking your data back from multiple greedy corporations and giving it to one corporation instead, and also giving them a direct link to who you are via your payment method.
But why? Is there a compromise taken on privacy in favour of visibility and mass adoption of whatever fediverse client they’re using? I don’t understand this, especially since I also find the strongest advocates for privacy right here.
A lot of Lemmy adopters joined with rose tinted glasses, and came with a lot of good ideas, like getting data out of the hands of big companies, making it easy to access it (as Reddit locked down APIs), etc. Which is all good, but a subset of them believe “not officially belonging to one company” is good enough. As for how your data is handled online, a subset of them believe nothing can be improved, and a subset believes it shouldn’t be improved because your data shouldn’t belong to you at all.
And Lemmy is made up of all sorts, so there’s overlap between Reddit refugees and diehard fans. That interaction is a lot more implicit here, but the friction is a lot more visible on sites like Mastodon where similar privacy discussions have been happening.
I’ve not seen any of these arguments. Though it may be all downvoted to hell and back.
My main gripe with adding privacy features to Lemmy is that the whole point of Lemmy is that all data is already publicly available and for Lemmy to continue working the way it does it’ll need to remain that way. And because of that there’s nothing that can be done to stop bad actors setting up an instance and selling all the data they collect.
At least in the EU (and UK to a lesser extent) no major corporation would be able to get away with selling that data, so the spent man hours on allowing privacy settings would be wasted time.
It doesn’t necessarily need to remain that way. For example,we should have the option to make our profiles private. We should also be able to create pseudonyms for content we submit. The content will still be federated, but not necessarily linked to one user ID
The only privacy setting I can encourage on any social media site is don’t share private stuff about yourself and never link to your account from other accounts
That is part of the problem though. Proper privacy allows you to express what you want to, without self censorship. The issue is not: don’t speak about x, but rather: speak about it and feel comfortable that you can do it in a safe environment. I fully agree with the account linking though
I think no one has mentioned the base for all the cryptographic functions. A mathematical operation which is simple in one direction but very hard in the the other (backwards). The factorisation of large prime numbers is one example.
I’m satisfied with the answers and insights I got so far. But if you may add I’d be happy to know why factorization of prime numbers is so crucial in cryptography. I heard about this a lot before but don’t know anything. I know quite well about Prime number and theorems about them on math, but not their applications
Calculating primes is fairly straightforward so you calculate a few large prime numbers, and do some math to them.
Now you have a strong key that didn’t require a supercomputer to create but taking that final number and turning it back into those original primes is a much more computationally expensive proposition.
In fact, it’s one that’s not viable with current technology.
privacy
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.