had its own built in lock with a unique key
Is this a common thing? I’m Aussie so I have no idea about guns.
Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb
had its own built in lock with a unique key
Is this a common thing? I’m Aussie so I have no idea about guns.
User agents are essentially deprecated and are going to become less and less useful over time. The replacement is either client hints or feature detection, depending on what you’re using it for.
Most developers just write their own feature checks (a lot of detections are just a single line of code) or use a library that polyfills the feature if it’s missing.
The person you’re replying to is right, though. Modernizr popularized this approach. It predates npm, and npm still isn’t their main distribution method, so the npm download numbers don’t mean anything.
That’s exactly what you’re supposed to do with the modern web, via feature detection and client hints.
The user agent in Chrome (and I think Firefox too) is “frozen” now, meaning it no longer receives any major updates.
That really depends on the company. At big tech companies, it’s common for the levels and salary bands to be the same for both generalists (or full stack or whatever you want to call them) and specialists.
It also changes depending on market conditions. For example, frontend engineers used to be in higher demand than backend and full-stack.
Hot take: If you don’t like ads, then don’t use services/sites that are funded by ads?
I like using Sriracha, or peri-peri sauce from Nando’s or Trader Joe’s.
Very popular in the Netherlands.
the scroll wheel can tilt to scroll sideways
I use these for switching tabs in browsers/IDEs by remapping them to Ctrl+Tab and Ctrl+Shift+Tab using Input Remapper
I’m just glad that KDE now has an option to disable pasting using the middle mouse button (mousewheel click). Only available on Wayland though - AFAIK this behaviour is deeply rooted in X11 and it’s not easy to disable it.
Your data really isn’t worth that much.
Also, it’s a common misconception that large tech companies like Google and Meta sell your data. They don’t. The data is what makes the company valuable - they’re not going to give away their competitive advantage. Instead, advertisers can target people based on the data. The advertisers never actually see the data nor exactly who their ads are reaching (it’s just aggregate anonymized data).
On Google and Facebook, even individuals can use the same tools that large advertisers use to list their ads, and see exactly what they see.
deleted by creator
Not sure how that’s relevant, but some states do have an equivalent to GDPR. California has CCPA for example.
I took down the home page of one of the top 5 websites for around 5 minutes.
There were two existing functions that were written by a different team: An encode
method that took a name of something (only used internally, never shown to the user) and returned a numeric identifier for it, and a decode
method that did the opposite.
Some existing code already used encode
, but I had to use decode
in my new code. Added the code, rolled it out to 80% of employees, and it seemed to work fine. Next day, I rolled it out to 5% public and it still seemed okay.
Once I rolled it out to everyone, it all broke.
Turns out that while the encode
function used a static map built at build-time (and was thus just an O(1) lookup at runtime), decode
connected to a database that was only ever designed for internal use. The DB only had ten replicas, which was nowhere near enough to handle hundreds of thousands of concurrent users.
Luckily, it’s commonplace to use feature flags changes, which is how I could roll it out just to employees initially. The devops team were able to find stack traces of the error from the prod logs, find my code, find the commit that added it, find the name of the killswitch, and disable my code, before I even noticed that there was a problem. No code rollback needed.
That was probably 7 years ago now. Thankfully I haven’t made any mistakes as large as that one again!
Always use feature flags for major changes, especially if they’re risky!
e.g. outlook replaces links in mails so they can scan the site first. Also some virusscanners offer nail protection, checking the site that’s linked to first, before allowing the mail to end up in the user’s mail client.
Proofpoint does this too, but AFAIK they all just change the link rather than go to it. The link is checked when the user actually clicks on it. Makes sense to do it on-demand because the contents of the link can change between when the email is received and when the user actually clicks it.
(DSGVO is the German version of GDPR)
This field needs to be checked everywhere the account is used.
Usually something like this would be enforced once in a centralized location (in the data layer / domain model), rather than at every call site.
for the automatic removal after x amount of days
This gets tricky because in many jurisdictions, you need to ensure that you don’t just delete the user, but also any data associated with the user (data they created, data collected about them, data provided by third-parties, etc). The fan-out logic can get pretty complex :)
I wasn’t disagreeing with you :) or at least I think I wasn’t. I was just quoting the RFC you linked to.
it makes connecting to localhost as easy as
http://0:8080/
(for port 8080, but omit for port 80).
The thing is that it’s not supposed to work, so it’s essentially relying on undefined behaviour. Typing [::1]:8080
is nearly as easy.
skimming through these PRs, at least for WebKit, I don’t see tests for shorthand IPs like
0
(and no Apple device to test with). What are the chances they missed those…?
I haven’t seen the PRs, but IP comparison should really be using the binary form of the IPv4 address (a 32-bit number), not the human-friendly form.
Waze is owned by Google, and they’re slowly converging over time.