I forgot such messages directly. Then when It realize I saw an important message tens seconds ago I have no way of going back. I can not press undo and get that message again.
Error messages are a bad design. Error logs are ok. Global undo would be king like the undo close tab feature in browsers.
Windows has always baffled me with the system tray icons it is too cluttered. I grew up with a tricked out Linux desktop so I understand the need to customize. But most of the time you do not need that.
I believe a VPN should stay hidden if it works, no need to have it visible.
> I believe a VPN should stay hidden if it works, no need to have it visible.
Which is fine if you only have one VPN client or one VPN network and you don't need to turn it on/off or change it regularly.
My current day job has one VPN client but five different networks.
At a previous job I had two different clients I would need to switch on and off.
It is very on-brand with Apple though that there is one right way to do things, and everyone else either needs to change the way they do things or go elsewhere.
LLMs are great at the roll you own crypto foot gun. They will tell you to remember all these things that are important, and then ignore their own tips.
A 100G file was ok in those editors even with syntax highlighting. That is an extreme because saving did take some time but there are ways to optimize for that would it ever become popular. IMHO 640K per file is enough for everybody.
The problems was mainly that even "apt-get build-dep" is not enough to handle all the problems that arise from that. Even if configure was standardized, there was always problems with diversity in systems.
The NIH syndrome is still big in software build tools, everything is complicated unless you have written it yourself in your environment. Admitted I seldom run those commands manually anymore, but things have gotten way worse when I do try. Specific versions of tools, libraries and kernels, or just kernels. Nix build scripts are actually one of the worst offenders here often ignoring every other standard available. Not saying it is bad, just an example of why what you write above is more complicated than it sounds.
My point with was actually that fairly well is too relative, same as learned a language. Languages are hard communication is easy, it takes way more than 100 weeks to learn Japanese, but I base it of my self.
I agree, there are two things I miss with markdown: import/export of text + media, multi user editing. This is always an extra step when you do not have and editing builtin in the Wiki that handles that. The "paste" image into document feature is one of the most useful features of a wiki if you want to write a fast bare bones tutorial.
Do you have examples of nature reserves where this is not allowed. Here there are always rules and they vary alot between the reserves, but mostly you are allowed to pick fruits. Digging, breaking sticks and collecting rocks is forbidden almost everywhere.
I ask because this would be an interesting data to have in Openstreetmap or Wikidata, so you can easily know what rules govern what nature reserve.
Do you renew the certificates used to distribute the public keys in SAML metadata, and if so why do you do it? I have had a hard time convincing people it is useless to renew those certs and have yet to find an implementation that care about those certificates.
Renewing the certificates seems technically pointless, but some organizations/federations require it.
Rotating the keys would make some sense, but just swapping the cert for a new one issued against the same keys doesn't. It's the easiest way to fulfill those requirements, because you don't need to synchronize the metadata updates, the signatures are always valid with both the old and new cert.
Make senses, most bigger federations do not bother with this luckily for us it is just specific idps.
> synchronize the metadata updates
Sadly I know many implementations that do not handle key changes in the metadata in a smooth way. The two SPs I have from Adobe both require manual updating of one key per idp, making a switch pain to synchronize.
All my x509s for SAML signing are self-signed, and all my self-signed certs live for 9999 days and I plan to let someone else figure out the fallout from that as I'm going to be /retired/. No one has ever really complained. Some IdPs I've integrated with use certificates that are signed by public CAs and it's always a hassle because the ergonomics around it are terrible.
IMO, I think rotation is wildly useless too. It might make sense in a world where my signing certificate was decoupled from the metadata someone else has to very likely load by hand.
If you need to know 100% that the bird is in the park at that precise moment it can be tricky. If you need to identify a Bird-of-prey in the Alpha quadrant you can understand the Klingon proverb a sharp knife is nothing without a sharp eye.
Error messages are a bad design. Error logs are ok. Global undo would be king like the undo close tab feature in browsers.
reply