Magic Wormhole reminds me a little of SimpleX. They both somewhat address the problem of Signal having IDs and a single monopoly server where $govt$ can do traffic analysis. They both have the problem of transferring a non-ID, ID token.
Just thought I’d send y’all down a rabbit hole… You can thank me later.
the problem with reading QR code is that Warp or iOS/android app generate just wormhole code (wormhole-transfer:2-some-code) = does not contain rendezvous or role …
so around this piece of code will need more enhancement to use default values if they are not in QR code…
else if (content.rendezvouz != wormhole.mailbox) {`
app.popup("QR Code URL is using a different connection profile!")
Thanks for the analysis.
I try to set the defaults in the URI parser correctly, but that rendezvouz part was a typo/thinko.
Shoud be fixed in 0.3.8 (8139e0a).
now it is working, reading and start receiving from Warp or iOS app automatically ![]()
for next transfer app must be killed. also phone must be locked/unlocked to start new readings otherwise camera only focusing and not reading. anyway if it reads qr code for the second time transfer will not start, still need to kill app.
0.4.3 should fix the restart after completed transfers issue.
0,4,4 fixes a regression caused by 0.4.3. argh!
And now we’re into python dependency hell proper:
Connecting to wss: instead of ws: websockets fails.
The pip-installed cffi is not compatible with the system libffi.
OK, we can recompile cffi on pip-install, but this then links against the system libffi which is not allowed in Harbour.
And while I can use __provides_exclude and __requires_exclude, that apparently is not enough for the links-to-libray scanner from the harbour validator.
@poetaster any ideas?
It’s not a very good situation. On the up side, it’s a setup.py so there is a single point to intervene (beside rpm patching), but you’d have to have 2 submodules including libffi as well.
EDIT: I’d remove cffi altogether and see how it performs. It’s in the _util.py bits of the OpenSSL lib Gin, and sat up against.
It’s actually NOT a very safe thing they do here anyway (ie. not zeroing allocated memory.) Might kill performance though.
Update: the first try in getting this into Harbour has been rejected.
Reason is currently it uses Amber.QrFilter, which is not allowed.
@vige kindly opened a PR to allow that, lets see how that progresses.
Meanwhile, I’ll disable/rip out QR code scanning and resubmit at Harbour. Maybe I’ll do a “plugin” for qr code scanning, published on Chum like I did with Lonewolf.
Mælstrøm 0.4.6 (without support for QR scanning) has been released in Harbour! Enjoy!
Still some quirks left to work on, but basic functionality is there.
Are there any plans for a 32 bit version? I really wanted to use it to send files between my XA2 and Xperia 10 iii.
The problem is the python dependencies.
Some of them are not available (as binaries) for 32bit ARM and I can’t build them.
If someone succeeds in making a usable set of python deps I’ll gladly merge them, but myself I can’t.
This may get resolved in SFOS 5.1+, when we have newer Python, but that’s unknown for now.
There is an official implementation in Rust.
This can help avoid Python dependencies.
Thanks. I’m aware, but Rust is even more of a can of worms than Python, when you’re trying to build offline (like on OBS).
Also, while there are great efforts to get the situation improved by rubdos and others, currently there is no really usable rust toolchain available on SFOS.
Thank you for the app! I discovered Magic Wormhole because of it.
Hey @nephros! After translating Maelstrom into Swedish I am actually trying to use it. ![]()
I found that it works pretty well with the Destiny profile, but I never got it working with other clients, but that aside, there is some gui strings that doesn’t translate at all, and I thought that I could fix that. I just need to know if you prefer the .qml version or the .ts one?
I can do either of them and make a PR if you wish?
Ooh yeaa… what do you use to transfer wormhole code to peers?
I don’t think SMS seems really applicable here. ![]()
You mean they aren’t wrapped in a qsTr() at all?
Possible that I forgot some.
Others may be are coming from somewhere that makes it hard to translate.
I’ll happily merge both qml and ts, but be warned that some parts of the qml are really a mess ![]()
Ah, there’s qml/config/profiles.js which describes the profiles - that’s currently not translatable.
Got to figure out how to make it so…
No, I mean the text is totally different. Two versions.
I guess .qml is the one to go for, so I’ll just edit .ts file?
It’s mainly about the leading info site… first app launch, after install.
