Trunked is essentially useless to HAMs, and we never really use it much. We have essentially everything that trunking was meant to solve for a company; large pre-authorized spectrum space, self-coordination in that space without having to get fcc involved. Use of 25khz FM where part 90 is now only 12.5 also is enabled by being a ham.
> Trunked is essentially useless to HAMs, and we never really use it much.
I wouldn't say it's useless, but the utility is reduced because we typically don't have the density of users where two timeslots on a single channel becomes a real limiting factor. A repeater that's set up for local talkgroups on one timeslot and then open access on the second is generally more than enough unless you have a lot of people trying to use it at once, especially in a world where anyone who wants to can have their own personal hotspot for less than the cost of a HT.
I don't think it's useless at all. It would be amazing, roaming the country and never having to worry about frequency settings. And in that case you do need more time slots. Tetra would be nice with 4 slots. I know in Holland and Germany they're experimenting with it.
In the US frequency allocation within each band (including repeaters) is left up to regional spectrum management organizations (which have no legal authority). So it varies by region.
Here is the allocation for eastern New England for example: https://nesmc.org/docs/nesmc_bandplans_2023.pdf On the crowded 2m band we have 20 kHz for major repeaters and 9 kHz for smaller ones.
Leveraging dvmproject, dvmhost, and the FNE bits, hams can operate their own APCO Project 25 trunking systems with commodity MMDVM hardware and link them across the Internet. You can use various MMDVM boards, use a v.24 serial link to a Quantar repeater, etc...
I installed Ubuntu for many people in their 80s. Give her some time with FF, you don’t have to remove chrome, just hand her FF. I bet she does just fine.
Are you taking upon yourself to do this for all uBO users that need it without knowing?
If you do, you acknowledge that "Chrome disabling uBlock Origin is a serious security threat."
If you don't, then "Chrome disabling uBlock Origin is a serious security threat" seems even more true.
Either way, I'm curious on the size of your bet here. Talk is cheap, and you've only given OP the laziest and most obvious solution. Do you believe what you said is profound and/or an interesting argument?
I took that comment as a good faith offer of the experience of the writer.
I’ve had both experiences myself. Sometimes the older folks manage just fine. Sometimes they don’t. Sometimes it’s an aversion to change, sometimes it’s to cope with cognitive decline, and sometimes they just like one thing or the other, just like anyone.
The author has not seemingly considered the vastly different networking in wasm. You don’t have networking. There is an entirely different utility in these environments, containers are meant to host applications, wasm is an application. Don’t even get me started on disk access, env handling, etc. wasi is great, for the places it does well. It is not a replacement for writing a pure golang/rust/c/julia app and running it in a container, it doesn’t have the facilities for that task.
