firmware VS davx5-ose

This is a fantastic idea, thanks for sharing. I feel like LoRaWAN and LoRAMESH are the perfect solution for shuffling messaging around for home and property sensors, easily traversing a couple miles in poor conditions.

Prior to seeing this I was thinking about how to use the Meshtastic [0] project to fundamentally provide simple UDP services for message brokering over LoRa. There are so many sensors that could easily hook or connect to devices acting as network routers that could bridge other protocols across long distances very easily.

Have you looked at doing something similar with ZWave at all?

[0] https://meshtastic.org/

Truly independent peer-to-peer internet when?

Seriously, I think more and more about building a LoRa network with friends. https://meshtastic.org/

Agreed-- at least relaxing the restriction for UHF/SHF signals on a "secondary usage" basis (traffic must yield to plaintext). Potentially with with reduced power (say 100w) or minimum directionality, but I think a 'secondary usage' would be sufficient. Without doing so virtually all experimentation will continue to be deflected onto the ISM bands and we will lose our allocations through disuse.

So long as identification is still decodable, spectrum usage can be managed.

It's sufficient to prohibit commercial usage you don't need plaintext to do so. The old threat of tow trucks and cab services moving onto ham-bands had long since been mooted by ubiquitous cellular, but even if it weren't any significant commercial usage will eventually have a whistleblower. Usage that is obscure enough to not be vulnerable to whistleblowers could also be hidden just as well in "plaintext" traffic that was really uncrackable steganography.

As it stands you can't even lawfully log into your own personal systems over amateur radio even if you take the unreasonable steps of using specially modified software to authenticate-but-not-encrypt because inevitably some third party will send a message to you via the internet that contains some naughty words that aren't permitted over the radio.

Without relaxing the encryption rules, innovative radio usage like meshtastic (https://meshtastic.org/) will continue to be pushed onto ISM bands where (1) they're still technically unlawful because the homebrew hardware is not type-accepted (amateur bands are the ONLY place where homebrew intentional radiators are allowed!) and (2) where the band choices, power limit, and EIRP limits are detrimental to full exploration of the possibilities.

Besides, the FCC has long allowed proprietary, license fee bearing, patent encumbered digital modes. These are very close to encryption in terms of their ability to lock others out of ham comms, and have frequently been used by amateur radio groups to establish "lid free" communications channels. (Because most of the more irritating people aren't technically sophisticated enough to adopt some new mode without help, and people won't help them...).

The rules as they stand punish honest people who follow the intent and spirit of the rule in favor of people willing to just ignore the rules (including operating unlawful devices in ISM bands), willing to use stego, or willing to use obscure protocols to achieve the same ends that they'd otherwise achieve with encryption. It blocks modern networking by disallowing standard internet-grade software use with radio since all of it has integral encryption which generally can't be disabled to prevent downgrading and cross domain attacks in contexts where the encryption is needed -- or because in some cases the protocols are designed in such a way that authentication without encypherment isn't possible.

Meh.... very very low range.

For ~$20 you can get a LoRa dongle and https://meshtastic.org/, and with some luck (someone putting a node on a hgh building or a hill), you can reach quite impressive distances.

Meshtastic (version 30109): An inexpensive open-source GPS mesh radio for hiking, skiing, flying, marching.

DAVx⁵ [0] operates under the same principle and they seem to have success with it.

[0] https://www.davx5.com/

As someone who has moved between macOS+iOS and Windows/Linux+Android several times, this is doable. For technical people, it's just annoying. For non-technical people, this probably needs written into a more formal set of steps. If you have the need, one can setup your world to work on both systems transparently, but that takes more work.

Caveats: iOS messages can be kept, but they'll be in files, not your new message app. Photo edits will be lost unless you take extra steps.

Messages: if you are comfortable with it, use imessage-exporter (https://github.com/ReagentX/imessage-exporter) on your Mac to export your messages to disk. Copy to new machine. Validate you got what you wanted! Can also be used to decrease iCloud usage by backing up messages and deleting the originals from Apple Messages.

Photos: three ways. 1) open up the macOS photos app, select all photos, and export them. This will make any JPEG photos much larger than they originally were due to ridiculous default quality settings. 2) If you have access to a Windows machine, install iCloud for Windows, let the photos sync, and copy them to a new directory. 3) Use iCloud's web UI to download all the photos on the new machine.

Mail: pick a new provider. Several ways. 1) Add the new provider account to macOS mail. Copy and paste your emails/folders between accounts. 2) Create an app-specific password for iCloud, use the provider's migration facility (most major players support this and it will move your contacts and calendars).

Calendars: if you are sharing calendars with iOS users or will keep some Apple devices, keep iCloud as your primary calendar system. Use DavX5 (https://www.davx5.com/) on Android to setup a two-way mirror between your Android calendar app. Your email provider may provide calendar mirroring (Fastmail does, for one). If you aren't sharing / using your mail provider, export your calendars to ICS files from Apple Calendar and import into your new calendar app.

Contacts: if you will continue using Apple products, keep iCloud as your primary contacts system and use DavX5. Otherwise, open macOS Contacts, select all, and export to a VCF file. Import this into your new Contacts app.

Documents: copy to a backup drive from the machine, download them from iCloud on the web, use iCloud for Windows for the initial sync. Whatever suits you. If you are using Apple's office apps, be sure to load and save as a more universal format.

Check their website : https://www.davx5.com/

https://www.davx5.com/ this has more info.

DAVx⁵ (version 403020001): CalDAV/CardDAV Synchronization and Client

Is this different or better than https://www.davx5.com/ ?

IDN depends on you, all fairly basic stuff TBH Rooting depends on the model, pixel 4: https://www.xda-developers.com/google-pixel-4-root-magisk/ F-droid App repo: https://f-droid.org/en/packages/org.fdroid.fdroid/ Setting up DNS, 1.1.1.2 provides some malware blocking: https://developers.cloudflare.com/1.1.1.1/setup/android/#configure-1111-manually Private email require you own a domain. Migadu has instructions on setting of the mail (MX) records with your provider, I use namecheap. I use this opensource app for caldav(calendar sync) and cardav(contact sync). https://www.davx5.com/

I now use CalDAV Synchronizer to sync Outlook to my Radicale CalDAV / CardDAV "server" (a Raspberry Pi), with DAVx running on our phones.

There is a similar problem with Dublin timezone in Davx5 / iCal4j: https://github.com/bitfireAT/davx5-ose/discussions/265 (and noone cares)