Very small suggestion: Can you make the entries actual links/anchor tags so that it is possible to copy link, middle-click to open in a new tab, and so on?
This is a very neat idea. I am not sure why the page needs to load 40mb of data and make me wait 5 mins before the first view. I'd probably also add some ranking criteria to surface good quality articles that maximize the "I learnt something new today" factor. Overall kudos to the developer for original thinking.
Presumably the 40mb of data is not from Wikipedia, but the Javascript tracking code bundle needed to turn it into a doomscrollable social media feed. ;) By those standards, I think it’s pretty lightweight! For comparison, the Instagram iOS app is 468.9mb, more than ten times the size…
I ran across a grammar mistake in one of the entries and clicked into the actual wikipedia entry to fix it. That was satisfying. Imagine being able to do that on social media.
Please fix the loading issue and I’ll return! I think you don’t need to pull all the data at initialization, you could lazily grab a couple from each category and just keep doing it as people scroll.
The loading issue is just a hug of death, the site's currently getting multiple visitors per second, and that requires more than a gigabit of bandwidth to handle.
I sort of need to pull all the data at the initialization because I need to map out how every post affects every other - the links between posts are what take up majority of the storage, not the text inside the posts. It's also kind of the only way to preserve privacy.
> Why are you serving so much data personally instead of just reformatting theirs?
Because then you only need to download 40MB of data and do minimal processing. If you were to take the dumps off of Wikimedia, you would need to download 400MB of data and do processing on that data that would take minutes of time.
And also it's kind of rude to hotlink a half a gig of data on someone else's site.
> What am I missing?
40MB per second is 320mbps, so even 3 visitors per second maxes out a gigabit connection.
no but...why are you passing 40mb from your server to my device in a lump like that?
All I'm getting from your serve is a title, a sentence, and an image.
Why not give me say the first 20 and start loading the next 20 when I reach the 10th?
That way you're not getting hit with 40mb for every single click but only a couple of mb per click and a couple more per scroll for users that are actually using the service?
Look at your logs. How many people only ever got the first 40 and clicked off because you're getting ddosed? Every single time that's happened (which is more than a few times based on HN posts), you've not only lost a user but weakened the experience of someone that's chosen to wait by increasing their load time by insisting that they wait for the entire 40MB download.
I am just having trouble understanding why you've decided to make me and your server sit through a 40MB transfer for text and images...
> no but...why are you passing 40mb from your server to my device in a lump like that?
Because you need all of the cross-article link data, which is the majority of the 40mb, to run the algorithm. The algorithm does not run on the server, because I care about both user privacy and internet preservation.
Once the 40MB is downloaded, you can go offline, and the algorithm will still work. If you save the index.html and the 40MB file, you can run the entire thing locally.
> actually using the service
This is a fun website, it is not a "service".
> you've not only lost a user but weakened the experience of someone that's chosen to wait by increasing their load time
I make websites for fun. Losing a user doesn't particularly affect me, I don't plan on monetizing this, I just want people to have fun.
Yes, it is annoying that people have to wait a bit for the page to load, but that is only because the project has hundreds of thousands of more eyes on it than I expected it to within the first few hours. I expected this project to get a few hundred visits within the first few hours, in which case the bandwidth wouldn't have been an issue whatsoever.
> I am just having trouble understanding why you've decided to make me and your server sit through a 40MB transfer for text and images...
Running the algorithm locally, privacy, stability, preservation, ability to look at and play with the code, ability to go offline, easy to maintain and host etc.
Besides, sites like Twitter use up like a quarter of that for the JavaScript alone.
I believe in privacy but generally people are fine with rec algorithms running on a server if it's transparent enough/self hostable. Mastodon/DuckDuckGo/HN/etc all don't need to download a huge blob locally. (If you do want it to run locally, hosting the blob on a CDN or packaging this as an app and letting someone else host it would probably improve the experience a lot)
Mastodon/HN do not have a personalized weighted algorithm. On HN you see what everyone else sees, and on Mastodon the feed is chronological. DuckDuckGo offers some privacy, but still sends your search queries to Bing.
Also, all three of the examples are projects that have years of dev effort and hosting infrastructure behind them - Xikipedia is a project I threw together in less than a day for fun, I don't want to put effort into server-side maintenance and upkeep for such a small project. I just want a static index.html I can throw in /var/www/ and forget.
And re: hosting, my bare metal box is fine. It's just slow right now because it's getting a huge spike of attention. I don't want to pay for a CDN, and I doubt I could host a file getting multiple gigabits per second of traffic for free.
Who made you do anything? It's a fun website. If you don't like it, move along or make one yourself. I could understand if you were paying for something, but this is free.
That's a very silly claim considering I bought the domain the same day I released the project. I'm sure whoever would've been interested in buying the domain could've already swept it up for 10 bucks before me.
Love the concept. Wikitok also exists [1] but the recommendation aspect that you're bringing you the table is a very intriguing original spin on it. I would be fascinated to see what a smart algorithm could discover on my behalf on Wikipedia given enough time.
I think it would be nice if you could do a non simple English version but nevertheless happy with what you've put together, and I've added a shortcut to my phone. Please don't let the negativity stop you from continuing to work on it.
I love the concept. But the long load at startup really kills it. Even clicking off the site and reloading makes me have to go through the download all over again.
The United States Virgin Islands are a group of islands in the Caribbean Sea. They are currently owned and under the authority of the United States Government. They used to be owned by Denmark (and called Danish West Indies). They were sold to the U.S. on January 17, 1917, because of fear that the Germans would capture them and use them as a submarine base in World War I.
Did you write your own summary parser for this? I wrote one in the past and found the wiki markup quirky to deal with. The wiki dumps do provide summaries but they seem to suffer similar issues.
Page crashed after downloading and extracting. On safari iPhone that’s a few years old, latest iOS. I was really interested in trying / why I waited
Ed: tried again it crashed at 66% loading (after 100% loading)
An issue I have with these apps that claim to be for doomscrolling is that you don't open apps like Instagram or Facebook to doomscroll, you open them to check messages or stories. The doomscrolling is an afterthought. These things assume you can realize you're doomscrolling and not only break out of it, but choose to hypnotize yourself in their app.
This could be a product. I'd pay for an app that fwd'd messages from other apps and gave me a wikipedia feed to scroll on the elevator / other places where the phone is a social respite
How does it actually work? Can you add an "about" page that goes into the algo? Or can you add more info on the readme on github? I'd love to learn more.
Impressive!
We're a university lab and published recommendation algorithms. Never knew that doomscrolling could be this addictive this fast, thnx!
Please consider taking an hour and push this to a Github with quick readme. Scientists and developers would get it. We have been building a torrent-based alternative to Youtube for a few years. Not many knowledge out there around operational frontpage algorithm.
I am so lucky to be basically immune to short form video garbage like TikTok, but I am not immune to Wikipedia's allure.
I easily have over 100 tabs of wikipedia open at any one time, reading about the most random stuff ever. I'm the guy who will unironically look up the food I'm eating on wikipedia while I'm eating it.
No need to try to make it "doomscrollable" when it's already got me by the balls.
This would actually be really fun if built around social feature like curators who could quote-repost the posts, popular/trending sorting and a threaded comment system.
So they took the worst aspect of Wikipedia (Wikipedia), and the worst aspect of "social" media (doom scrolling), and combined them? Brilliant concept. When can we expect the IPO?
Very small suggestion: Can you make the entries actual links/anchor tags so that it is possible to copy link, middle-click to open in a new tab, and so on?
This is a very neat idea. I am not sure why the page needs to load 40mb of data and make me wait 5 mins before the first view. I'd probably also add some ranking criteria to surface good quality articles that maximize the "I learnt something new today" factor. Overall kudos to the developer for original thinking.
Presumably the 40mb of data is not from Wikipedia, but the Javascript tracking code bundle needed to turn it into a doomscrollable social media feed. ;) By those standards, I think it’s pretty lightweight! For comparison, the Instagram iOS app is 468.9mb, more than ten times the size…
40mb is way too much for a JS bundle... Even with a framework you could do this with 5mb or less.
Now imagine how big the builds are for Instagram's server side doomscrollable feed algorithm, given their inverse incentives to this project.
Yeah. Should be able to load in the background once you start scrolling
probably vibe coded
I ran across a grammar mistake in one of the entries and clicked into the actual wikipedia entry to fix it. That was satisfying. Imagine being able to do that on social media.
that's really cool!!
Please fix the loading issue and I’ll return! I think you don’t need to pull all the data at initialization, you could lazily grab a couple from each category and just keep doing it as people scroll.
The loading issue is just a hug of death, the site's currently getting multiple visitors per second, and that requires more than a gigabit of bandwidth to handle.
I sort of need to pull all the data at the initialization because I need to map out how every post affects every other - the links between posts are what take up majority of the storage, not the text inside the posts. It's also kind of the only way to preserve privacy.
I think I'm missing something, but does every user get the same 40MB? If so, can you just dump the file on a CDN?
I feel very strongly that you should be able to serve hundreds or thousands of requests at gbps speeds.
Why are you serving so much data personally instead of just reformatting theirs?
Even if you're serving it locally...I mean a regular 100mbit line should easily support tens or hundreds of text users...
What am I missing?
> Why are you serving so much data personally instead of just reformatting theirs?
Because then you only need to download 40MB of data and do minimal processing. If you were to take the dumps off of Wikimedia, you would need to download 400MB of data and do processing on that data that would take minutes of time.
And also it's kind of rude to hotlink a half a gig of data on someone else's site.
> What am I missing?
40MB per second is 320mbps, so even 3 visitors per second maxes out a gigabit connection.
no but...why are you passing 40mb from your server to my device in a lump like that?
All I'm getting from your serve is a title, a sentence, and an image.
Why not give me say the first 20 and start loading the next 20 when I reach the 10th?
That way you're not getting hit with 40mb for every single click but only a couple of mb per click and a couple more per scroll for users that are actually using the service?
Look at your logs. How many people only ever got the first 40 and clicked off because you're getting ddosed? Every single time that's happened (which is more than a few times based on HN posts), you've not only lost a user but weakened the experience of someone that's chosen to wait by increasing their load time by insisting that they wait for the entire 40MB download.
I am just having trouble understanding why you've decided to make me and your server sit through a 40MB transfer for text and images...
> no but...why are you passing 40mb from your server to my device in a lump like that?
Because you need all of the cross-article link data, which is the majority of the 40mb, to run the algorithm. The algorithm does not run on the server, because I care about both user privacy and internet preservation.
Once the 40MB is downloaded, you can go offline, and the algorithm will still work. If you save the index.html and the 40MB file, you can run the entire thing locally.
> actually using the service
This is a fun website, it is not a "service".
> you've not only lost a user but weakened the experience of someone that's chosen to wait by increasing their load time
I make websites for fun. Losing a user doesn't particularly affect me, I don't plan on monetizing this, I just want people to have fun.
Yes, it is annoying that people have to wait a bit for the page to load, but that is only because the project has hundreds of thousands of more eyes on it than I expected it to within the first few hours. I expected this project to get a few hundred visits within the first few hours, in which case the bandwidth wouldn't have been an issue whatsoever.
> I am just having trouble understanding why you've decided to make me and your server sit through a 40MB transfer for text and images...
Running the algorithm locally, privacy, stability, preservation, ability to look at and play with the code, ability to go offline, easy to maintain and host etc.
Besides, sites like Twitter use up like a quarter of that for the JavaScript alone.
I believe in privacy but generally people are fine with rec algorithms running on a server if it's transparent enough/self hostable. Mastodon/DuckDuckGo/HN/etc all don't need to download a huge blob locally. (If you do want it to run locally, hosting the blob on a CDN or packaging this as an app and letting someone else host it would probably improve the experience a lot)
Mastodon/HN do not have a personalized weighted algorithm. On HN you see what everyone else sees, and on Mastodon the feed is chronological. DuckDuckGo offers some privacy, but still sends your search queries to Bing.
Also, all three of the examples are projects that have years of dev effort and hosting infrastructure behind them - Xikipedia is a project I threw together in less than a day for fun, I don't want to put effort into server-side maintenance and upkeep for such a small project. I just want a static index.html I can throw in /var/www/ and forget.
And re: hosting, my bare metal box is fine. It's just slow right now because it's getting a huge spike of attention. I don't want to pay for a CDN, and I doubt I could host a file getting multiple gigabits per second of traffic for free.
I really like how you have done things. Didn’t mind the waiting time.
Thank you for making my day a little brighter.
Who made you do anything? It's a fun website. If you don't like it, move along or make one yourself. I could understand if you were paying for something, but this is free.
Why not…. Load it on demand?
That's my point. So confused. Got a ton of users clicking off because of this.
The point you're missing is that this website is actually a submarine ad for the domain, xikipedia.org, which the owner is probably trying to sell.
That's a very silly claim considering I bought the domain the same day I released the project. I'm sure whoever would've been interested in buying the domain could've already swept it up for 10 bucks before me.
Is it down ? I can't access it right now
> you will likely see NSFW content. Please only continue if you're an adult.
Should be: Please only continue if you're not at work.
Not everyone works for Valley Virgins
Love the concept. Wikitok also exists [1] but the recommendation aspect that you're bringing you the table is a very intriguing original spin on it. I would be fascinated to see what a smart algorithm could discover on my behalf on Wikipedia given enough time.
I think it would be nice if you could do a non simple English version but nevertheless happy with what you've put together, and I've added a shortcut to my phone. Please don't let the negativity stop you from continuing to work on it.
1. https://www.wikitok.io/
First thing I see: https://en.wikipedia.org/wiki/Esophageal_cancer
Thank you.
I love the concept. But the long load at startup really kills it. Even clicking off the site and reloading makes me have to go through the download all over again.
TIL:
The United States Virgin Islands are a group of islands in the Caribbean Sea. They are currently owned and under the authority of the United States Government. They used to be owned by Denmark (and called Danish West Indies). They were sold to the U.S. on January 17, 1917, because of fear that the Germans would capture them and use them as a submarine base in World War I.
https://simple.wikipedia.org/wiki/United_States_Virgin_Islan...
Took several minutes to load for me, and when my download got to 100%, the browser (safari on ios) refreshed the page and started at 0% again.
Great idea, i find this is better than just doom scrolling X or Instagram
Did you write your own summary parser for this? I wrote one in the past and found the wiki markup quirky to deal with. The wiki dumps do provide summaries but they seem to suffer similar issues.
You know, I enjoyed this, it's nice to get some random, interesting stuff to browse on occasion.
It's ironic that doomscrollable social media feeds are built for low attention spans, because this website is the opposite. Gave up after 20 seconds.
Page crashed after downloading and extracting. On safari iPhone that’s a few years old, latest iOS. I was really interested in trying / why I waited Ed: tried again it crashed at 66% loading (after 100% loading)
I was genuinely excited to try this and it sounded in theory like a lot of fun! Unfortunately yeah too slow to load.
I've been meaning to do something like this for the books I want to read, and things I want to learn.
This is really cool. And in only 500 lines of code is really impressive. I would have thought this was much more.
Built something similar for research papers: https://www.producthunt.com/products/soch
I wonder if this would be a "better" way to build this thing: https://www.infoq.com/news/2026/01/duckdb-iceberg-browser-s3...
DuckDB loaded in the browser via WebAssembly and Parquet files in S3.
Man, this is the greatest thing I have seen on the internet.
An issue I have with these apps that claim to be for doomscrolling is that you don't open apps like Instagram or Facebook to doomscroll, you open them to check messages or stories. The doomscrolling is an afterthought. These things assume you can realize you're doomscrolling and not only break out of it, but choose to hypnotize yourself in their app.
This could be a product. I'd pay for an app that fwd'd messages from other apps and gave me a wikipedia feed to scroll on the elevator / other places where the phone is a social respite
This is unfortunately loading very, very slowly for me.
How does it actually work? Can you add an "about" page that goes into the algo? Or can you add more info on the readme on github? I'd love to learn more.
I might add a proper explanation at some point, but for now you can view-source the page and read the code, there really isn't that much of it.
Impressive! We're a university lab and published recommendation algorithms. Never knew that doomscrolling could be this addictive this fast, thnx!
Please consider taking an hour and push this to a Github with quick readme. Scientists and developers would get it. We have been building a torrent-based alternative to Youtube for a few years. Not many knowledge out there around operational frontpage algorithm.
Edit: https://github.com/rebane2001/xikipedia
why does everyone keep making this exact same thing again and again
Nice loading indicator! People just don't know how to make those anymore. I think you mistitled your submission, though?
See also: https://www.wikitok.io/
And a plug for my own (fiendishly difficult) Wikipedia-based game:
https://studiowgx.willgrant.org/wikipedia-golf/
Reminds one of Sesame Street - let’s put educational content in this new hyponotic medium!
You can do this manually, obviously. The key is the starting point. The design of thermonuclear weapons is always a good place to begin.
How cool is that! Feature request: Let the user select another language than English.
I am so lucky to be basically immune to short form video garbage like TikTok, but I am not immune to Wikipedia's allure.
I easily have over 100 tabs of wikipedia open at any one time, reading about the most random stuff ever. I'm the guy who will unironically look up the food I'm eating on wikipedia while I'm eating it.
No need to try to make it "doomscrollable" when it's already got me by the balls.
This would actually be really fun if built around social feature like curators who could quote-repost the posts, popular/trending sorting and a threaded comment system.
Can you not?
> Xikipedia is loading... (3% of 40MB loaded)
I gave up after about a minute.
If you load it in Chrome, it loads MUCH faster
Please only continue if you are an adult? You realize Wikipedia has no age restrictions right...
It took forever to load
all images overflow for me
surprisingly... boring?
So they took the worst aspect of Wikipedia (Wikipedia), and the worst aspect of "social" media (doom scrolling), and combined them? Brilliant concept. When can we expect the IPO?
Cool story bro
WP is already shit, why should anyone doomscroll it?
I like the concept, but I'm not going to be reading Simple English Wikipedia.
Man wikipedia is full of trash
human history*