FAP will be closing on September 1st. You can read about this here.
°ekigyuu
Made FAP
Member since April 24th, 1987
- 8,586 pageviews
- 81 works (61 drafts)
- 47 blog entries
- 788 comments given
- 270 comments recieved
- 63 favourites
- Watches 156 users
- Watched by 683 users
What do you want from FAP2?Posted 1 year ago
From the official FAP blog...
Current Bug list * * * Large images scroll off the page (this is actually a feature to prevent the layout from breaking. A more beautiful solution is planned for FAP2) New Features in FAP2 * Submit stories, flash movies, profile pictures! * Advanced browse features (date, time, tags!) * Improved tag filters! * Privacy upgraded so you can block abusive users from commenting, tagging, annoying! * Edit/Delete your own comments! * RSS feeds for your message centre, comments, userpages, EVERYTHING. * A new layout. * And, wow...so much more. I can't even remember all the new features... |
Previous blog posts |
12 comments
Comment from *carlos, 1 year ago (#23409)
I have another request.
I don't know if you have done this for security reasons, but I notice I have to re-login when I change browsers (DA does this too). Can this be changed securely to a cross-browser rather than session cookie?
Thanks!
Comment from °ekigyuu, 1 year ago (#24891)
Comment from *carlos, 1 year ago (#24962)
Comment from *carlos, 1 year ago (#18383)
We could also use a text box for comments when we flag a pic. I'm sure some aren't that clear, like "mature art not properly tagged as mature" or "quality control needed" as specified under "What every user needs to know.".
Cheers!
Comment from °ekigyuu, 1 year ago (#18412)
Comment from ♥locoindigo, 1 year ago (#9166)
Loads of people are uploading boobies and cock without a mature tag, presumably by accident. Could you make it more difficult to do this? Default it to "on" somehow? The consequences of getting the task wrong would then be less severe for the site ^^
Also, the site rules require a mature tag on anything nekkid, even perfectly tasteful nekkid without bits visible. Current FAP practice seems to be nude ⊈ mature, so perhaps the rules need to be updated.
Total aside: I always thought that nsfw would be a better choice - in my book, it covers more than mature, presents a purely sfw experience for casual browsers, and it's way less ambiguous, so it's easier to get right in the first place ^^
Comment from ×skech, 1 year ago (#7375)
Comment from °ekigyuu, 1 year ago (#7406)
Comment from ×skech, 1 year ago (#7409)
Comment from °ekigyuu, 1 year ago (#7413)
Just a little longer~
Comment from ×skech, 1 year ago (#7425)
Comment from ♥locoindigo, 1 year ago (#6827)
Comment from °ekigyuu, 1 year ago (#7412)
• Say a user edits their work with new tags, or someone adds new tags to a work. The messaging system isn't retroactive, so people that watch those newly added tags wouldn't see freshly tagged works.
• Each tag would increase the load time for submitting a new work as expressed by
time in milliseconds = 12(number of tags in FAP + number of users). With the current size of FAP's database and an average 24 tags in the submitted work, it would take an additional 18 seconds to process the work.I've been dreaming up different ways to create this feature--18 seconds is an unacceptable lock on the table--and if FAP continues growing as fast as it has been, it would only get worse.
Until I can design an efficient method for this feature, I'll allow users to save searches as AutoPiles.
Comment from ♥locoindigo, 1 year ago (#7551)
Would maintaining a user-has-seen-work table (pk(user, work)) and outer joining the stored search relation with that help? If it's a fast enough query, ordinary user watches could be reimplemented like that too: after all, they're just stored searches that return works (and blog posts) ^^
Sticking a cutoff time limit in each stored search (2 months ago, say) and pruning the user-has-seen-work table to match could be pragmatic and prevent it growing too much.
"seen" could mean "has crossed off", and "work" could mean "object: work or comment or blog post". Depends on how you're organising it.
Comment from °ekigyuu, 1 year ago (#7616)
Unique pageviews for works and users are already calculated in a table, so it would be easy enough to implement...
...but, creating a table listing all the "seen/has crossed off" works for every user instead of a messages-table would be
(every user ever) x (every work ever) = (FA's message system). I'll stick with the current message system...See. That's the challenge now: giving message-centre functionality to AutoPiles without creating too much overhead...that's tough.
We should chat sometime, brainstorm real time.
Comment from ♥locoindigo, 1 year ago (#7751)
I don't understand what you're saying here. You'd only store records for crossings-off, so what you say only makes sense (for *storage space*) if every user crosses off every work. Which they don't; only the ones that appear in their inbox. For *time complexity*, it's driven by the crossing-off event, and that's of the order of a btree insert, ln(n). It'll be a largeish table, but you could also batch-expire old records when they're not needed any more.
It's the LEFT OUTER JOIN followed by a restriction on a COUNT() of these records that makes message-system-like behaviour possible. Now that could be slow, and you'd have to analyse the query fairly carefully probably. In my head, this is a join across about 6 tables and counting, maybe more if you do sense in tag matches, so forgive me if I'm vague. It makes my head hurt.
{{{This thread has come adrift from its context somehow (it should be public, in your second-to-last blog post's thread!), and I can't remember what I said originally.}}}
I'm awake UK times (UTC+0000 right now: it's the cold rainy season). Can't remember if gmail has a chat, but I'm user locoindigo there.
Comment from °ekigyuu, 1 year ago (#7912)
Eh, but I think that might still be slower...I'll play around with it.
I'll add you to my gmail, I'm ekigyuu there. ttyl!
Comment from *blade, 1 year ago (#6462)
Comment from *duo, 1 year ago (#5125)
Comment from °ekigyuu, 1 year ago (#6627)
Comment from ×skech, 1 year ago (#3961)
Comment from °ekigyuu, 1 year ago (#4223)
Comment from °ekigyuu, 1 year ago (#4656)
It's all part of my master plan to create the best furry art site ever and win the internet...so every suggestion, bug report and idea helps!
Comment from ×skech, 1 year ago (#4325)
thanks for giving us a place that is actually worth posting to
Comment from °ekigyuu, 1 year ago (#4660)
It's all part of my master plan to create the best furry art site ever and win the internet...so every suggestion, bug report and idea helps!
Comment from ×skech, 1 year ago (#4666)
Comment from °ekigyuu, 1 year ago (#4951)
I really liked how they let you selectively watch works, scraps, blogs...and put 8 users on your front page.
So! I'm working on something like that for FAP2! Not sure how I would make them...unwatched after a certain period of time...
I'll play around with it and see what I can code up with.
Comment from ×skech, 1 year ago (#5004)
Comment from °ekigyuu, 1 year ago (#5014)
Comment from *hobbes, 1 year ago (#3300)
Comment from *hobbes, 1 year ago (#3301)
Comment from °ekigyuu, 1 year ago (#3312)
Comment from *hobbes, 1 year ago (#3318)
Comment from ♥locoindigo, 1 year ago (#2717)
GET shouldn't really be used for side-effects like that; so sayeth the HTTP RFCs. What about an HTML checkbox+submit formlet for older browsers and Luddites like me, and some JS that removes the formlet from the DOM tree and replaces it with with an async PUT or DELETE call on the "joeuser's favorite thing, ID 1234" resource? Should be really fast. RESTful too.
Comment from °ekigyuu, 1 year ago (#2732)
Comment from °ekigyuu, 1 year ago (#2728)
State change URLs (+watch, +favourite, etc...) are the same for either state to prevent state-XSS attacks. Every GET and POST request also requires a random checksum that changes hourly and upon successful requests to prevent prefetching tools like Google Accelerator from accidentally triggering a GET request...
...I should be using something server-side, like
SecFilterSelective "HTTP_X_MOZ" "prefetch" "deny,status:412", now that I think about it...dur...ANYWAY. I'll probably create a more eloquent and beautiful solution for FAP2...my notebook says I brainstormed some ridiculous REST/SOAP/HTTP Binding multi-environment solution....
Comment from *donamer, 1 year ago (#2714)
Not many people have a signup date on FA before me, hehehe.
Comment from °ekigyuu, 1 year ago (#2733)
Comment from *donamer, 1 year ago (#2979)
Comment from °ekigyuu, 1 year ago (#2999)
Not like I'm giving special prizes to the first 792 people that joined.
Comment from ×skech, 1 year ago (#2478)
Comment from °ekigyuu, 1 year ago (#2509)
Comment from ×skech, 1 year ago (#2514)