←back to thread

622 points ColinWright | 1 comments | | HN request time: 0s | source
Show context
kstrauser ◴[] No.30079330[source]
I sure hope that's right. It was the best feeling in the world to stand up an Apache server on my Amiga, and later my little FreeBSD server, and see my friends viewing the website I was hosting on my dialup connection. It wasn't pretty, it wasn't elegant, and it certainly wasn't fast, but it was mine. I made that. From installing the server to writing the HTML, I owned that service from end to end and had completely freedom to do whatever I wanted with it.

That's what I want the Internet to look like for my younger family and friends. It'll probably never happen exactly this way, but I can picture someone running an IPv6-only service on their phone to impress their friends. I know what their smile would look like because that was once my smile, too.

replies(14): >>30079383 #>>30079412 #>>30079441 #>>30079505 #>>30079550 #>>30079551 #>>30079596 #>>30079689 #>>30079823 #>>30080525 #>>30080756 #>>30080986 #>>30082530 #>>30085966 #
throwhauser ◴[] No.30079550[source]
How can a small website cope with GDPR compliance though? The rules that sprang up to constrain the social-media behemoths seem onerous for anyone but them to comply with.
replies(3): >>30079576 #>>30079601 #>>30080059 #
WesolyKubeczek ◴[] No.30079601[source]
By not collecting data it has no need for, and not passing that data on to third parties? By providing an ability to delete any user account, and for editing any personal information? By not using EBCDIC to store said information?

Are you making this more complicated than it needs to be?

replies(3): >>30079666 #>>30079754 #>>30138554 #
throwhauser ◴[] No.30079666[source]
> Are you making this more complicated than it needs to be?

I'm not sure. I guess if one trusts the default logging settings on the server software to be compliant, and only uses static HTML, maybe that's adequate? But as soon as any third-party code or data provided by some other server gets involved, it's hard to know what might be logged elsewhere as a result of visiting your site.

I mean, would an old-fashioned web visitor counter be compliant? It's tracking something in order to provide that number.

replies(2): >>30079839 #>>30080264 #
corobo ◴[] No.30080264[source]
You can +1 a database `views` column without storing anything at all about the user. If you’re just doing that you’re good to go
replies(1): >>30080403 #
erulabs ◴[] No.30080403[source]
I mean, most "unique view counters" store the users IP address, so that would be right out. I'm fairly sure even being aware of what complying with a complex legal documents implies constitutes enough of a complication that it's worth mentioning.

It is a complication, but I believe it's worded so that small companies and individuals are immune from its consequences.

replies(3): >>30080494 #>>30083502 #>>30086229 #
martin_a ◴[] No.30083502[source]
You could always hash the IP on the client side before sending it to your counter. That way you have no information which you can backtrack to a specific IP and therefore a person.
replies(1): >>30089780 #
BenjiWiebe ◴[] No.30089780[source]
Except there's so few IPs (v4) you could just bruteforce it in not too much time.
replies(1): >>30092395 #
1. WesolyKubeczek ◴[] No.30092395[source]
There are different kinds of hashes. You can, for example, assign numbers to your incoming IPs. The first one to come in gets 1, the second gets 2, and so on. Numbers zero out at midnight, correlation between them and real IPs are at the load balancer. Good luck bruteforcing these.