I'm not a fan of fully socializing medicine, but having a non-profit with negotiating power in the mix could only help.
14,007 karma · joined August 16, 2012
My opinions are my own and do not necessarily reflect those of my employer.
* X: [@tracker1](https://x.com/tracker1) * Email: tracker1 at gmail * Website: [tracker1.dev](https://tracker1.dev/) * Keto Blog: [Keto Playhouse](https://medium.com/keto-playhouse)
-----
``` [ my public key: https://keybase.io/tracker1; my proof: https://keybase.io/tracker1/sigs/DAQeHW19H-HCUr1ZBXVK7v0QEKqyv4J40IU227AiCVg ] ```
I'm not a fan of fully socializing medicine, but having a non-profit with negotiating power in the mix could only help.
More than once I was on the hook for a $15k set of injections that I had to run on a credit card. At this point, I'm maxed out, paying out of pocket for what I can and it sucks... I'm hoping to convert to a City employee (temp) vs contractor which at least gets decent medical, but my own experience has me doubtful even then. I've worked my whole adult life, didn't even take vacation time through my 20's and 30's... and never planned to retire... I don't want to, but I'm facing a reality that may not give me a choice in the long run.
I don't think shifting to public healthcare is the answer in the US... but would like something similar to fiduciary safeguards around medicine and insurance.
Assembling a new model from scratch requires a ton of resources and knowledge bases... there's been a lot of sketchy activity just in training. You also have weighting, distillation and other approaches to create more portable options that can run on lesser hardware. But, K3 as an example takes massive compute resources to run.. and this isn't going to get to a portable device any time soon... as Moore's law is effectively dead, you may get newer/better tooling around the LLMs, or you may get an entirely new/unique approach to AI... but current trends aren't going to put a leading model on your own hardware anytime soon for most people.
I also think the restrictions on OpenAI and Anthropic are somewhat short sighted. In that the guardrails dramatically limit efforts towards securing your own software in many ways. Yes, it's also "dangerous" and maybe there should be a means of identifying "domestic" or otherwise "secure" accounts for those allowed to use the models without the same guardrails in place.
If your production system at most runs a backup to a drop site, then your backup facilities pull down versioned backups from there, you can better ensure older backup files are intact. More so by not allowing the two to see each other at all and not using backup accounts from a system that can access production resources.
That said, it's nice to use SQL from code directly in projects. Also, if you're on x86_64, you can always use SQL via Docker pretty easily if you aren't using the more advanced features. That said, I have a Windows Server VM expressly for testing MS-SQL.. I need to finish my ODBC based driver for Deno/Bun/Node (supporting FileStream).
For reference, part of where the thought exercises are for is in terms of replicating what might have been a traditional BBS message net, but a massive hub for such activity on Cloudflare hosting. Some pieces burrowed from FTN (Fidonet technology) but some rethinking in terms of more modern capabilities in practice.
Libertarians aren't generally in favor of limited liability. Read it again, slower.
Been using OpnSense for about 8 years now though... it's just been the best option for me, I use separate commercial AP.
Of course, it's not like you couldn't have done a google search yourself, if you really cared.
It's nice to see some old ideas like this come back... also hoping to see more self-hosted conversational sites around topics of interest (bulletin boards) over the giant social media sites we have today.
The continuous feed is nice though... I can see this used for banners like in the old sheet fed dot-matrix days... Print Shop Pro FTW!
For a persistent store.. sure... but that's true for PostgreSQL as well, which has some pretty painful major version migrations by comparison to other options.
That said, despite it being in a position where it would have normally disappeared, I don't think .io is going anywhere... there's way too much interest in keeping it around. I'd go so far as to suggest that maybe it should become "not" a "cc-tld" despite it being two characters and having it's origins in a national definition.