1
point
lukechilds
Joined 26 karma
- lukechilds parentThis is a good suggestion, we're taking a look into it.
- Hi Umbrel CTO and cofounder here, appreciate the thoughtful feedback.
> how do I keep using this thing in 5–10 years without your cloud, your app store, your updates?
The code is publicly available with a non-commercial restriction. If Umbrel the company disappears it's possible for a community maintained fork to live on. Someone else in this discussion mentioned that the NC clause hurts maintainability due to no future company being able to profit from taking over maintenance. They suggested we add a clause revoking the NC restriction if Umbrel goes out of business. It's a good suggestion and something we'll definitely consider, I think it should be possible.
Regarding apps specifically, we have the concept of "community app stores". Anyone can host their own app store which is just a public git repo that any other user can use by pasting it's url into their web ui once. Community app stores completely bypass our main app store, they don't rely on our infrastructure and will continue working if we disappear. There are already hundreds of community app stores in use:
- https://github.com/getumbrel/umbrel-community-app-store/fork... - https://github.com/search?q=in%3Areadme+sort%3Aupdated+-user...
> automatic off-site backup that isn’t tied to one vendor, painless replacement/restore if the hardware dies
We recently shipped backups baked directly into umbrelOS. You can backup to a local NAS, USB device, or another Umbrel (local or remote). You can restore individual files from hourly/weekly/monthly snapshots, or restore the entire state of your Umbrel onto a fresh device from your backups.
https://x.com/umbrel/status/1970508327479320862
> portable across generic hardware
We currently support running on Raspberry Pi, all amd64 devices, virtual machines and there is unofficial support for running in Docker.
> The interesting opportunity here isn’t selling a fancy N100 box, it’s turning “self-hosted everything” into something your non-technical friend could actually live with.
I completely agree, that's the plan.
There are some sats left on that wallet, help yourself.$ docker run -it lukechilds/ephemeral-electrum "much bottom such hurt hunt welcome cushion erosion pulse admit name deer"HD wallets can be loaded as Electrum or BIP39 mnemonic seed phrases as well as extend public and private keys.
Single addresses can be loaded using the Electrum address-type:wif format.
The Docker container automatically creates an Electrum wallet file importing your seed/key, then starts the text based interface for Electrum.
Once you quit the process everything is destroyed. It's all isolated to the container, nothing is persisted to disk.
It's pretty handy for just quickly checking the state of a wallet/address or monitoring test wallets while developing.
Hopefully some people find it useful.
- 18 points
- 2 points
- It can't, as per the BIP39 spec[0], the mnemonic is run through PBKDF2 to generate the seed that is actually used.
So even knowing one or two of the input words doesn't tell you anything about the actual seed.
[0] https://github.com/bitcoin/bips/blob/master/bip-0039.mediawi...
- 2 points
- Only if you want the entire dataset. Datasette allows you to query for a subset of data.
- 2 points
- libui looks amazing but it's not quite ready yet https://github.com/andlabs/libui
- Unless I'm misunderstanding something, an Electron app also has direct unchecked access to users' files by using the Node.js 'fs' core module.
- Strange...
Is it a symlink or something? Does `ls "$NVM_DIR"` list nvm.sh anywhere?
- Ahhh, zsh-nvm requires that nvm has been installed via git.
Although it shouldn't be trying to install over your previous installation, it checks if nvm exists first with `[[ ! -f "$NVM_DIR/nvm.sh" ]]`.
Out of interest what does: `[[ ! -f "$NVM_DIR/nvm.sh" ]] && echo "nvm doesn't exist" || echo "nvm exists"` return?
If you wanna try it out you could backup your "$NVM_DIR/versions" folder and restore it. That holds all your node installs and global modules.
- It should work fine with existing nvm installs, have you commented out the line where you're manually sourcing nvm?
If you have can you paste the exact message you're getting?
- If you use zsh I wrote a little wrapper for nvm that adds a few handy features. Upgrades can be done with `nvm upgrade`.