got my tech within the last year, was stunned at how not old-white-guy the class was. all age groups, balanced genders, mixed races. many seemed there for neighborhood emergency teams. the airwaves are dead most of the time i’ve turned the rig on, except during the net hour. i feared exactly what you’ve heard but thankfully haven’t run into it. yet.

it seems to me that flying drones into trees would be a massively expensive hobby

2m fm, 146.820 (in new orleans)

Welcome! I’m a new amateur in the States. Like you, I peek in here and find that at the moment, it doesn’t take long. The frog boil has worked quite well in Reddit; the frogs are staying in their pots even as enshittification becomes obvious (pro tip, it’s spelled IPO). Unlike you, I’m new enough that I have nothing worthwhile to contribute yet.

As for Mastodon, I’m on an instance with a 5k character limit. Some instances run modified versions known as glitch or hometown, which allow the admin to set a limit (well) above 500. I didn’t find a handy list of these easily, but a little searching in google or r/Mastodon may turn up ideas.

It’s a very heavy building - multiple stories in earthquake country, and I’m not on the top floor. Everything dies when I leave the nook with the windows. NOAA works literally only on the windowsill, TRACON almost never clears the noise floor once I’m not near the window, and I hear some smaller UHF repeaters away from the window but haven’t yet heard the 2m (it’s not super high traffic, so can’t say I haven’t just been unlucky).

We’re allowed on the roof and I’ve been up there, everything’s peachy. When I’m at the office downtown, I’m on a high floor, so I can pick up the 2m easily even though I’m on the other side of the building.

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.)

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.

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.

https://blog.archive.org/2017/04/17/robots-txt-meant-for-search-engines-dont-work-well-for-web-archives/

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