Honestly EU doesn't have to change a single thing. All compliance exists already.
The trick is to not track good children at all, only those bad ones. I'd you leverage sanction lists (that exist already) to track the bad children, you have all cases covered.
Any Santa related contractor (Santa helpers, elves, etc) have to check a sanction list to see if they can finalize a transaction with said child.
As for lists: when a child sends a request for particular gift, it starts a formal transaction. The other entity is legally allowed to process said child's data to provide the service they agreed upon.
Kids that have not sent a letter to Santa and are not mentioned in sanction lists, can still get gifts but Santa lacks profiling metadata and can only provide generic, unprofiled gifts. Which is good as already have sufficient amount of Bluetooth speakers and Paw Patrol toys.
Wait, how would tracking bad kids be less illegal? I think putting bad children on state sanctions list might very well be deserved for some of them, but a bit overkill... Imagine not doing your homework leading to being officially sanctioned by EU governments or the UN... though I'm sure that's a pretty convincing way to make someone do their homework.
I would not optimise for performance yo early. All the building blocks are here. Let's leave "scaling issues" to the Christmas OPS team! Some cloud provider must have a North Pole region, right?
I have worked with a few CEOs like this; the last was an old company (25 years) in dire need of a digital transformation to survive. The company had more than 300 employees and was still using Excel and Lotus Notes on-prem server room. I started a move to Office365 and Azure Cloud .NET, but the CEO showed no interest in the technology and gave me a few months to complete the transition. He came up with some unrealistic ideas for accomplishing the move when timescales were not met.
After a year, I left the company after delivering a few things. Recently, I visited their website and found only a single home page with several PDF documents embedded within it and no sign of any client-facing solution. Assume they are back in Excel again.
There are plenty of CEOs / Founders out there that would love to find a great CTO / CIO so don't give up looking :)
My advice is to start looking for a new job or go freelance. I started doing fractional CTO work - which is interesting but challenging to find new clients.
The old age problem of having an open project where people don't understand what an alpha is.
You give this out to the world for feedback and people moan its not working.
I am old geek and back in the day you knew an Alpha was just for the playground to kick around - most likely will crash, worse case will destroy you PC but you have a play / provide some feedback and wait for the next release.
A lot of other projects do everything in the dark and do a big ta da at the end - and missed the opportunity for the community of "alpha" or "beta" testers to provide some feedback along the way.
Keep going - its added to my list to take look once in beta as I prefer to play in that playground rather than the alpha one these days.
It's the old-age disconnect between the marketing, the claims and the actual functionality.
For example, the title claims that it's a file explorer. However, someone in the comments shows that it fails at actually exploring files. Something which even an alpha project would not fail to do considering the claim.
Only when you read through the marketing copy and the comments, you realise that it's a hybrid cloud/local/cross-device Dropbox that creates a view of your files across systems/locations, and only once it's done that, only then can it do the actual file exploring. At least for now.
The title doesn't claim it IS a file explorer, it is an alpha version of something that aims to become a file explorer (for some definition of "explorer"). That's exactly the point of the OP?
> UPDATE: Spacedrive is under active development, we are in the pre-alpha stage, with builds occasionally released via GitHub actions, official alpha coming soon.
I think expectations broke as companies shifted from a focus on polished shrinkwrap to a ubiquitous race to market with continuous deployment.
For them, “alpha” and “beta” became ways to say “fresh out of the oven” and high profile revenue-generating products were proudly emblazoned with those words for years.
At this point, it doesn’t even mean anything. Half the internet is running on some 0.11.45-alpha of something or other, maintained by corporate engineering teams whose total compensation is in the millions.
It makes it legitimately hard for people to know what to expect and what standard to hold things to.
Time to wrap around and have -omegas. When that standard becomes the norm we can keep going backwards until -alpha, at which point we can use --omega and so on.
NATs has reported that the system is now back up and running. It is possible that the secondary system took over with data syncing having to take place before the switchover?
My original post was about my interest in the technical aspects of redundancy and failover mechanisms in something as mission-critical as air traffic control.
I come from a background in broadcasting, where failover is critical, and redundancy is built into any broadcast chain. e have multiple backups and jumping-off points to deal with any issues that arise. It's pretty rare we could ever go to “black”.
Because large systems are complex and have very complex and hard to detect failure modes.
What is more impressive is how rare these events are, given the complexity of the underlying systems. Redundancy is not without its own problems (source of truth, for instance).
The IT is just poor. Tech firms routinely change much more massive and complex systems at a far faster pace compared to the stagnation found in airline IT, and yet total failures are not more frequent.
Im not sure that's true. If something makes the news it's likely to be of interest to a large amount of people, that doesn't immediately qualify it as something rare.
A lot of times large scale outages like this are because of the redundancy. The whole system is interlinked with automatic failover. then it hits a corner case that was not engineered into the fail model and you get cascading system failure where each node starts bringing down other nodes automatically. basically the lesson is: In highly interlinked systems you get highly interlinked failures.
And then after a lot of angry words and finger pointing this new failure gets added to the failure model.
My personal takeaway after chasing the long tail of automatic failover on a few projects, is quite often it is better to drop a few 9's from your service goal, decouple some of the systems, and accept that while some parts of the system may go down, it should not bring everything down with it.
The US air traffic control crash at the start of the year turned out to be a decades old system which had not been upgraded, I think the UK one is a little bit more recent, but like alot of software, people dont want to pay for the real costs of software developments.
Complexity tends to hide problems. An over-engineered system is going to be less stable than a simple one where you know how things can break and how to bring them online pretty quickly.
They agiled software to the point where it’s written by product managers and wanna be engineers that cargo cult “good practice” without understanding what it’s meant to do. This types of issues are common in british made software.
You'd hope an air traffic control centre would have a big box of popsicle sticks and black pen markers to cover the fallover of power | backup power | digital systems.
It's based on the handshake blockchain https://handshake.org/ and yes, it's outside of DNS from what I have read. I originally assumed that had bought 1,000,000 TLD at $240k each :) which is crazy as its sounds.
As i understood it the difference was esignature (was what this was providing) and esign was to sign with a digital certificate. esignature is plenty for most things.
Docudeal looks really cool and simple! and compared to the crazy costs of HelloSign, Docusign etc.
One thing I would say is provide a RestAPI so easy to integrate into our own applications so we can have the GUI on our side.
