The latest release is dated 2 days ago https://github.com/markqvist/Reticulum . Actively supporting is not the same as actively developing.

This should probably be taken as “I am tired of supporting everyone who did not RTFM, too bad if you can’t make it work” and is a totally reasonable thing to do, especially as the project gain more traction.

There is a pretty good community around reticulum that is usually supportive.

The reticulum project with the Sideband client is probably a lot more censorship resistant than DeltaChat or Meshtastic.

For those of you who are interested in this but don’t know where to start I think https://www.freedombox.org/ may be a good starting point. It’s been around for a long time, provides easy enough installation and a nice web interface for management. Its based on Debian and you can give it a try on their demo.

Also the vision for the project aligns pretty much with what op is saying https://wiki.debian.org/FreedomBox/Vision

This is not what you asked for specifically but check out tqm https://github.com/autobrr/tqm it does everything you want automatically. It takes a bit of fine tuning but it can handle a lot of scenarios.

I have two Yale Zwave locks that are at least 11 years old and still kicking. The key factor to this is the non reliance on the cloud.

Zigbee, Zwave, Esphome and other non-cloud will always work longer than any cloud based solution that is at risk of being shutdown, use a outdated or no longer available app, become a subscription, etc.

I agree with you that they should be required by law to open their code and unlock the devices but I doubt this will happen any time soon.

I am doing this with my personal and work laptops. I have two dell docking stations and a KVM to switch between the two.

It will work, probably not well. There is a ton of factors to take into account.

1- When switching the KVM input, depending on the KVM, the screens just get disconnected, meaning that the screens get re-detected each time you switch. Sometime it works well,sometimes not. Your laptop may also enter sleep mode since it is closed without screens attached. You may have to open it and press the keyboard if the USB from the KVM and docks are not re-detected.

2- If you use Displayport MST to connect your screens you have to make sure both the dock and KVM will support it.

3- When switching the KVM USB also gets disconnected and reconnected, it can be problematic with your dock, also see end of point 1

I have both high quality (and too expensive) docks and KVM that I took time to research and it works ok most of the time but still glitches. The docks and multiple screens add complexity to the setup and fail points.

If you go this way you will want to take your time and make sure all the pieces work together, I would steer clear of cheap Amazon stuff also.

• KVM : iogear GCS1964
• Docks : 2 WD19S
• Screens: 3 Dell U2415 connected through HDMi

To answer the last part of your post:

So far my experience is that the RCS-iMessage feature is working (or not) depending on the Apple user’s provider. I’m on Android with a “cheap” provider in Canada and RCS-iMessage work with my iMessage contacts that are on major providers but those on cheaper providers don’t work yet.

So if you are on Android and your basic RCS works you should be good.

I have had Zwave Yale locks for almost 10 years now and am pretty happy with them. I have the assure SL (mentionned in another comment) on 3 doors right now and they are rock solid.

The battery is reported to Zwave but you will also get some beeping and flashing on the lock itself when the battery gets low, so even if you don’t see it in HA it is hard to miss and end up with a dead battery.

As a side note, I always bought the push button variant of those locks and stayed away from the touch pad version. Living in Canada it seemed like a bad choice to deal with touchpads in the winter with the gloves and snow possibly melting on it.

Canadian here who used both small and big providers with pixel phones (3, 5 and 7 pro) bought directly from Google (not financed through the provider).

Not all smaller providers provide 5G but they all have LTE or LTE+. I had 5G working with my Pixel 5 without issue when I was with one of the large providers. I’m with a smaller provider now on my Pixel 7 pro and have no issue connecting to LTE(+).

But, you also mention the Pixel watch. I never used a watch with a sim card and I have to say that it is not always clear from the provider’s website if they are supported or if they will provide a esim for them or not, and at what cost. This is something that looks a lot more straightforward when with Apple than Android.