71–80 of 168 posts
The worst thing about data driven UX - especially with porn - is that it's often a self fulfilling prophecy. Trends that are likely side-effects are considered to be primary factors driving engagement. With porn, it's usually a fetish that is only moderately popular, but broadly unoffensive. Because the average person who isn't specifically interested in the fetish isn't turned off by it either, that fetish gets more…
Why is infinite scrolling not more popular with these sites?
Why is infinite scrolling not more popular with these sites?
How is the pornhub interface different from youtube‘s?
The byline says July 2022, but the errata says “This article was updated with corrections on August 13, 2019”… hmmm Also possibly NSFW (illustrations of the porn sites).
>This story is part of our Weekend Reads series, where we highlight a story we love from the archives. It was originally published in the fifth issue of Eye on Design magazine and again online on August 8, 2019.
Earlier quoted context omitted.
Probably, but you still want to maximize the amount of time users are on the site, or the amount of pages they visit. Orgasms are just an additional complication, I'd imagine.
TikTok, Netflix, Instagram and other sites specifically designed to be sticky (no pun intended) also have this problem although it isn't orgasms. It is that people need to sleep.
I have the same issue with this as other commenters here: The article says that porn sites are designed to maximize engagement. As opposed to what, other video sites?
Interesting how, in attempt to make the article on this topic more SFW, they decided to replace thumbs of actual porn with hand-painted representations..
Earlier quoted context omitted.
IMO the only booru like site that has a better tagging/searching system than esix is derpibooru. It is fast enough to be almost scary. Even with highly complex filters.
I was curious because I am a back-end tech nerd, and apparently "derpibooru" (I had no idea what to expect) is running on Elixir (I assume Phoenix) specifically this: https://github.com/philomena-dev/philomena Edit: PLEASE BE AWARE OF THE LICENSE, it is AGPL licensed, which means if you copy any of the code into your back-end, your whole back-end must be open sourced, as a back-end nerd I stay away from anything AGPL…
That’s a feature, not a bug. If you don’t want that, don’t use it.