I've got two, I hope that's okay.
Requested Feature 1: Having a RES sort of thing where you wouldn't have to type out the HTML, but you'd only have to press a button. See:
Why it'd be useful: It would make commenting a lot easier.
~~~
Requested feature 2: So, I heard a couple months ago that having a blacklist that worked as if you had typed all of the tags in the negative into the search bar wouldn't work because it'd put too much strain on the website. So, this gave me an idea: what if you gave the user 3 slots to put in tags that they really want blacklisted so that the page doesn't get tiny if it's blacklisted. Like, I have the female tag blacklisted, and it'd be nice to have the site auto-search "-female" so I'd get to see double the posts on a single page. Again, the user would only get to do this with 3 (or so) tags so there'd be little to no strain on the server.
Why this would be userful: It'd make searching a lot easier and more convenient.
SpaceWhale said:
I've got two, I hope that's okay.Requested Feature 1: Having a RES sort of thing where you wouldn't have to type out the HTML, but you'd only have to press a button. See:
Why it'd be useful: It would make commenting a lot easier.
I have these: http://i1246.photobucket.com/albums/gg609/xch3l/bar.png Though they don't work as I wanted, but they're usable
slyroon said:
So users can see why an artist is on the avoid_posting list
An Enumerated and Exhaustive List of Why Artists are on the Avoid Posting List:
1. They asked to be put there.
Takedown requests don't factor into it.
slyroon said:
Requested feature: Have a link next to artists name on the avoid_posting that leads to there take down requestWhy it would be useful: So users can see why an artist is on the avoid_posting list
I do like this idea, actually, but as Snowy said, really the only reason they're on it is because they asked to be placed on it. At that point the only purpose I could see linking to their takedown request serving is to "prove" that they asked to be put on the list, which seems kind of unnecessary to me. Should we do it anyways though?
Char said:
I do like this idea, actually, but as Snowy said, really the only reason they're on it is because they asked to be placed on it. At that point the only purpose I could see linking to their takedown request serving is to "prove" that they asked to be put on the list, which seems kind of unnecessary to me. Should we do it anyways though?
No, because there isn't guaranteed to be a takedown request for every artist that's implied to avoid_posting. And even then, it's not an exact 1:1 ratio; maybe there's multiple takedowns for one artist, maybe there's none, maybe there is one but it's a different spelling or a different alias of their name. So it would be impractical to "find" the takedown that resulted in the avoid_posting tag.
Please have e621 keep a list of all FFD requests, even those that have already been processed.
Each FFD request could be marked as "approved", "rejected" or "pending".
I realize that this feature is far from essential, but it would be very entertaining to browse the list. It would also help to educate new users about what's a valid FFD reason and what isn't.
Requested feature: A google-esque "Did you mean...?" when somebody types in a tag that isn't associated with any images.
Why this would be useful: It'd help people find images faster if they're typing quickly and misspell a word.
SpaceWhale said:
Requested feature: A google-esque "Did you mean...?" when somebody types in a tag that isn't associated with any images.Why this would be useful: It'd help people find images faster if they're typing quickly and misspell a word.
That would be very useful, but Id imagine very hard to implement.
Rainbow_Slash said:
That would be very useful, but Id imagine very hard to implement.
I'm no programmer, but I'd imagine that if Google was able to implement it with no problems then it can't be too difficult.
SpaceWhale said:
I'm no programmer, but I'd imagine that if Google was able to implement it with no problems then it can't be too difficult.
Nah, e6 is fine
SpaceWhale said:
I'm no programmer, but I'd imagine that if Google was able to implement it with no problems then it can't be too difficult.
Yeah, but Google's put many years of work and watching how people use the search into that system (although that also accounts for why certain words are treated as the same thing, like 4 and four).
SpaceWhale said:
Requested feature: A google-esque "Did you mean...?" when somebody types in a tag that isn't associated with any images.
There's something similar to this on yande.re and sankakuplex (super NSFW), but they use different builds
titaniachkt said:
There's something similar to this on yande.re and sankakuplex (super NSFW), but they use different builds
Well, yande.re seems to be using cookies to return a list of recently searched tags along with their post index. I suppose as long as they keep it to 1000-2000 results then it only adds 20KB-40KB to the page. Then as the user types in something to search for, it's running a series of regexes for potential matches against the recent tags list.
It's not anything too nifty, like BK-Trees or whatever this damn-near mystical shit is, but it could help if a person can only remember part of a tag name. I'm not really sure how many people struggle to spell "scalie", "canine", or whatnot, so I'm not sure how useful this specific technique will be to e621, but I can totally see how it's useful on a more general hentai site where someone might want to search for kono_minikuku_mo_utsukushii_sekai.
I couldn't be arsed to delve into sankaku complex's javascript to determine how they're doing it, but from the delay between typing and suggestions I'd guess they're calling into a server-side script and it's impossible to know what they're doing.
SpaceWhale said:
I'm no programmer, but I'd imagine that if Google was able to implement it with no problems then it can't be too difficult.
1: How do you know that Google was able to implement it with no problems?
2: Why do you assume that "if google can do it, it can't be hard"? Google is a large corporation with tens of thousands of very smart employees. Search is a core area of their business. "Google can do it" doesn't mean that it's easy to do.
Snowy said:
1: How do you know that Google was able to implement it with no problems?
2: Why do you assume that "if google can do it, it can't be hard"? Google is a large corporation with tens of thousands of very smart employees. Search is a core area of their business. "Google can do it" doesn't mean that it's easy to do.
Whiy not? If Google can do a barrel roll I can do too.
-----
Requested feature: Make this thread a subforum
Why it would be useful: Make this thread more organized separating suggestions and comments. Like these 8 last comments, they could be in SpaceWhale's thread
ikdind said:
but it could help if a person can only remember part of a tag name. I'm not really sure how many people struggle to spell "scalie", "canine", or whatnot, so I'm not sure how useful this specific technique will be to e621, but I can totally see how it's useful on a more general hentai site where someone might want to search for kono_minikuku_mo_utsukushii_sekai.
Did you know that..
If you click on tags, then type: part of a tag followed, or preceded by a *, you can get a list of all tags starting with, ending with, or containg that set of characters...
For example:
can*
-canine
-canine_penis
-candy
-candle
-cane
*can
-scan
-can
-toucan
-trashcan
-native_american
*can*
-canine
-canine_penis
-scan
-arcanine
-african_wild_dog
SnowWolf said:
Did you know that..If you click on tags, then type: part of a tag followed, or preceded by a *, you can get a list of all tags starting with, ending with, or containg that set of characters...
This also works in the search bar such as *background for example. Also, the "source:" metatag doesn't need a wildcard (asterisk). source:deviantart returns everything with at least deviantart in the source.
Requested feature: Disallow posts with unicode in the private range (U+e000 to U+f8ff, U+f0000 to U+ffffd, U+100000 to U+10fffd). When someone tries to use them, show an error page.
Why it'd be useful:
ikdind said:
When someone tries to use them, show an error page.
Better yet, show an error *and* a preview of the post, with the offending characters marked in some way. Turning them red might work, but:
- there are colorblind people (who like porn, too!)
- you can use colored text on e621 (Only usable by privileged+)
so if someone posts private Unicode characters formatted as red, the systems fails
then again, that's not very likely
and privileged+ users should know better than to use private Unicode characters, anyway :)
That all seems like a lot of work when we could just say hey please don't use private unicode characters.
Well, Munkelzahn is right when he says in forum #39115:
Munkelzahn said:
You'll never get people to stop using private Unicode characters just by asking.
The fact is, certain irresponsible developers have decided that it's a fun and profitable idea to use private unicode plug-ins to allow users to type what they think are interesting and expressive characters into documents and forms that can then be made public.
Nobody can read these interesting and expressive characters, but why should your average Apple user know, or care? Simply asking them to stop won't help, because they don't have the technical knowledge to discern real unicode from Emoji's (or anyone else's) piles of poo.
And certainly the developers don't care. The user who buys their stuff will then tell their friends to buy and install the unicode package to see these interesting and expressive characters. When these friends do, it's Mission Accomplished. Money in the bank. Abusing an extensible feature for money and profit.
The real people I'm upset at are the developers who make these tools. No doubt these are the same kinds of developers that link into random Windows libraries to call private, unpublished functions, then wonder why their apps have compatibility issues when MS issues a hotfix to a critical security flaw.
It's not like this is an epidemic. If it really gets that bad then it can become a new rule but I don't see it happening.
doorspawn said:
Major (and unlikely) idea.Request:
Tag each character individually, and allow searching per image or per character.Why?
Searching for multiple tags often leads to multiple characters each with only some of the tags. This is especially problematic when blacklisting tags.For example, searching for female -mono_breast can exclude images with 1 normal female and 1 single-breasted one. (Although it seems my example fails as this site has a severe lack of mono-boobed entities).
This could surely be implemented now simply by putting the artist / series name in brackets after the character tag
e.g Amy_rose
becomes
Amy_rose_(sonic_the_hedgehog)
In fact, I've seen some people do this already, so why not simply change the tagging rules for cases where two characters share the same name.
Requested feature: Having gender work like the rating system, so that as well as having to specify explicit, questionable, safe you would have to specify Male, Female Intersex etc, and instead of having go to one or the other by default you would have to click one or the other.
Why it would be useful: Gender would always be tagged correctly by necessity.
therabbidwanker said:
Requested feature: Having gender work like the rating system, so that as well as having to specify explicit, questionable, safe you would have to specify Male, Female Intersex etc, and instead of having go to one or the other by default you would have to click one or the other.Why it would be useful: Gender would always be tagged correctly by necessity.
not all images have characters in them
ippiki_ookami said:
not all images have characters in them
Fair point.
----
Requested Feature: Having the number of remaining posts you can upload in the upload setion of the site.
Why it would be useful: No need to second guess anymore.
Requested Feature: Blacklist straight from the Tag page. Could be a link on the bar with "List New Help" ect
Useful Because:If I find an artist I don't like, for example, I'd just open the tag page from the "?" link and blacklist it right from there instead of digging into my profile settings and pasting the name.
Munkelzahn said:
Better yet, show an error *and* a preview of the post, with the offending characters marked in some way.
Better yet, make the post but flag it so that only the user who posted it can see it, and nobody else.
Because fuck being helpful.
ippiki_ookami said:
not all images have characters in them
well, you'd need them to be check boxes, not one-or-the-other selectors...
You'd need male, female, ambiguous_gender, herm, dickgirl, and cuntboy... adding "other" seems like it would be pretty simple as well. If 'male' adds the 'male' tag, then 'other' can add nothing...
not that I'm necessarily arguing for this, but hey.
slyroon
Test Janitor10 months ago
Requested feature: Have a link next to artists name on the avoid_posting that leads to there take down request
Why it would be useful: So users can see why an artist is on the avoid_posting list