> In some cases borders may overlap without making it an incorrect tagging. It may be result of agreement between countries to administer area together or to mark areas not controlled by any country, with both claiming it.
Fun fact: when you think of boundary disputes, two things tend to be assumed. One, this only happens in 'certain' countries. Two, this always means more than one country claims the same piece of land.
As for two: because of complex reasons to with their eventual bullshit bargaining position, there are several slivers of land wedged between the respectively claimed borders of Serbia and Croatia which belong to… nobody¹ (https://www.openstreetmap.org/relation/19478817). Although the local Serbian border patrols will gladly point their rifles in your general direction to point out that this does not, in fact, mean you get to be there as far as they're concerned.
1: Head-line grabbing claims by assorted dreamers notwithstanding; hence Verdis.
The basic sets are still there; look up the Lego Classic line. And for creativity at a good price the Creator 3in1 sets are gold.
Don't be misled by all the franchised stuff (Star Wars, etc.). That stuff sells well and has its fanbase, but Lego is much more than that. Lego currently has good sets (including the user submitted Ideas range).
LeoCAD is really nice and smooth to work with, and on Linux a much better experience than Lego's own Bricklink Studio. Unfortunately, for instructions you can't really get away from Studio, and while importing the model made in LeoCAD works for 99% of the bricks, you tend to end up with one or two types of brick misaligned, flipped, rotated, or missing.
It's a skill, but it's not too hard to get decently good at it. It's mostly a matter of actually building your model in the real world and iteratively improving your digital model and instructions from there, and changing the camera angle for steps that need it.
Most of the time is spent fighting with Stud.io (the software) and dealing with its bugs (it runs OK in Bottles (i.e., managed Wine environments), but stupid rendering bugs mean you may have to do the final export step on a device with a different GPU).
When you also want to print a booklet of instructions, getting the generated steps neatly out of Stud.io's instruction maker and into a sane pipeline for making the print-ready PDFs takes some work (as well as CMYK conversions), but that is mostly a matter of setting up some scripts to wire up pdftk and ImageMagick and friends.
They haven't published the full list of the 34 researchers accepted so far:
> Namen van de 34 bursalen maakt NWO niet bekend, aldus een woordvoerder, omdat de aanstellingsprocedures nog lopen en sommige onderzoekers geen publiciteit willen.
I don't really think it's primarily the CoMaps devs and contributors warning others about OrganicMaps. It's mostly OpenStreetMap contributors (e.g., mappers) like myself who followed the relevant discussions and events and decided that the community is better off routing around the problem.
OrganicMaps could be the best app there is in terms of functionality (it isn't), but if there are significant issues with their governance they are harmful to the broader OpenStreetMap community.
So we recommend CoMaps and OsmAnd, and carry on mapping.
Quite. At least Google delivers some value to society, despite being mostly evil. Klarna is exclusively parasitic, getting people needlessly into debt and pushing a buy now pay later mentality for luxury products.
> How did these people live through COVID and never encounter a QR code they had to scan with a phone?
Was that a requirement? I got through it without scanning a single QR code. I had my vaccination status available as a QR code (on paper when travelling in order not to depend on just a smartphone), but not the other way around.
We just ignored restaurants without paper menus, as we always do. It wasn't the time to eat out in any case.
Why refuse Adolf Hitler, but allow Vladimir Putin? I mean, it's not a race, but if you're going to draw a line in the sand (labelled 'no admittance to utter cockwombles' or something like that) I know where Putin would end up. Are those models refusing one and allowing the other? Why do they even refuse one?
> […] but then we'd have to make sure we get every single saved game for all the various games moved over […]
Every single game save? Why? I get it if you are deep into a month long Factorio game or have a huge Minecraft world, but on the whole games are ephemeral entertainment. If it's not worth backing up, it's usually fine to just start a new game.
Does it say 'don't bother with a regex beyond checking it contains an @ surrounded by arbitrary pieces of text?' This still sounds like it is leading developers to conclude that they should use a too complex regex and then send a confirmation email.
Claude Sonnet says:
> A practical email regex that covers the vast majority of real-world addresses:
>
> ^[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-zA-Z]{2,}$
Which is still way more complex than needed (and takes effort to read), and buggy according to years of blog posts written about this topic.
Of course the problem is the developer asking for a regex at all, but the must-regex-email instinct seems heavily engrained in our collective psyche.
This all old hat, unfortunately, and also a thing which will be gotten wrong by developers for years to come. Just shouting 'give me a regex for validating email addresses' will make an LLM like ChatGPT happily output bullshit suggesting some overlong regex which is flawed precisely as outlined by the linked article, even though no one is arguing for those long unmaintainable regexes once they've seen the light.
Ah well.
Where there is still room for improvement is in how email addresses are often made a little bit anonymous by a lot of websites. Did you ever see something like 'j*[email protected]'? Oh wow, that neatly leaves out John Smith's full name! Like showing only the last four numbers of an IBAN or credit card.
Except for us edge cases with a personal domain, where I then get 'm*[email protected]'. So stop that. Store it next to the bit of knowledge about validating email addresses — the bits of knowledge you use to correct junior developers and senior idiots.
The classic 'those guys did something bad, so I am going to go with the guys who are absolute assholes doing several orders of magnitude more bad things now instead' response.
That usually means that whoever utters it was just looking for a sycophantic excuse to go with the bigger threat because it is more convenient to them (for now).
Outsourced stuff is late and expensive too, just not directly the responsibility of the minister or secretary of state because of the magic piece of paper in between.
IT is hardly something we need to do occasionally, so build up a department that can do it (not just write up huge reports about what it should do and outsource, like Logius) and invest in the people that will work there (retaining them as much as possible). Give a big middle finger to consultants, and listen to the tech experts. Build boring stuff that works instead of a new app every month.
It's not impossible in theory, and cheaper in the long run. It's impossible because asshats who would actually benefit from left and centre politics keep voting right-wing parties in to power.
It's an unfortunate Dutch way of doing things. The firm believe that the market will solve it if you have a contract that says thing will be solved. Write a tender, pick the cheapest party, trust in contracts, hope it won't break before you (the external contractor pushing for it) move on in a few months time.
The people who pointed out that none of the moving parts of DigiD should have been outsourced were ignored until the tide shifted this year.
I'm honestly surprised the government decided to intervene. The usual method is to keep on believing in the signed piece of paper until the shit hits the fan (like with the Fyra high speed trains) — never mind that the US (where the buyer is from) is not likely to give a toss about those pieces of paper if they need something from our data.
Fun fact: when you think of boundary disputes, two things tend to be assumed. One, this only happens in 'certain' countries. Two, this always means more than one country claims the same piece of land.
As for one: even the Netherlands and Germany claim the same bit of sea. Boundary status: unresolved (https://www.openstreetmap.org/relation/19478817#map=12/53.56...), but don't worry, we're friends and allies these days.
As for two: because of complex reasons to with their eventual bullshit bargaining position, there are several slivers of land wedged between the respectively claimed borders of Serbia and Croatia which belong to… nobody¹ (https://www.openstreetmap.org/relation/19478817). Although the local Serbian border patrols will gladly point their rifles in your general direction to point out that this does not, in fact, mean you get to be there as far as they're concerned.
1: Head-line grabbing claims by assorted dreamers notwithstanding; hence Verdis.