Nine year-old Tawnse and I got half-way to activating the park before the ML-300 Bluetooth transmitter gave up the ghost. I knew I forgot to charge something. Tawnse was so entranced with the walled Philadelphia park she thought we should have stayed the extra half hour we would have probably needed to activate it. What led Tawnse to this scheduling priority decision? Turns out the park doubles as the neighborhood dog park. There's only one way in or out though a small and, of course, historic cemetery. By the time the pups got to the wander-around-unleashed bit we were in they were far to transfixed to try to leave. Turns out two of the pups were aspiring radio engineers to boot .We ’ ll get to that. Because our antenna was low, propagation wasn't great on 20m at 15:30 UTC on the East Coast next to an interstate in Philadelphia. Even so right after I self-spotted a fellow ham immediately called in from South Dakota. After that, the QSOs came in every five minutes or so on
The gang and I are very lucky to live in a San Francisco neighborhood where we have markets, a family owned pharmacy, and family-owned restaurants, coffee shops, and delis all about a ten block walk from the house. Here’s the haul from our Farmers Market that we walk to along with our local butcher shop and dim sum bakery a few weeks ago. Consequently when I saw a mention of local-first software ,[ via ] I was intrigued. (As a side note, the presenter, Maggie Appleton, at one point in the not to distant past , worked with Elicit, a research paper summarizing AI startup with an office in Oakland, so kind of surprisingly local, but I digress.) It turns out that local-first development advocates for keeping the data for an app offline, i.e. keeping the data with the person who created or is using that data by default. But, what happens to collaboration? Well, the local, offline data is synched to the cloud when a connection is available allowing for collaboration while also creating