The sound that a frog makes is 'kwak' in Dutch. And that is also the name of this bird which makes a similar sound. Onomatopoeia for the frog predator.
I didn't know this was a thing until you mentioned it. I'm glad there are more options today. I have since left the company and haven't gotten to work in address-related problems since.
We were pretty invested in using Google at the time for their Geocoding API. The questions that needed answering for our use-case were:
- Does this place actually exist?
- Can it be found on Google Maps?
- Do we (the company/researchers) have an entry for this place already?
Some barbarian without a grasp of the Dutch language knee-jerked the down-vote button so I'll add a Swedish version which adds an important attribute.
Imse vimse spindel klättra upp för trå'n.
Ner faller regnet, spolar spindeln bort.
Upp stiger solen, torkar bort allt regn.
Imse vimse spindel klättrar upp igen.
Here's how to interpret this saga of the ever-climbing little spider in the context of web development. It climbs up its tread (klättra upp för trå'n) 'cause that new framework will sure make catching those flies (clicks/jobs/likes/whatevers) easier. And then the rain starts (the CVEs start piling up, the corrupted packages come flooding in) and the hapless spider gets thrown off its web (Pwned!) until the sun comes back and dries away the rain (a new framework, yay, this will solve all problems) upon which the spider climbs up its thread again.
They stole the axios's npm keys and they uploaded malicious artifacts. They did not takeover the axios's repo. The issue is with packaging and distribution, not with code.
Because the way npm works means that as soon as a developer key got stolen, a lot of people got pwned. The key is the only barrier.
Compare that with the average distro. You would have to compromise the developer infrastructure (repo or website) and publish a new version without them being aware while notifying the maintainer that’s its ok to merge the new package script in the distro repo. Hard to pull off in high profile projects.
Funding for NLnet Labs is largely from paying customers for development of DNS software.
NLnet funds development of the full stack of communication technologies from chip design to office suites. Funding for NLnet comes from public institutions, private companies and citizens.
Another data point: I've visited public libraries around Friesland province. They all use catalog + internet facilities which look & feel the same across libraries: a browser (Mozilla) + office suite, PDF reader, files can be saved locally put don't persist between user sessions.
This would lend itself perfect for a Linux-based setup: netboot (from per-building local file server or NL-based cloud), read-only filesystem, LibreOffice etc.
But alas: the setup is Windows-based (running on Intel NUC or similar), office suite is Microsoft Excel/Word/PP. Completed by Acrobat PDF reader. No doubt it's at least able to leak telemetry and/or user data if Microsoft were to feel like it (or asked/forced to do by US gov).
Disclaimer: I made mxmap.be after seeing Swiss ant Dutch counterparts. I did not look at MX records only but also at EHLO replies, SPF and DMARC records and at fronting services.
Any recommendations / lessons learned when building this? I would love to give it a go for Brazil if one doesn't already exist around the time of my holidays in June/July.
"Purely based on the MX-records, we learn that 72% of Belgian municipalities run Microsoft mail servers and 60% of the Dutch municipalities. For Scandinavia, it’s 64% in Norway and 57% in Sweden. In Finland, it’s a whopping 77% if the cities that are being served by Microsoft."
reply