Nice. But unfortunately these addresses are hard to remember and "nobody" recognizes them when reading examples. One of those "standards" that have been a great idea, but lack practical relevance.
> But unfortunately these addresses are hard to remember and "nobody" recognizes them when reading examples.
How does that matter? The point isn't that the reader should know that "oh, this is a reserved address". The point is that there should be no room for the address that's actually being used by someone to end up being used incorrectly just because it showed up in some random documentation.
Much like how you probably wouldn't be thrilled if your phone number was used as an example in some random documentation somewhere.
> But unfortunately these addresses are hard to remember and "nobody" recognizes them when reading examples.
Mmm.
It's pretty easy to put three IPv4 /24s on a sticky note on your monitor. I think it's not unfair to say that if one can remember every fact related to one's job, then one has a job with a very, very small scope.
Also, this is another great reason to use IPv6. The v6 documentation prefix is '2001:db8::/32'... plenty of space for example subnets and easy to remember.
For me it's the opposite: I usually misremember 192.0.0.0/8 as being entirely private, so for 192.0.2.0/32, I usually assume that the example given is supposed to be a private v4 address/network.
Anyone who writes technical documentation about networking knows the key ranges, and at least TEST-NET-1 (192.0.2/24) is pretty easy to remember. You only gotta look it up a few times, instead of being sloppy and justifying so with “no one cares anyway”.
It partly because attitudes like that is why software is a mess. Too few people care about correct semantics, everyone is satisfied with whatever sticks. From lists for sets, to tag soup instead of markup, and so on - all the way to modern code slop.
We used Clearcase around year 2000 on HP-UX. I found it nice and powerful, but 90% of the developers did not understand it. Well, probably a similar statement holds for git.
I certainly didn’t understand it. We were using it up to 2019. A coworker set up a spec that would automatically mirror to the main codebase, unknown to me that was possible. I made a branch there, did some stuff, and then reverted. Little did I know I was essentially working on production. Broke a bunch of stuff and had to remember what I changed because there was no history. Point is it was too powerful for people that did and didn’t know how to use it.
Yes, Cloudflare. It says: Your browser is not supported. Use another browser or upgrade. I would upgrade if the vendor of this weaker embedded device provided something...
I know Cloudflare works fine on Firefox desktops and probably also on Android.
I am from Nordic country. I did not use any cash, had no wallet for several years. It's not needed. After the US government acting like it does I mostly stopped using cards. Like with phone OSes a US-controlled duopoly.
Cash does not to need to be used anywere, but cards can be avoided for weeks until I need to use it again. Most can be handled by cash or bank transfer without problems.
For phones I have not any Google Android or iOS until a year ago. Nowdays I have a Google work phone, but it's always in flight mode except when a pay my lunch subsidized by employer. I type this comment on my Sailfish device and I use a degoogled Android. Can cause minor inconvenienance occasionally, but rarely enough to turn on my work phone.
Sorry, I should proof-read my comments... Can't edit it anymore
It is not necessary to use cash anywhere because cards can be used really everywhere.
But if you don't want to use cards, it's still possible to avoid it for weeks in row. You can pay cash at most brick and mortar places and by bank transfer at most online sites.
We used zulip at work 7 years until I had to leave when the startup had to cut down development. We didn't pay a cent (which is not good for the project...) It was truly enjoyable software. Nowadays I am forced to use Microsoft Teams, which is largely non-functional bullshit. We pay real money to the disgusting company.
On delay-day you won't be travelling on the train you booked. So the reservation will only help if things go reasonably well. Which depending on your itenary might be less frequently than desired. Yes, a reservation helps if you happen to be on the correct train, but many others are not. It all remains a big gamble, you never know...
Not very familiar with Vercel. Discovered them only recently when a business my brother is a customer of fell victim of a phishing attack. The "Login to Microsoft" page hosted on Vercel was still online many days later when I heard of the case.
I often hear the argument of savings in printing and postage.
Having seen all the over budget, years delayed or completely failed IT projects in the public sector, I wonder whether there are any savings at all in the end.
(Perspective from a couple of EU countries at different degrees of digitalization)
While composing a reply to recipient B leaking some details that it "learned" when reading a mail from sender A, which you did not want to share with B. I have no idea how they organize sessions, indexes and whatever they use. But if no "side-channels" existed, I would be extremely surprised.
Of course reading generated text remains the sole responsibility of the user before clicking "Send". We all know that reading drafts can happen more or less carefully, especially when being in a hurry.
reply