thanks, i'll look again. it's not that i love the idea of being fingerprinted; i just think that five mylar bags, four tin hats and a partridge in a pear tree won't save me from that. i need my password manager, and once that's in, enforcing a generic screen is silly - cow's out of the barn. but not having the arms race against pocket and telemetry would be a big bonus.
i did try that but the never-dark mode blinded me. i understand the reasoning, but absolute anonymity isn't my own threat model; i'd like to be able to use themes and resize the window
an interesting oddity: on my non-rooted xperia, signal thinks that i don't have play services and so it falls back to… polling. every five minutes. killing my battery and my logs.
i had to put signal into the restricted battery group, which means no notifications. i anxiously await the new molly, as i already have a unified push environment. it looks like the migration will be a bit delicate.
neo store refuses to run if you don't grant it the right to send notifications and bypass battery optimizations. if an app demands a permission and doesn't have a plausible explanation why it needs it, i don't keep it :/
imo magic earth is a navigation app, full stop. it does that amazingly well, including live traffic, but i wouldn't use it for anything else. organic maps is a better general-purpose map but isn't a patch on magic earth for nav.
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.
Our map data is often downloaded and used offline on various devices for several weeks or months. For offline data to be useful, it should at least be expected to remain unchanged in the next few weeks when you map it.
yes, by this blurb, concession for offline users does supersede safety.
i'm an editor active enough to have been granted foundation membership but hadn't known this rule; it indicates a view of osm as analogous to a paper map rather than for real-time navigation. if a change of less than weeks' length is discouraged, i can't in good conscience steer my friends away from google maps, as navigation is not a primary use case.
1
flashback: zine slags off simple minds' "awful garbage" song for "bad movie"
(poptalk.scrubbles.tech)
i was cruising the music site looking for backfill songs i might buy, and was rudely reminded of the state of music criticism in the 80s (to be fair, this was from a zine, but was put in front of me by qobuz, so it had some staying power).
this hatchet job on the blink-and-you-missed-it "don't you (forget about me)" by some scottish dudes called simple minds, for the soundtrack of a very niche and forgotten film, reminds me of everything i escaped. it's probably from "the big takeover" issue #17 from 1984.
i closed the tab. no sale.
For six years this was a creative and interesting Scottish band that used synths in artistic ways to go with Jim Kerr's Roxy Music-like yearning, poetic vocals to forge lovely, danceable, moody soundscapes full of promise, enchantment, and sinewy shadows. So now they get to do a hit song for a bad movie, and they suddenly turn into every cliché you've ever heard, complete with Kerr doing what he said only last year he never would: singing the word "baby" in a pop song (repeatedly at that!). They didn't write this song, but it's their name on it and they recorded it, and sure enough this awful garbage is heard everywhere after no one in the U.S. ever played one of the band's great songs outside of nightclubs. Sorry Jim, this is obviously the most forgettable thing you've done so far. Hopefully the next LP will make this look as asinine as it is, a bad one-off, but experience tells us that once you open Pandora's box, you can't close it again, especially if it yields sales instead of ridicule.
© Jack Rabid, The Big Takeover /TiVo
n.b. all good pop songs have "baby" in them. repeatedly. sorry, jack
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
from TerribleMaps: https://en.osm.town/@TerribleMaps/110684461612856823
well i feel stupid now for not doing the obvious. but…
on the PPA box, this is what it showed me (meanwhile it was attempting to connect to incoming.telemetry.mozilla.org). another symptom of displaying respect for enterprise policies but in fact ignoring them. (as i had mentioned, on this box all of the settings look locked down as they should be, but it's still attempting to send telemetry.)