• 1 Post
  • 27 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle







  • Even in areas where they would fit it’s really annoying how some companies are trying to push it down our throats.

    It’s always some obnoxious UI element, screaming at me their 3 example questions, and I always sigh and think, “I have to assume you can only answer these 3 particular questions, and why would I ask those questions, and when I ask UI questions I expect precise answers so would I want to use AI for that.”

    I have no doubt that LLM’s have more uses than I can think of, but come on…

    I’m happy for studies like this. People who are trying to smear their AI all over our faces need to calm, the f…k, down.








  • Tip: find -type f | xargs head (but no it’s not comfy)

    but I don’t think going to “one giant metadatafile” argument helps; personally my attention starts splintering far sooner than that. Most of the time, if I’m looking at meta-data of an object, I’m not just looking at that single object, I’m reasoning about it in relation to other data points (maybe other objects in the same collection, maybe not). If at some point I want to shift my focus from created_at to updated_at or back, I need that transition to be as cheap as eye saccade. So by splitting the data to multiple files you are sort of setting “minimal tax” already pretty high.

    That said, for simple projects where you want to have as few dependencies as possible, I think it’s fine; it might or might not be better than raw-dogging your own format. I’ve actually implemented pretty much this format multiple times when I was coding predominantly in Bash. (Heck, eg. my JATS framework is pretty much using FAMF for test run state 😄 .) Just be careful: creating / removing files and directories can be a pretty risky operation – make a typo in (or fail refactoring) a shell variable and you might be just rm -rf’ing your own “$HOME”. It might be one of things you want to do less of, not more.

    BTW, I chuckled because you turn from created_at to cre_at for no apparent reason. (I mean, if you like obscure variable names, fine by me, but then why would you call it created_at in the first file?)

    BTWBTW, I love your site, I wish most of the web looked like that; the grey gives me sort of nostalgy :D Also you reminded me that I should give Kagi a try…




  • Just a follow-up with what I use now.

    As a replacement, I ended up setting up Nextcloud AIO container set and so far the experience has been pretty good. I do occasionally have to go and do the update manually but the AIO interface makes it pretty straightforward.

    The limitation is that I don’t have a very strong machine to host it. I have cheap VPS with only few gigs of RAM so I could give 2G to the nextcloud machine, which prevents me from enabling the more resource-hungry features, on the other hand the base NextCloud with caldav/carddav (which really is all I need) works fine.


  • Unfortunately later I learned that for some reason, somehow (surely my mistake), the only full copy of my dad’s contacts was at the nextcloud instance, so that collection was the “hostage”. Far more sadly, my dad deceased earlier this year, so in a weird irony when I received bill this time, the sad fact enabled me to put this all behind myself, so today I just canceled the service and goodbye.