btc-rpc-explorer VS flood

Get a non-custodial wallet: This is where you start to believe you really have Bitcoin, but it is still not perfect. A non-custodial wallet (like BlueWallet) is one of the slow types of Bitcoin wallets (on-chain) but this is where I think you, as a inquisitive mind, should start. Others will start with lightning wallets so they can buy beer right away. BlueWalllet has you create a "wallet" and gives you "seed words" to write down and keep safe. This is private. Do not take pictures of it, screenshots of it, and do not save it to a digital file. Paper is really easy and there's no risk of undiscovered malware being able to see what you write on paper. You'll very quickly learn the lingo: "wallet", "addresses", "utxo", etc. When you receive funds, the wallet will show you your balance like Coinbase does, but it will also show you a "transaction id". This, you can use to check that your transaction is real by checking a blockchain explorer like "https://mempool.space" or "https://bitcoinexplorer.org/". You are now able to check multiple sources, increasing your belief that the Bitcoin is real.

- Bitcoinexplorer.org https://github.com/janoside/btc-rpc-explorer (lang: nodejs, db: none) I would like to prioritize practical issues such as displaying fees and general ease of use for viewing transaction details, these are the topics of discussion. I am looking forward to your opinions.

I'm not aware of a desktop explorer, but it probably wouldn't be as advanced as something like https://github.com/janoside/btc-rpc-explorer

BitcoinExplorer — https://bitcoinexplorer.org/

It depends what you're running. Raspiblitz, for example, allows you to use btc rpc explorer (https://github.com/janoside/btc-rpc-explorer) and mempool (https://github.com/mempool/mempool) quite easily.

BTC RPC Explorer v3.3.0 (Released: 7th December 2021) - https://github.com/janoside/btc-rpc-explorer/releases

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Only one that I'm aware of is Flood: https://github.com/jesec/flood

If you haven't seen the https://flood.js.org project before. It has subjectively a nicer ui and works with qbittorent.

You can install alternate web UIs very easy. I’m a big fan of Flood, which is mobile friendly: https://flood.js.org/

One note: I lean heavily on an API to manage it so I'd love to continue using flood, I tested qbittorrent with it briefly and it didn't go well.

You mean a torrent client? I’m using rTorrent with Flood (the new jesec fork that’s actually active) and it works brilliantly on mobile

https://flood.js.org/ ?

If it's just the web ui you're worried about perhaps look into installing Flood & see if it helps? It's going to be a better web ui overall. (I've never needed to use it personally but it's been recommended in the pat)

qbitorrent-nox with flood-ui

Impressive. But I dont get why they would rebuild the web client when there are existing options like: https://github.com/jesec/flood