chrash0

heck yeah this is the review i was looking for 💯

you’re right. i just expected it to be an increase 😅

i honestly didn’t look that close, obviously haha

but yeah, i’ve been kinda looking for a reason to de-Microsoft my stuff

good lead. it’s just the one project for now, and to my surprise it’s actually a dependency for the ollama-rs project, so i feel somewhat obligated to keep it stable.

yes, according to this morning’s email

sure, there’s reason to be cynical, but i don’t think handing society to fascists out of bleak pessimism is the way i want to live my life.

i guess in these situations i think of my aunt, who is in her 80s. she has an iPhone. should she buy a NAS and host Immich? i don’t think “make backups” is the simple advice it appears to be for the vast majority of people

i think it’s easy to make comments like this from the peanut gallery, with the benefit of hindsight and a self-selected group of users who will agree. but Apple should be legally obligated to address this. the solution can’t be “this idiot didn’t spend his nights and weekends doing 3-tier backups and high availability infrastructure diversity!”; that’s not scalable. if we just accept that companies can do this, they will continue to. but this has been on the front page of HackerNews. it’ll probably make it to Tim Apple’s desk eventually, so we’ll see what shakes out.

as someone who used to work on “expert models” i’m excited that not everyone has abandoned them for “what if we just had a model that knows everything (that doesn’t exist) and costs a billion dollars to run”

three, maybe four things:

1. as mentioned: Obsidian. i pay for Sync cuz i like the product and want them to succeed and want reliable offsite backups and conflict resolution. use a ton of links and tags. i’ve been into using DataView to make tables of IoT devices, services, todo items, etc based on tags and other YAML frontmatter.
2. chezmoi. manages my dotfiles so my machines are consistent. i have scripts that are heavily commented that show how to access MQTT, how to read and parse logs from journald, how to inspect my network, etc. i do think of them as code as documentation, even if they’re also just convenient.
3. NixOS. this has been my code as config as documentation silver bullet. i use it as a replacement for Docker, k8s, Ansible, etc as it contains definitions for my machines and all the services and configuration they run, including any package dependencies and user configurations. no more statting an assortment of files to figure out the state of the system. it’s in flake.nix
4. honorable mention to git and whatever git hosting provider is not on your network. track your work over time, and you’ll thank yourself when things go wrong.

some things are resistant to documentation and have a lot of stateful components (HomeAssitant is my biggest problem child from an infra perspective), but mainly being in that graph mindset of “how would i find a path here if i forgot where this was” helps a lot

he’s been salty about this for years now and frustrated at companies throwing training and compute scaling at LLMs hoping for another emergent breakthrough like GPT-3. i believe he’s the one that really tried to push the Llama models toward multimodality

i guess the point that’s being missed is that when i say “hard” i mean practically impossible