ndguardian

I tend to go back and forth between Go and Python. Typically for work stuff I am writing AWS automation utilities though so I’ll opt for Python because Boto3 is lovely. Go is typically for my personal projects.

I’ve also been itching to try my hand at Rust, but haven’t brought myself to start yet.

My SO just had something similar pop up yesterday. She was running into weird errors on her Chromebook, so I had her change her user agent to Chrome on Windows. Everything magically worked. Hmm…

I’m lucky in that my employer went the opposite direction. Downsizing our local office and just letting us all be 100% remote. We’re a geographically distributed group so it doesn’t make sense to enforce office requirements.

Wait. I can automate my meetings too? I dig it.

Your partner has an impressive bank account.

As much as a lot of that hate it warranted, I’d say the install location isn’t so much a Teams issue as it is a Windows issue and how it handles user-level vs system-level installs. Obviously still a Microsoft problem, but important to note.

Is it just me or do crabs always look so dainty when they eat?

Ah, neat! Yeah that would work then. I’d hope that your usernames are unique in your self-hosted setup, so that should work just fine. Very nice!

Hmm…this should work but I do have a concern on it based on my experience with AWS. Maybe this is different with minio though.

In AWS, S3 bucket names are globally unique. Not just to your AWS account, but across ALL S3 buckets period. So let’s say you have a username of “test” and use that policy. If that user attempts to create a bucket and that bucket name is taken, well that user is out of luck.

Obviously if minio doesn’t require globally unique bucket names you’re probably fine, but otherwise this could realistically become a problem.

What makes that better is that VS Code is running on Electron, meaning it is running Chromium under the hood. Or at least part of it. Been a while since I read up on it so I can’t remember for certain.

I think the biggest place it has genuine benefit would be for something like deeds to homes, titles for cars and stuff like that. A permanent, auditable and public system for tracking the transfer and ownership of things.

Unfortunately it comes with its own caveats, such as “what if I lose the wallet containing the deed to my home, and I want to sell it?”

I never really understood the whole thing about picture based NFTs though.

Yeah, I’ll remain skeptical here. I’ve used HP laptops before and they always seem to fail immediately after the warranty expires in my experience.

Yep, this is key. If you’re getting a bunch of malicious traffic from one source, that’s easily fixed. Just drop the traffic.

But when that traffic is coming from hundreds or thousands of sources, that becomes much harder to address. Can you just drop traffic from those sources? Sure! But then you also risk dropping legitimate traffic.

There are also services that can automate the detection and prevention of DDOS attacks such as CloudFlare and Akamai, but these can get expensive very quickly, so it can significantly increase the cost to running the instance in question.

Obviously this isn’t digital piracy, it’s identity theft. Hence the reason Hollywood is perfectly fine with it. 😛

I don’t think the post has a ton of merits for reasons that have already been described. That being said, there is one potential issue that I’m surprised that hasn’t been mentioned, which is impersonation.

Say someone takes the username jimbo on an instance somewhere and becomes super popular. Then someone else decides to create the same username jimbo on a similarly named instance and tries impersonating the other user. Sure, people can look and see “oh this isn’t that other jimbo” but you would have to look and see.

Probably not a major issue, but could theoretically become one.