This app is probably in violation of store rules because of it’s name:
https://uappexplorer.com/snap/ubuntu/mati865-thefuck
There are young programmers now, not to mention it potentially breaks Store rules.
The store Terms of Service are linked at the bottom of every page on the developer dashboard. In addition the privacy policy is linked from the ToS page.
Do you have a specific rule which is not being adhered to?
1 Like
Weird… apparently, there isn’t a rule yet on using 4-letter words in application names. However, it seems obvious (to me) that having such names are not a good idea due to the potential younger users (Raspberry Pi programs?) and that it could damage some of the Snap Store’s reputation.
We the users do have the power already to remove it:
f. Canonical may remove your App from the Client Software or Developer Site at any time and for any reason.
I believe that for things like this, we should probably have a vote (for now). +1
(edited by moderation)
–
(obviously this is a joke post)
It isn’t a whim. I might not want my young son to use the Snap Store if there are apps like this. A rename would also work. Don’t forget about all those really young kids learning about computers through Raspberry Pi.
I just want to add that this is indeed a valid piece of software. Why someone would choose to name it that is a different question, but I wouldn’t blame the snap dev.
1 Like
I would not blame the dev either, the name is the only problem here. Just rename it (for him, or tell him to) and if he doesn’t then pull it down.
the problem is if there is no breach of terms then cutting apps arbitrarily, even if agreed upon by some voting system, seems random to the person whose app is cut. If there is a clear breach or terms then it is easy to remove them; without that breach it becomes he said, she said.
1 Like
Well, then we should have a vote to add a rule saying no expletives in app names or content, and if the app itself contains expletives it must warn that on the description. All other app stores that I know of have this rule, and it seems pretty obvious.
Besides, advertising your store (e.g. advertising the Snap Store) while ignoring that there are expletive-named apps in their catalog could make the Snap Store look bad. I mean, if I am a distribution maintainer for, say, PIXEL Desktop for Raspberry Pi, what part of me is going to say, “I am going to include the Snap Store which contains apps like this even though my distribution is used about 1/3 by kids.” It won’t fly.
I vote +1 on not allowing expletives on app names or their textual information. This is a public space, and it can easily show up in people’s screens even if they are not interested on that particular application. The fact it’s the real application name is not a great argument… people are free to name their own application whatever they want.
Update: I take that back. See follow up points below.
Agreed @niemeyer. He can name his app whatever, but it just can’t have that name or description if it wants to be on the Snap Store listings. +1
Note we don’t need to remove it… We just need to rename it, and we can do that while getting in touch with the author so we pick a new name together.
Exactly. I might find the application really useful, but I would never use it under that name.
Hmm… this is surely not a new problem. What’s the situation on every other distribution repository today? What is the policy on Debian, Fedora, Ubuntu, OpenSUSE? We can learn from their wisdom (or mistakes?) here.
I don’t know, but I will look. What I do know is that I have never seen any apps in my life through the software repositories with expletives in the name.
Fedora Forums:
“6). Don’t use profane language or post images containing nudity, violence, or other offensive content.
Our members can be as young as thirteen and people of all ages can view your posts. Therefore, all content here has to be considered family friendly. A staff member will edit or delete threads and posts with potentially offensive content and issue a warning to stop the practice.”
openSUSE Forums (TOS):
“Offensive and/or vulgar language is not appropriate for openSUSE sponsored forums.”
“You agree not to post or transmit through this web site any material or content that violates or infringes in any way the rights of others or solicits, encourages or promotes the use of illegal substances or activities, which is unlawful, threatening, abusive, harassing, defamatory, libelous, derogatory, invasive of privacy or publicity rights, vulgar, obscene, bigoted or hateful, profane, scandalous, pornographic, indecent or other-wise objectionable, gives rise to civil or criminal liability or otherwise violates any local, state or federal law.”
Debian Forum Rules:
"The following might get your post EDITED:
- Profanities
- Links to inappropriate websites
The following might get your post/ thread LOCKED
- Flaming/ personal attacks
- Obvious trolling
- Thread has wandered way off topic
- Cross posting
The following might get your post REMOVED
- Advertising/ Spamming
- Obviously racist/ sexist/ hateful content
- Obviously political/ religious content
- Obvious pornographic content"
While I appreciate the arguments against having expletives, this is a tricky area. Do we cover only certain words, certain languages? Is it okay to obfuscate?
This should be implemented as a store policy decision, and acted upon appropriately.
In answer to @niemeyer
Ubuntu 16.04
alan@hal:~$ apt-cache search fuck
beef - flexible Brainfuck interpreter
irssi-scripts - collection of scripts for irssi
libacme-brainfck-perl - Embed Brainf*ck in your perl code
libghc-brainfuck-dev - Brainfuck interpreter library
libghc-brainfuck-doc - Brainfuck interpreter library; documentation
libghc-brainfuck-prof - Brainfuck interpreter library; profiling libraries
libtest-tabledriven-perl - write tests, not scripts that run them
bf - a fast Brainfuck interpreter
gir1.2-cattle-1.0 - Brainfuck language toolkit (introspection files)
hsbrainfuck - interpreter for the brainfuck programming language
libcattle-1.0-0 - Brainfuck language toolkit
libcattle-1.0-dev - Brainfuck language toolkit (development files)
libcattle-1.0-doc - Brainfuck language toolkit (API reference)
thefuck - spelling corrector of console commands
Debian 9.1
alan@debian-stretch-amd64:~$ apt-cache search fuck
beef - flexible Brainfuck interpreter
gir1.2-cattle-1.0 - Brainfuck language toolkit (introspection files)
libcattle-1.0-0 - Brainfuck language toolkit
libcattle-1.0-dev - Brainfuck language toolkit (development files)
libcattle-1.0-doc - Brainfuck language toolkit (API reference)
hsbrainfuck - interpreter for the brainfuck programming language
libghc-brainfuck-dev - Brainfuck interpreter library
libghc-brainfuck-doc - Brainfuck interpreter library; documentation
libghc-brainfuck-prof - Brainfuck interpreter library; profiling libraries
irssi-scripts - collection of scripts for irssi
libacme-brainfck-perl - Embed Brainf*ck in your perl code
libtest-tabledriven-perl - write tests, not scripts that run them
thefuck - spelling corrector of console commands
Fedora 26
[alan@localhost ~]$ dnf search fuck
Fedora 26 - x86_64 - Updates 5.0 MB/s | 13 MB 00:02
Fedora 26 - x86_64 5.4 MB/s | 53 MB 00:09
Last metadata expiration check: 0:00:04 ago on Tue 12 Sep 2017 15:39:48 BST.
========================================= Name & Summary Matched: fuck =========================================
brainfuck.x86_64 : Brainfuck interpreter
ghc-brainfuck.x86_64 : Haskell brainfuck library
ghc-brainfuck-devel.x86_64 : Haskell brainfuck library development files
============================================== Name Matched: fuck ==============================================
thefuck.noarch : App that corrects your previous console command
python-fuckit.noarch : The Python Error Steamroller
python3-fuckit.noarch : The Python Error Steamroller
Raspbian 8.0
pi@pizerow1:~ $ apt-cache search fuck
beef - flexible Brainfuck interpreter
gir1.2-cattle-1.0 - Brainfuck language toolkit (introspection files)
hsbrainfuck - interpreter for the brainfuck programming language
irssi-scripts - collection of scripts for irssi
libacme-brainfck-perl - Embed Brainf*ck in your perl code
libcattle-1.0-0 - Brainfuck language toolkit
libcattle-1.0-dev - Brainfuck language toolkit (development files)
libcattle-1.0-doc - Brainfuck language toolkit (API reference)
libghc-brainfuck-dev - Brainfuck interpreter library
libghc-brainfuck-doc - Brainfuck interpreter library; documentation
libghc-brainfuck-prof - Brainfuck interpreter library; profiling libraries
libtest-tabledriven-perl - write tests, not scripts that run them
Google Play store
https://play.google.com/store/apps/details?id=com.toolboxx.brainfuck_interpreter&hl=en
Apple iOS store
I don’t believe quoting forum guidelines from other distros is useful. We’re talking about what’s in the archive or store, not the language used on the forums. Although there may well be guidelines for this forum, which cover that issue, the topic at hand is applications in the store.
3 Likes
Well, that is the first time I have ever seen that in a software repository.
Fedora puts things quite simply: “Everything must be family friendly.” Easy.
Also, why should the forums be any different than the Store?
Obfuscation would probably not be a great idea, probably because it is too vague on what “properly obfuscated” means. F*** is obfuscated, but only one letter missing (like sometimes seen) should not be counted. Even simpler, just don’t allow any apps like that.
Store policies differ? I will look.
I am not suggesting the policy should or shouldn’t be different. Merely pointing out that you’re quoting forum policies, not store/archive policies, which clearly do differ, or I wouldn’t have found the results I did.
On Google today:
Now, what if children these ages were reading through Snap Store listings? Obviously they aren’t here, but roll with me. What would you as a parent judge?
[I was writing, and opened a new tab, and that was the link under the Google logo]