a beautiful robot, dancing alone · showgirls über alles: kylie, angèle · masto · last.fm · listenbrainz · lovekylie
so per wikipedia and confirmed at MDN, firefox is the only major browser line not to consider certificate transparency at all. and yet it’s the only one that has given me occasional maddening SSL errors that have blocked site access (not always little sites, it’s happened with amazon).
i don’t understand how firefox can be simultaneously the least picky about certificates and the most likely to spuriously decide they’re invalid.
i have wired sennheiser momentum 2s. the momentum line is on 4th generation now, and they look to all be bluetooth.
mine are great for use on the train, or the plane, or in bed for not getting hit with a pillow. fed from a phone, they’re a little weak in the bottom end — probably an impedance thing — but fed from a headphone amp they’re ace. (though it then becomes possible to leak enough sound to get hit.)
they’re not active noise-cancelling and they’re not sold for high isolation, but they keep enough in and out for any of my needs. and impedance matching isn’t an issue when fed by bluetooth, though then they’ll need to be kept charged.
It exists, it’s called a robots.txt file that the developers can put into place, and then bots like the webarchive crawler will ignore the content.
the internet archive doesn’t respect robots.txt:
Over time we have observed that the robots.txt files that are geared toward search engine crawlers do not necessarily serve our archival purposes.
the only way to stay out of the internet archive is to follow the process they created and hope they agree to remove you. or firewall them.
i made the same migration from markor (files in a folder) to logseq. there’s a lot to be gained - always-preview alone is a game changer - but on mobile the visibility of the keyboard can be fiddly. once in a while you’ll feel like you’re in vi, it has such a mind of its own. but i’m not planning to go back
looks great! the catch for me is that my current host doesn’t have docker support. your dependencies don’t look crazy so in theory i could burst it and install directly to the host environment, but at that point i’m giving myself grocy-level headaches.
reading about docker-capable hosts, i was surprised to see them starting at 1GB RAM - i couldn’t run pac-man in that. what would be a reasonable expectation for kitchenowl?
i haven’t tried the docker route - it seems fairly new. it also doesn’t seem like it would fix the issues i ran into. containerization is great for insulating the app from external dependency hell and environmental variation. but the problems i’ve had involve its own code and logic, and corruption of a sqlite database within its own filesystem; wrapping issues like that in a docker container only makes them harder to solve
again not foss so won’t dwell at length — but i use fund manager from beiley software. commercial, but works double-entry and handles more investment complexity than a human could ever need. windows app, i run it under wine on linux and crossover on mac. (i don’t own a windows box — that’s how irreplaceable it was for me.)