@Nyfure
@kbin.socialI like the streaming approach, but i dislike that its linked to stremio.
I want to have the option to use my server (at least for syncing) with my own auth and transcode when needed on the server.
Basically jellyfin with streaming sources and search built-in.
And most debrid services dont seed (well) and have poor retention, so thats also not that great.
Seemy like you dont know how the cli actually works.
So if you ever have to touch the CLI (not sure when a normal user would need to), you complain you dont know the CLI instead of learning the tools you want to use?
Lots of stuff on Windows didnt work for me when i wanted advanced things.. very intuitive to fix that, if it was even possible.
Every system has its fair share, but if you are unwilling to learn and understand your tools before using them, you might drill yourself in the hand. Windows is just a bit over-protective before you can do so.
mhh.. you might be correct.
I havent considered how easy it actually is to search for a comment and find the exact post.
Question is if searching indexers like public search-engines is enough to call the data easily re-identifiable.
Or if this usage of personal data is covered somehow else e.g. legitimate interest, weighed against the freedoms of the data subjects, as you have listed above already.
Of course they are linked, but removing the username from the comments means they are mostly anonymized as far as GDPR is concerned.
It is perfectly fine to unlink data and keep processing it, as long as its considered anonymized under GDPR.
Your post content here is also not considered personal data, it shows up on a lookup request because its currently linked. If i crawl the page and dont save the username, the resulting data can most likely be considered anonymized under GDPR as far as the current interpretation is concerned.
It only becomes a problem as soon as i become aware the content indeed did contain personal data or probably also if i could have expected it to with high probability.
And i'd have to make sure to remove obvious ways to re-link the content to your user (e.g. mentions of your username in comments).
Anything else requires precedence about ways to re-identify someone based on posts on a platform weighed against the users freedom and the difficulty of doing such re-identification.
Recital 26 discusses when something could be considered anonymous. (or rather when gdpr would apply at all, and what it means to have anonymous data)
Now i dont want to defend reddit here, but afaik most comments are not subject to GDPR as long as you dont know they contain personal data and they have been detached from other personal data fields (like username).
So by removing personal data fields, they most likely become "anonymized".
Of course thats not the end of it, you have to consider the available technology to de-anonymize this data for it to be legally called anonymized.
But i dont think there has been any case where this was challenged before.. and i bet most supervisory authorities would discard such complaints as being "too hard to follow through". (i got that reply from the Netherlands authority for checking newsletter opt-in from a website)
And i certainly dont think reddit or any operator will be forced to delete comments because they could be deanonymized depending on the content the user wrote, when most comments probably cannot be deanonymized.
Having to check everything for potentially identifiable data in that regard would be ridiculous for website operators.
Maybe some light checks sure, but not as deep as it would be required to truly anonymize everything that a user could have written to identify them.
Alot of that information becomes fragments as soon as you unlink it from the user. e.g. 12 people in a post wrote "I am gay", great. But if you cant link that back to other comments of the same users somewhere else, its not identifiable, just text.
As far as i understood tailscale funnel its just a TCP-tunnel.
So you handle TLS on your own system, which makes sure tailscale cannot really interfere.
If you already trust them this far, might aswell do the same with a VPS and gain much more flexibility and independence (you can easily switch VPS provider, you cannot really switch tailscale funnel provider, you vendor-locked yourself in that regard)
I'd connect the VPS and your home system via VPN (you can probably also use tailscale for this) and then you can use a tcp-tunnel (e.g. haproxy), or straight up forward the whole traffic via firewall-rules (a bit more tricky, but more flexible.. though not that easy with tailscale.. probably best to use TCP-tunnel with PROXY-Protocol).
This way you can use all ports, all protocols, incoming and outgoing traffic with the IP-Address of the VPS.
Tailscale might even already have something that can configure this for you.. but i dont really know tailscale, so idk..
And as you terminate TLS on your home-system, traffic flowing through the VPS is always encrypted.
If you want to go overboard, you can block attackers on the server before it even hits your home-system (i think crowdsec can do it, the detector runs on your home-system and detects attacks and can issue bans which blocks the attacker on the VPS)
And yes, its a bit paranoid.. but its your choice.
My internet connection here isnt good enough to do major stuff like what i am doing (handling media, backups and other data) so i rent some dedicated machines (okay, i guess a bit more secure than a VPS, but in the end its not 100% in your control either)
Many systems dont support subpaths as it can cause some really weird problems.
As you use tailscale funnels, you really want incoming traffic from the internet. I am not sure thats a good idea for e.g. homeassistant that is limited in access anyways.
Might aswell use tailscale and access the system over VPN.
And for anything serious i wouldnt use something like funnel anyways. Rent a VPS and use that as your reverse-proxy, you can then also do some caching or host some services there. Much simpler to deal with and full support for such things as you then have an actual public IPv4/IPv6 address to use.
Heck, dont even have to pay for it with the Oracle Always-Free system.
In an more ideal world, getting less money because people tip less, would push you to reconsider the job choice and ultimately switch to something more lucrative.
With less workers, the company would be forced to pay more to even get employes.
Problem with this idealised scenario is, it doesnt work in the US, because workers are getting screwed so much and have so little choices at those low paying jobs, they'd be the ones loosing massively in the short-term.
And with little support structures my the states and federal government, they would fail.. and the 2 party system would fail them even harder, noone cares about them in the government.. too much invested in fighting imaginary culture wars.
But then again, using less services of the business leads to the same outcome in the end, so even that wouldnt work well.
The business will always win in the short-term.
So as it is ineviteable, maybe its better to think long term anyways.
And everyone wants tips these days, no longer just a gratitude or paying low wage workers, but now also a 'bid'.. (sure not every worker might like relying on tips, but specially well paid servers prefer it as they make bank)
I dont see you getting iut of tipping either way very well without government intervention.. which i dont see happening, but you have orher big issues too..
You can not only use that information for e.g. blackmail, but also to build material to manipulate you to do things without you knowing.
Information is a powerful tool.