frame VS syncthing-android

Regarding your earlier comments on Frame, did you try the AppImage? At least on the x86 side of things, the AppImage just works, and I don't think I've ever seen an AppImage that didn't "just work". The arm64 version can be seen on their releases page here: https://github.com/floating/frame/releases/tag/v0.6.6

Using frame.sh instead of metamask helps. It isn't connected to a single chain at a time, but all of the chains you've added. For example you can use dapps on multiple chains at the same time but never go through the step of switching networks. Also sounds like what you're really complaining about is delay period for fraud proofs, that should not be abstracted away because bridging without waiting is likely costing you more than you're making in returns if you bridge too often.

MetaMask provides an extension to add a wallet feature to your browser so that you can interact with dapps. This was the first project to provide this feature back in the day, but it's now quite outdated; A much better alternative would be Frame. A wallet needs an RPC node to talk to, and a new user doesn't want to have to worry about this, so MetaMask uses Infura as their default. But you can go into settings and change it, either to your own node or to a node hosted by someone else.

As your next step, I'd suggest trying alternative apps for accessing and managing your account(s). I'd personally suggest Frame (https://frame.sh/), but most use MetaMask (which is available as a browser extension).

gotcha, maybe check out frame (https://frame.sh) — you can import any wallets, hardware, seeds, private keys, etc. If you want to use it with any defi, there’s a companion browser extension.

I work on Frame (frame.sh) and used MEW to get a keystore file for testing our import keystore flow. The file I got was a different version (v4) and format from the expected v3, and our import flow does not support it at all. Digging deeper, we use `ethereumjs-wallet` to parse the keystore files - this library does not have a fromV4 method, and the existing fromV3 does not work at all with the MEW file.

Just wanted to install frame.sh as a new web3 wallet. It tells me to add "frame companion" to Edge, it warns me about:

So try MetaMask, or my personal favourite for stuff like this is: http://frame.sh and play around with derivation paths.

Frame Wallet does a few things Rabby doesn't and also supports hardware wallets but lacks the contact security check.

We use syncthing to share files between our machines. It avoids is having to use dropbox / OneDrive etc. You just choose a folder and it automatically syncs it in the background.

https://syncthing.net/

This very hn entries is bust contradicting your statement.

Also what about syncthing[1] (for recurrent/permanent sync) and croc[2] (for one time copies) ?

I have used both for a number of years already.

[1] https://syncthing.net/

[2] https://github.com/schollz/croc

I would use syncthing, which is open source at https://syncthing.net/.

After minimal setup, it just works(tm).

You have a normal directory in your filesystem, that is synced to the other peers (which you set up in the "minimal setup").

I have been using it for years, and it works well. It has no problems crossing os'es (i.e. windows -> linux, linux -> mac)

For windows I usually recommend https://github.com/canton7/SyncTrayzor, but vanilla syncthing works fine too (but don't try to mix them!)

Do consider Syncthing particularly if you are using Android. If using apple iOS you'd need the möbius sync client.

https://syncthing.net/

https://www.mobiussync.com/

One thing that it beats the cloud / centralized sync on is because the connection is direct between devices when the initial transfer is completed the file is completely there on the other device. With a cloud type of sync you do the transfer twice. I've seen stack up on large media or with the structure of cloud services pricing making it expensive depending on how your workflow is setup with inside and outside parties. For example, Dropbox deduction from all parties' storage limits not just the sharer.

You can also point Syncthing at a local sync of Dropbox or Google drive and then forward the files to other recipients from that for some purposes.

I think sync is a non-feature, as you can just ride on your existing solution.

For example, I use syncthing [1] with Obsidian to sync files off-cloud.

https://syncthing.net/

When I was 14 and just getting started, I used Notepad. Upgraded to Wordpad when I realized I loved putting italics in every other sentence, moved to Google Docs at around 25 when I started writing on my phone and wanted to sync with my computer, finally moved to Obsidian a few months ago (with Syncthing for syncing) when I decided I don't want to live in Google's house where they can burn my stuff down whenever they want.

Pick it up again an use cloud syncing this time! Is worth! https://syncthing.net/