One thing I didn’t mention is that VoLTE requirements will make this harder than it used to be. I’m not sure there are any usb modems that would work with mod_gsmopen that support it. I found some cheapish GSM<>VoIP gateway on AliExpress but the only support GSM, so they are useless in North America.
It’s doable by hosting your own Asterisk or FreeSWITCH. You can accomplish this in FreeSWITCH using a GSM/LTE modem and the mod_gsmopen module. FreeSWITCH can also be used as an IMS provider for VoLTE, but that’s way too involved and probably not attainable for a home gamer. In Asterisk (or also an option for FreeSWITCH) I believe you will need an GSM to SIP Gateway which is going to be a bigger investment in terms of hardware as they tend to be rather specialized.
I know you said you’d pefer the physical sim option so you can pay chash, which is valid. But also have a look at https://jmp.chat/ service, they are good people. They provide a SMS enabled gateway you can connect to with XMPP and specifically support multiple recipients.
Postmarket and Mobian sure do have VoLTE on certain phones. OnePlus 6 for example. The trick is it needs to be abled first before you wipe Android. But I remember someone posting a workaround recently.
Yeah that do, I remember that the demo was pretty impressive ten fifteen years ago!
And you better inspect and execute a downloaded copy, because a malicious actor can serve a different file for curl/wget than to your browser
Home Assistant can absolutely do that. If you are ok with simple intent based phrasing it’ll do it out of the box. If you want complex understanding and reasoning you’ll have to run a local LLM, like Llama, on top of it
All I can tell you is that Conversations didn’t send your messages to Google. The servers you used didn’t send your messages to Google, and if you were using OMEMO, they couldn’t even they wanted to.
Then it’s probably just a fluke.
Notifications with full message contents?
Did you search for anything while having that conversation?
I don’t think that was very clear since other people also assumed you were using it as your account in Conversations.
A recovery email doesn’t really have anything to do with XMPP. Using Google or whatever won’t make them be able to read your messages.
If OMEMO was on, then Google didn’t read your message. Also now you say you weren’t using your Google account but a server from jabber.network? How about your interlocutor? If both of you were using an account for a random server on the jabber.network list, then Google wasn’t reading your messages, even with OMEMO turned off.
XMPP is not end to end encrypted, so whatever server you use, unless you own it, will have access to your messages.
Almost every current XMPP client, including conversations, supports OMEMO E2E encryption by default.
I don’t think it’s legal in Quebec under provincial privacy laws.
Absolutely. Simply use ACME with the DNS validation method. Using bind you’ll want to create keys and allow TXT access for those keys to the validation domains. Fear not, this isn’t exclusive to bind, ACME tools supports dozens of other backends. That’s all you need the actual domain doesn’t need to be resolvable with an A/CNAME record. Internally you can run an entirely different DNS server to resolve your hosts, use hosts files, or use bind zones.
Except it isn’t. Saying it is trivial is just gross generalization. It’s trivial to configure bind to have internal zones that aren’t resolvable publically. It all depends on configuration, such as reverse ns entries, zone accessibility, etc.
You can have (sub)domains that are listed in the certificate lists and yet aren’t resolvable externally as well.
It’d be better and more accurate say the list of certificates then.
Sub domains aren’t public unless your DNS server has XFER on.
Ah man, they beat Thought Emporium’s Torment Nexus to the punch!