Signal has started rolling out Signal Login, an optional registration method that allows users to create a Signal account without providing a phone number. The feature will be rolled out first on Android and will come to iOS later.
As we previously reported, Signal Login is not a free alternative registration method. Signal requires users who choose to register without a phone number to make a one-time payment. The price at launch is $2.99 / € 3.49, although this may vary by region and currency.
The main problem with XMPP (well for me anyway) is that the implementation of OMEMO that 99% of the apps use is woefully out of date, and Conversations (and their ilk) seem to actively resist updating because unless EVERYONE does it at the same time it will break interoperability.
The second problem for me is the ease of use, I’d have to physically set up accts for literally all my contacts on Jabber (everyone I know is stupid [it’s really just learned helplessness and it pisses me off to no end]), but on Delta I can legit say “here, click link” and it’ll bring up their app store on DC, then they DL and make an acct and then I say “click the link again” and they’re directly connected to me, done. So much easier. And then next time I see them I can say “hey give me your phone I’m gonna do stuff to your Delta acct” and I can add relays and create a backup for them, but at least we can get started easier.
Besides, they are working on forward secrecy afaik, and they’re one of the only teams making these apps that seems to acknowledge metadata’s existence, honestly they seem like one of the best options all things considered. Sure if your threat model is the US gov then maybe not, but better not use Intel or AMD or any android (incl Graphene, and I’m a user myself) or iphone then. Carrier pigeons maybe.
The whole ‘OMEMO is out of date’ thing started with Soatok’s blog, however what is less known is that blogger
removedchose to block/not approve a response in the comments from an OMEMO developer who clarified some things (you can it read here), which personally I think was rather odd/bad faith of them to do.According to that response, there’s nothing really wrong with the older OMEMO 0.3.0, as the developer considers it a stable standard that clients can safely implement, while the newer versions are basically public beta releases that are working toward a stable ‘OMEMO 2’ standard that can eventually replace 0.3.0, and be stable enough for all XMPP apps to implement at once, hence why most apps are remaining on the older version.
I absolutely agree that Deltachat has by far a smoother onboarding process compared to XMPP, and I think for most people, Delta is probably the better option.
Where XMPP shines is if someone needs access to more discord-like features, which is where the the Movim XMPP client (a web app that works across all platforms, Desktop and Mobile) does well, as it was able to use XMPP to have Discord-like servers with text and group voice chat rooms, as well as screensharing. It works quite well for the most part. There is still definitely some UX oddities in Movim that can add some friction, but the dev is quite open to suggestions for improvements, and it’s come a long way in recent months (the discord-like features for example were added just this year).
My blog hasn’t had comments enabled for years. People can write their own blog posts if they want to respond to something. Not becoming a dumping ground for other people isn’t “bad faith”.
Furthermore, I didn’t remove a response. I’ve always held comments in a moderation queue back when I did allow them, and I didn’t approve it. That’s all.
The reason for the moderation queue is obvious to most people, but if you find yourself unaware: Being openly queer, or part of the furry community, or both opens you up to a lot of harassment networks that try to cause grief. They might dox you and post this in a blog comment so it shows up on search engines, for example. So I never wanted to deal with that retroactively.
Could you elaborate how their response would be making your comment section a ‘dumping ground’? Was it not directly relevant to your issues with XMPP and OMEMO?
What was your reasoning for not approving it?
My blog exists for me to publish my writing. If other people want their own writing published, they should publish it on their own blog. “Mopar” clearly was capable of doing so.
Does relevance matter? If so, why?
What is your reasoning for thinking I owe you or anyone an explanation? My blog, my rules.
I guess I’m trying to understand what about the OMEMO developer’s comment made you not want to approve it in comparison to the 19 other comments you did approve.
You don’t owe anyone anything, I’m just trying to make sense of why you would choose to not publish that comment.
Based on the information I have at hand, it seemed like you wrote some strong opinions about the bad qualities of XMPP, and then opted to not approve a comment with information that may have made your opinions seem less strong? Without further insight into why you didn’t want that comment seen on your blog, I personally can’t come up with a different explanation that fits. 🤷
It’s not your or anyone else’s place to “understand” arbitrary decisions I made years ago. Whatever point you want to emphasize is moot anyway: Comments are disabled and users are encouraged to blog independently if they want to remark on something I wrote.
Consider yourself corrected on the “removed” remark.
Good to know, thanks!