search

akopachov / flipper-zero_authenticator

Software-based TOTP/HOTP authenticator for Flipper Zero device.
GNU General Public License v3.0
544 stars 25 forks source link

[FEATURE] List app in the Flipper Application Catalog #230

Closed ololobus closed 5 months ago

ololobus commented 5 months ago

Flipper Authenticator looks like a great app. It doesn't seem to violate any guidelines at first sight and has OSS license.

What do you think about listing it in the official Flipper Application Catalog? https://github.com/flipperdevices/flipper-application-catalog

Guideline is here

Sorry if answer is already mentioned somewhere and I just missed it :)

akopachov commented 5 months ago

Hey, that's a great question. Here is the answer why it is not there, and unlikely be there. TL;DR

  1. Flipper Catalog maintainers dictate how the code should be formatted in your repo
  2. They tried to dictate me what I can put to the description of my own app and what I should not.
ololobus commented 5 months ago

I see, thanks for the quick response, although I've seen the FAQ, just didn't scroll till the end %)

Well, Flipper-XFW is unofficial firmware based on Unleashed, which removes regional radio restrictions. It's illegal in the most of the world, unfortunately. Although I understand how annoying it is, I also understand that they as a company may not want to take the risks :( For example, Apple has crazy history of removing apps from the store, which were 100% safe. Nobody fully knows their logic, but I guess Flipper authors want to be extra cautious.

Don't write this to say that it's normal, just when you run the private company you have to balance and you want it to continue existing, while such monopolists like Apple and Google can make you life a hell if they ban you from their platforms.

Anyway, wish you all the best and going to play with flipper authenticator soon :)

akopachov commented 5 months ago

Well, of course it might be so. But let's consider couple of points here:

  1. Why don't they announce it publicly in their TOS - "any links to anything mentioning custom firmware is not allowed". So that everybody knows that this is Flipper Devices official position.
  2. I put a link to the discord server, not to the custom firmware website. Neither I nor anybody alse force to install custom firmware in that discord. And if somebody were running official firmware asking Authenticator-related question there were zero problem answering them.
  3. It still doesn't explain why I should keep the code in my repo formatted the way Flipper Devices wants. To let them review it? I see no problem them running any formatter they want right before review. OSS allows it to them.

Overall, I have nothing against of TOS and following them. What I avoid dealing with is a TOS which are not written, not officially and publicly announced and instead existing in some ephemeral form.

ololobus commented 5 months ago

Yeah, I agree, they should've been more open and clear about the reasons

akopachov commented 4 months ago

Dude, read this first

If this is not allowed - no problem, mention this explicitly and publicly so that everybody knew who initiated that. I don't want it to look like it is me who decided so. Is that so hard to do? Any good explanation on why I should keep formatted my code in my repo the way flipper devices want?

Upd: Also, FYI, a lot of people download xfw, mfw, unleashed because that firmwares are more customizable. So I wouldn't say that illegal features is the only reason for everybody