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.
Overall, I think the project looks great, and the fact that it's open-source is a big plus. However, there are a few issues that I noticed:
- The web editor doesn't seem to display pages 2, 3, etc.
- The biggest concern I have is how the platform handles the end of a page and page breaks. Specifically, the text seems to be too close to the bottom of the page, with no footer padding. If I were to add a new role to the CV and include the company name, I'd expect the platform to be smart enough to recognise that there isn't enough room for the entire entry and to move the name and the first couple of associated bullets to the next page instead of awkwardly splitting them across two pages.
- I also noticed that my Word CV fits on 2.7 pages, while the document on your editor spans 3.5 pages, with identical font sizes and types. Is there any way to adjust the text width which is what i think the issue is.
Re-posting my comment from the github issue: Agree that the app is currently buggy for multi page layouts. Its initial target audience is for students and early-career professionals who can fit their experiences in one page, and multi page layouts haven't been well thought and implemented.
There are hundreds of phones stolen by the youth with hoods and stolen e-bikes in London each day. If they grab your phone in the seconds before it locks your screwed. That’s my biggest concern!
The passkey provider should require either a PIN or biometrics each time it is authenticating you against a service. So it won’t matter if your device was unlocked when it was stolen
I maybe being dumb here - but why can you not plugin a USB-C dock that has dual HDMI output ? I get you cannot dual monitor direct from laptop > screens. I would always use a dock with single cable. e.g https://www.belkin.com/uk/docks-hubs/connect-pro-thunderbolt...
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.
I like the idea!