Feel free to use a software that suit you more.

That didn't need to be said. Please keep it civil, Tbaut. I put a lot of work into posting to help find bugs and help Parity become better by explaining other use cases, etc. I personally don't use any UI.

You are not using Fether for what it's intended to be used for

Where do you have a site that states what Fether is intended to be used for? Because at the moment it works with the SSH tunnel that is described on the Parity wiki. At least, it did many months ago when I helped test it for you. I have not used it since then.

we will not trade security for this use case

What use case? The use case of an SSH tunnel that the Parity wiki recommends? That is very secure. If people do not use it correctly it is not secure but if that is the problem then your priority is not security but fool-proofing. Maybe that is your priority, I don't know? To be a good end-user tool that anyone can use. This is not stated anywhere so I was assuming something different.

Or do you not want to support the use case of a Parity node on a VPS? Or the use case of a person living in Venezuela? Or the use case where "Fether will automatically connect to any Parity Ethereum node that is already running (using WebSockets port 8546)." (That is from your FAQ).

Exactly what use case is Fether for? I think one problem is that you are not being clear about this when you say "Parity Fether aims to be the lightest and simplest decentralized wallet." De-centralized sounds to me like the opposite of requiring that Fether runs on the same computer that the node runs on.

Use IPC instead of Websockets #546

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions