• 0 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • It’s important here to think about a few large issues with this data.

    First Data Storage. Other people in here are talking about decentralizing and creating fully redundant arrays so multiple copies are always online and can be easily migrated from one storage tech to the next. There’s a lot of work here not just in getting all the data, but making sure it continues to move forward as we develop new technologies and new storage techniques. This won’t be a cheap endeavor, but it’s one we should try to keep up with. Hard drives die, bit rot happens. Even off, a spinning drive will fail, as will an SSD with time. CD’s I’ve written 15+ years ago aren’t 100% readable.

    Second, there’s data organization. How can you find what you want later when all you have are images of systems, backups of databases, static flat files of websites? A lot of sites now require JavaScript and other browser operations to be able to view/use the site. You’ll just have a flat file with a bunch of rendered HTML, can you really still find the one you want? Search boxes wont work, API calls will fail without the real site up and running. Databases have to be restored to be queried and if they’re relational, who will know how to connect those dots?

    Third, formats. Sort of like the previous, but what happens when JPG is deprecated in favor of something better? Can you currently open up that file you wrote in 1985? Will there still be a program available to decode it? We’ll have to back those up as well… along with the OSes that they run on. And if there’s no processors left that can run on, we’ll need emulators. Obviously standards are great here, we may not forget how to read a PCX or GIF or JPG file for a while, but more niche things will definitely fall by the wayside.

    Fourth, Timescale. Can we keep this stuff for 50 yrs? 100 yrs? 1000 yrs? What happens when our great*30-grand-children want to find this info. We regularly find things from a few thousand years ago here on earth with archeological digsites and such. There’s a difference between backing something up for use in a few months, and for use in a few years, what about a few hundred or thousand? Data storage will be vastly different, as will processors and displays and such. … Or what happens in a Horizon Zero Dawn scenario where all the secrets are locked up in a vault of technology left to rot that no one knows how to use because we’ve nuked ourselves into regression.





  • I’m a DevOps Engineer and thus, I spend 8+ hours at a keyboard a day… I finally decided that I should spend some money on a device i was going to use that much of my life and I now have two Iris’s I built. I’m using one to write this that I made last year so i could leave the one I built back in 2019 at the office. Both were v2’s. I can’t recommend them enough. Takes a little getting used to as you’ll want to figure out your layers and play with QMK for things like adding a numpad under a layer and adding in special keys and macro’s and such, but It’s been well worth it. My wrist pain completely went away. Between that and either logitech trackball, It’s been a great setup for 4yrs now and I can’t go back to normal keyboards for any decent amount of time before starting to feel sore. FWIW, the new Iris Rev 7’s make it so there’s almost no soldering or anything.

    My setup is Tented as well, and I made matching wrist wrests to match the contour and tenting angles.

    Technical Details:

    I used my original Iris for 3 yrs before deciding I should use what I had laying around to make this one. I bought two sets of PCB’s when I originally got the v2’s as it was my first mechanical keyboard build and I didn’t want to worry about screwing it up. But I didn’t have any issues, so I had another set of PCBs laying around that whole time. I decided for this one I’d go all out and make a custom bottom of walnut and I had laser cut brass top plates. I also used Millmax sockets for the keyswitches so they’re hot-swappable. Then, since the v2’s still require your to solder your own Arduino Pro Micro’s, I swapped those out for nice!nano’s so it’s fully BlueTooth wireless both between the halves and to the PC. I’ve filled it with Hako Trues and MT3 White-on-Black doubleshot keycaps. So far, I’ll say the True’s are a bit stiff sometimes, but I still quite enjoy typing on this thing.