Explaining the problem and the details.
- Lingua principale
- C
- Stelle
- 3.4k
- Fork
- 177
- Merge medio
- 2g 15h
- PR unite (30g)
- 2
Descrizione
It seems like the issue of fake flash and why applications like this are needed is not clear to quiet a lot of people.
When I discovered your application (I searched a replacement for h2testw for linux and asked on askubuntu), there was a lot of information on the website of f3, but now it's gone. I only have sources in German, so I wonder how to explain the problem to people who can't read it. And even those sources are not explaining technical details. The given sources on your website and the page of h2testw do not really look like a good overview that can be trusted on (they look like those automatically generated pages at first sight and I can't see who wrote it). [The people here](https://askubuntu.com/a/805611/67724) for example seem to be very sceptical and also raised the desire in me to read into why again a tool like this is necessary, and dd is not always enough (there was some stuff about flags and caches on your website, I think).
So, I suggest to bring back (or if it is there, highlight) some information about the problem itself and some technical details to help people understand it. Like this:
* How is h2testw a method and how does it work?
* What documented cases of fake flash are there?
* Why does it need an extra tool? Why is `dd` not enough?
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Valutazione
Questa issue non è ancora stata valutata.