OpenNefia VS scraper

The code for all these mods lives here, if you're curious to see what the modding system looks like right now. I think that, even if some of the mods are incomplete in their current state, they implement several of the useful features that I was wanting to port from the start, so having any amount of progress towards completing them isn't a bad thing. They're also implemented as separate mods, so if they get too buggy they can be disabled easily.

Well, it's not Elisp, but:

https://github.com/Ruin0x11/OpenNefia

It's an engine rewrite of an old roguelike I used to play in Lua. I'm trying to experiment with making a game where the engine is similar in flexibility to Emacs.

It has an Emacs frontend, and I designed it with the zealotry of an Emacs user, meaning it has advice, hooks, interactive evaluation and runtime module hotloading. You can run anything the engine can run from a REPL (and cause all the state to become broken easily).

I recently implemented nefias in my engine rewrite of Elona, called OpenNefia. Hopefully the ability to generate lots of new dungeons in addition to the ones in vanilla would make the game more interesting. Here are few I made, as part of a mod:

An engine rewrite of a Japanese roguelike I played a lot. I liked Emacs, so I decided to see what would happen if I tried writing it in the style of what Steve Yegge calls "living systems", where all the code is interactively callable in-game and reusable in mods. There is no scripting layer, the implementation and extension language are one and the same (Lua). I like to think of the engine as a massive programming runtime with a bunch of libraries and functions made for the sole purpose of modding the game. You could whip up a scratch buffer and start tinkering around with the game state or prototyping new mods fairly quickly.

The engine is not general purpose either, it's specific to the quirks of the original game. The number of weird ideas that I could graft onto it keeps increasing with each week. Yet, without feature parity and stability with the original, it's a long way away from having those things.

Another downside is going back and playing the original now isn't as fun, because I keep thinking I'm playing the rewrite and expecting bugs to pop up at ever corner. Working on a project like this for so long affects your perception of the end result in ways you can't easily unsee.

Also gets pretty lonely working on something alone for years you're not sure anyone will care about when it's playable.

[1] https://github.com/Ruin0x11/OpenNefia

Additional info and source code for generating the dataset, summarizing it and rendering the chart are available at https://github.com/get-set-fetch/scraper/tree/main/datasets/javascript-libs-from-top-1mm-sites

Store the scrape progress (to-be-scraped / in-progress / scraped / in-error URLs) in a database shared by all participants and scrape in parallel with as many machines as the db load permits. Got a connection timeout / IP is blocked on one machine ? Update the scrape status for the corresponding URL and let another machine retry it. https://github.com/get-set-fetch/scraper (written in typescript) follows this idea. Using Terraform from a simple config file you can adjust the number of scraper instances to be deployed in cloud at startup and during the scraping process. In benchmarks a PostgreSQL server running on a DigitalOcean vm with 4vCPU, 8GB memory allows for ~2000 URLs to be scraped per second (synthetic data, no external traffic). From my own experience this is almost never the bottleneck. Obeying robots.txt crawl-delay will surely put you under this limit. Disclaimer: I'm the npm package author.

Written in typescript https://github.com/get-set-fetch/scraper stores scraped content directly in a database (sqlite, mysql, postgresql). Each URL represents a Resource. You can implement your own IResourceStorage and define the exact db columns you need.

You can use https://github.com/get-set-fetch/scraper with a custom plugin based on the mozilla/readability as detailed in https://getsetfetch.org/node/custom-plugins.html (extracting news article content). I think it's a close match to your use case.

I'm currently implementing concurrency conditions at project/proxy/domain/session level in https://github.com/get-set-fetch/scraper . On each level you can define the maximum number of requests and the delay between two consecutive requests.

If you're familiar with nodejs give https://github.com/get-set-fetch/scraper a try. Scraped content can be stored in sqlite, mysql or postgresql. It also supports puppeteer, playwright, cheerio or jsdom for the actual content extraction. No scheduler though.

I'm using this exact strategy to scrape content directly from DOM using APIs like document.querySelectorAll. You can use the same code in both headless browser clients like Puppeteer or Playwright and DOM clients like cheerio or jsdom (assuming you have a wrapper over document API). Depending on the way a web page was fetched (opened in a browser tab or fetched via nodejs http/https requests), ExtractHtmlContentPlugin, ExtractUrlsPlugin use different DOM wrappers (native, cheerio, jsdom) to scrape the content.

[1] https://github.com/get-set-fetch/scraper/blob/main/src/plugi...

https://github.com/get-set-fetch/scraper - I've been working (intermittently :) ) on a nodejs or browser extension scraper for the last 3 years, see the other projects under the get-set-fetch umbrella. Putting a lot more effort lately as I really want to do those Alexa top 1 million analysis like top js libraries, certificate authorities and so on. A few weeks back I've posted on Show:HN as you can do basic/intermediate? scraping with it.

Not capable of handling 1 mil+ pages as it still limited to puppeteer or playwright. Working on adding cheerio/jsdom support right now.