They’re not. Some buy a Verified Mark Certificate (e.g. ikea.{com, ca, fr, maybe others} do), but most won’t ever (e.g. the first one on https://bimi-explorer.svg.zone/bimi/list.html 026430010.co.il, and a slightly random other dailydot.com). Also the two Mark Verifying Authorities listed at https://bimigroup.org/implementation-guide/ currently talk about approximately $1,300 and $1,600 per year, less than the $2,000 you say though recurring.
Feature suggestion: a "my location" button on the map, so you can zoom in to your current location. There is a browser API [1] for this (which asks permission, or you can do it based on the IP address [2]
The root cause for the PHP vulnerability is trying to parse unstructured text. The actual information in WHOIS has structure: emails, addresses, dates, etc. This info should be provided in a structured format, which is what RDAP defines.
IMHO, there is no reason for a registrar to not support RDAP, and to have the RDAP server's address registered with ICANN.
I think this points to the real problem: it is hard to evaluate how "good" someone is during the hiring process
Lots of great coders don't have a big open presence. Years of experience isn't a good sign with the churn in tech, plus you don't know if they wrote code or just watched. Is being able to do a l33t coding exercise in a fixed time a sign? IMHO I'm decent programmer and I've failed them. Can you come up with an exercise that matches the work that will be done and can be completed in a reasonable amount of time?
And the phrase "matches the work that will be done" is doing some heavy lifting: many companies don't really know what they need. I've seen companies that need 99% soft skills that want a ton of niche tech experience. Or advertise for something other than the real dumpster-fire that you'll have to work on.
This is the fundamental reason that knowing someone works: they know your coding skills and they can give you the inside scoop on the position.
I made feed.style[1] to help people add a decent XSLT stylesheet to their feed.
I'm using it myself[2] and really like the effect.
I think it always makes sense to have a stylesheet (and use text/xml content type): otherwise people clicking a rss/atom link are greeted with a wall of xml (or a download prompt). Hard to think of a worse UI for people who aren't familiar with feeds & feed readers.
Everyone's memory is better than mine: I can't even remember the command I typed, so I need to hunt it down from the context: current directory, date or previous commands.
Lines 11-21 can be ignored, they detect if the folder you were in got moved/deleted from another shell, to avoid the confusing behavior you get in that case.
zsh has a comprehensive hook system available for these types of tasks¹(zshaddhistory in this case). It gives you more options to control how/when the history is preserved, and allows you to be more selective in when it should be written.
Possibly worth noting for others that you'd want to think this through if you're using any of the history eliding options(hist_ignore_space² for example), as one history file may contain secrets when you're really expecting that it wouldn't.
There is also a better interface to work with hook functions through the add-zsh-hook mechanism³, which allows stacking multiple hook functions together.
https://bimi-explorer.svg.zone/bimi/
reply