I was in Rome with my wife for less than two days for other reasons, and we decided we'd pass by Trevi Fountain. Let me tell you, that place was packed.
Maybe 400-500 people packed just to say they were there, or maybe wait in hopes of getting a clear shot. All of this just to brag in social media.
I think the problem would be better if people didn't brag on social media about every single place they go to.
If only you'd put as much effort into reading as you put into your condescending tone, then, just maybe, you'd notice the part where I mentioned we wanted to "pass by", and not "sit for hours just to take a picture".
Those 400-500 people were just staying there, with many blocking the street – you know, the thing people walk on?
Well, I tend to see it like opioids, for example. Some people can just use their prescribed dosage and in the end they have no addiction whatsoever. Many more, even though they use their prescribed dosage, start an addiction which can lead to their lives getting ruined.
I think the same happens with social media. There are people who are more prone to addiction than others. People close to me have claimed to have felt much better after deleting/deactivating their social media accounts.
Personally it's been more than 10 years without Facebook, and I never had an Instagram, so there's not much I can say about the topic from my own experience.
> Many more, even though they use their prescribed dosage, start an addiction which can lead to their lives getting ruined.
I don't know if it's true that many more people prescribed opioids become addicted than not, and spreading such information harms people who do need them.
I'm guessing a single hash could be problematic for detections based on the domain for example. But this could be circumvented by sending hashed parts of the URL.
For example they could hash the domain, path and query separately.
Sending a hash of the URL or individual parts of the URL is problematic because the server can easily execute a dictionary attack to identify those parts in most cases.
The "Google Safe Browsing Update API" (used by Firefox, Chrome, Safari and others) solved this a long time ago. In that protocol, the browser hashes the URL, sends a short prefix of the hash to the server, and receives a list of hashes for the URLs that should be blocked. A huge number of valid URLs all hash to each prefix and the server does not know which one the user has visited. Also, the client caches the list of hash prefixes for which the block list is non-empty, to avoid unnecessary fetches of empty lists, which further improves privacy and reduces response time.
Also, the client doesn't send any kind of user ID token to the server.
Personally my best interview experience has been with Automattic. Having a text based interview on Slack where I could take the time to collect my thoughts, removed my anxiety almost completely.
Yes, I did. It's a bit lengthy but most definitely the best process I've been part of. You will find lots of posts from other people regarding their interview process. That helped me a lot during the process.
We used to have one a long time ago when we fronted with nginx and I could just throw a static file up there, but once we switched to everything being dynamic, it wasn't worth the effort to code up a route. :)
A few months ago, I contacted Microsoft support regarding an old Hotmail account of mine. I couldn't get access due to my own fault in the end, as I had set it up as a kid and 10 years later I could barely remember any details. However, the conversation with the support agent was by far the best. It felt natural, without the "copy/paste" ready-to-use responses they usually have.
So it seems V lang has finally been open sourced (not sure when exactly but it seems 4 days ago).
In any case great news. Looking forward to playing around with the language later this week.
