Dumps with complete page edit history can be downloaded too, as far as I can see, so no need to crawl that.
clb92
joined 2 years ago
valid reasons for not wanting the whole database e.g. storage constraints
If you're training AI models, surely you have a couple TB to spare. It's not like Wikipedia takes up petabytes or anything.
Yeah, but organized into as many threads as there are issues/PRs, so it’s exactly as daunting as the same list as viewed on GitHub/project/issues (because it is exactly the same content).
Surely, dedicated tools for managing/tracking issues give you better tools for triaging, filtering, planning and such, compared to a mail client...
Why would anyone crawl Wikipedia when you can freely download the complete databases in one go, likely served on a CDN...
But sure, crawlers, go ahead and spend a week doing the same thing in a much more expensive, disruptive and error-prone way...
Ah, makes sense.
Awesome and detailed explanation, thanks. I figured they'd be juggling a lot of mails, and I guess it is possible for some people to stay on top of that and keep it all organized with a good mail client, but still... I would get lost so quickly.
Thanks again!
No, I don't think I "should" know this.
You should know that this isn't the place to post random promotional advertising.
You don't have to fully restart caddy. You can tell it to reload the caddyfile.
Oh, it's not actually FOSS, I think, sorry. Disregard this.
~~Total Commander is what I use. It's a dual-pane file manager that has support SFTP, WebDAV, SMB and more with the official plugins it has. It sometimes feels a bit dated, but most other file managers I've tried felt simplistic and dumb compared to it. It has lots of advanced features too.~~
I'm probably gonna sound like a noob now, but how does one even properly handle issue tracking, working like that?
What did they use before? GitLab? A hosted solution like GitHub or Codeberg?
It also depends how humid it is where you live.