Show HN: Wikipedia as a doomscrollable social media feed
31–40 of 151 posts
Re: Show HN: Wikipedia as a doomscrollable social media feed
#32Re: Show HN: Wikipedia as a doomscrollable social media feed
#33Re: Show HN: Wikipedia as a doomscrollable social media feed
#34Earlier quoted context omitted.
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…
> 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…
Re: Show HN: Wikipedia as a doomscrollable social media feed
#35Re: Show HN: Wikipedia as a doomscrollable social media feed
#36Earlier quoted context omitted.
Why not…. Load it on demand?
That's my point. So confused. Got a ton of users clicking off because of this.
Re: Show HN: Wikipedia as a doomscrollable social media feed
#37Re: Show HN: Wikipedia as a doomscrollable social media feed
#38Earlier quoted context omitted.
> 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…
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)
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.
Re: Show HN: Wikipedia as a doomscrollable social media feed
#39Earlier quoted context omitted.
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.