Futureporn September 2023 Sprint

CJ_Clippy commented

2023-08-10 19:19:44 +00:00

Owner

Next.js redesign
Twitter Historian
Uploads

With August comes a much needed redesign of the site's UI. The redesign is focused on converting Futureporn's single vtuber fansite into a multi-vtuber powerhouse.

I've been thinking about what I want the user experience to be. I've spent a long time thinking about this, and every time I come back to xvideos or pornhub methodology, where models can be browsed and their videos viewed.

I'm re-realizing that there are too many lewd VTubers out in the wild. I can't possibly run a futureporn-scout instance on my home internet connection. This doesn't scale for me to capture all the realtime events from all the lewdtubers out there.

Just today I noticed that skyeanette, passionyx, and lil_happa were all streaming at the same time. 3 at once is doable, but what about when it's 30 at once? Impossible for one person. Even if I capture and log all events, managing the vods is a completely different challenge.

I think I need to expand the mission statement. "The Galaxy's Best VTuber Hentai Site" is a lofty goal, but how do we get there? I think we get there by capturing all the VTubers. And how do we get there? By getting as much help as humanly possible.

My thought is this. Gamify the collection of vods. I can't do it on my own, it's impossible. What I can do is create a platform enabling collaborating on capturing them all. "Gotta catch 'em all!"

Futureporn needs a purpose, and that purpose is protecting and preserving hentai livestreams. Visitors are presented with a calendar which shows known streams, and whether or not they have been archived.

On https://futureporn.net/vt/:vtuber, I need the following.

twitter historian data displayed in a nice, compact way
/goals style percentage of collection progress
clicking a missing vod redirects to /upload/:ts and populates relevant fields
clicking a present vod redirects to /vods/:ts
/upload needs more storage platform upload support
#7 feature parity
#35 thumbnails
#36 obtrusive stalled messages

* [x] Next.js redesign * [ ] Twitter Historian * [ ] Uploads With August comes a much needed redesign of the site's UI. The redesign is focused on converting Futureporn's single vtuber fansite into a multi-vtuber powerhouse. I've been thinking about what I want the user experience to be. I've spent a long time thinking about this, and every time I come back to xvideos or pornhub methodology, where models can be browsed and their videos viewed. I'm re-realizing that there are too many lewd VTubers out in the wild. I can't possibly run a futureporn-scout instance on my home internet connection. This doesn't scale for me to capture all the realtime events from all the lewdtubers out there. Just today I noticed that skyeanette, passionyx, and lil_happa were all streaming at the same time. 3 at once is doable, but what about when it's 30 at once? Impossible for one person. Even if I capture and log all events, managing the vods is a completely different challenge. I think I need to expand the mission statement. "The Galaxy's Best VTuber Hentai Site" is a lofty goal, but how do we get there? I think we get there by capturing all the VTubers. And how do we get there? By getting as much help as humanly possible. My thought is this. Gamify the collection of vods. I can't do it on my own, it's impossible. What I can do is create a platform enabling collaborating on capturing them all. "Gotta catch 'em all!" Futureporn needs a purpose, and that purpose is protecting and preserving hentai livestreams. Visitors are presented with a calendar which shows known streams, and whether or not they have been archived. On `https://futureporn.net/vt/:vtuber`, I need the following. * [ ] twitter historian data displayed in a nice, compact way * [ ] /goals style percentage of collection progress * [ ] clicking a missing vod redirects to /upload/:ts and populates relevant fields * [ ] clicking a present vod redirects to /vods/:ts * [ ] /upload needs more storage platform upload support * [ ] #7 feature parity * [ ] #35 thumbnails * [x] #36 obtrusive stalled messages