Azzu

joined 1 year ago
[–] [email protected] 29 points 8 months ago

The lawsuit says that they think exactly what you're talking about is unlawful according to the DMCA. Let's see how it goes.

[–] [email protected] 1 points 8 months ago (1 children)

I had a few legacy apps on the paid store, and everything works on my /e/os without any Google, I'm not sure what does it, but I have Aurora and microG

[–] [email protected] 2 points 8 months ago

I use the default desktop KeePass client (no Xs or whatever) and it always synced correctly and picked up abd merged changes.

[–] [email protected] 5 points 8 months ago (2 children)

I just use Keepass2Android. You can use any solution you'd like that is able to sync normal files and sync your database between your devices

[–] [email protected] 10 points 8 months ago* (last edited 8 months ago) (1 children)

Because it sounds conceptually nice to good people, but selfish people know that without proper transparency and checks, it's very easy to consolidate power with it.

So the bad people get the support of good people and then exploit that flaw to do what they want instead of what is good.

[–] [email protected] 111 points 9 months ago (2 children)

Ah yes, "the" government.

That's probably it.

[–] [email protected] 4 points 9 months ago (1 children)

Using kde-connect for that, works really nicely cross platform.

Also inb4 "Discord community server - no thanks" :D

[–] [email protected] 8 points 9 months ago* (last edited 9 months ago) (1 children)

Maybe your server just has Gluetun intolerance...

[–] [email protected] 4 points 10 months ago* (last edited 10 months ago)

There's already plenty of tools that do this automatically, sadly they're very often proprietary and paid-for services. You just have to have a way to appeal false positives, because there will always be some, and, depending on how aggressive it is, sometimes a lot.

[–] [email protected] 15 points 10 months ago (3 children)

Really though? You can implement the same limits for federated posts, and just drop the ones exceeding the rate limit. Who knows, might be frustrating for normal users that genuinely exceed the rate limits, because their stuff won't be seen by everyone without any notice, but if they are sane it should be minimal.

The notice might still be able to be implemented though. idk how federation works exactly, but when a federated post is sent/retrieved, you can also exchange that it has been rejected. The local server of the user can then inform the user that their content has been rejected by other servers.

There are solutions for a lot of things, it just takes the time to think about & implement them, which is incredibly limited.

[–] [email protected] 2 points 10 months ago (1 children)

Yeah idk why you spread misinformation like that. File up/downloads are done via a p2p connection (see a reverse-engineered documentation of the p2p connection process) and thus the IP addresses are obviously known. Maybe not directly visible in the SoulseekQt client itself, but definitely through third party network connection monitors like Wireshark. It's pretty trivial for anyone using Soulseek to get IPs of the people they download from.

[–] [email protected] 2 points 10 months ago (6 children)

It's more about being visible to other users. If other users have your IP address, they can go to your ISP and complain about your IP address sharing copyrighted material. In certain jurisdictions they have to give out your info so that legal action can be taken against you.

If you use a VPN, they only know that somebody using this VPN is sharing copyrighted material. Since VPNs usually do not log who sends what, they can't be made to give out users data, so you're safe.

view more: ‹ prev next ›