The problem wearethene.ws has is that it verifies threads and expects EVERY THREAD NUMBER TO EXIST ONLY ONCE.
And because of the fights in the kitchen almost every thread is marked for manual intervention.
I'm grabbing notables automatically and I don't care about bread #, so notables in notable thread are up to date and fine.
I'm Auto Archive Anon.
I have been archiving threads automatically since July of this year (if I remember correctly).
So I had to get the post data already.
When the outage of wearethene.ws occured, I thought about adding notable detection as well. I was already figuring out in which thread Q posted, so that information is available as well.
It's all JSON parsing and interpreting that data.
Anyway, you can go to the notables thread and get them there.
I'm not getting them the same as wearethene.ws.
I'm always expecting bakers to post notables within the first few posts of a thread. So when that doesn't happen, I won't have notables. Only happened once, and I think that was a note taker and the baker afterwards didn't care.
And what I mean about archiving is:
archiving the bread itself
archiving all videos (wayback machine only)
archiving all high resolution pictures
also now archiving all pictures of all notables
also archiving all Q post attachments, and I think I also archive all replies to Q posts, but I'm not sure about that
archive.is archiving is currently down though, because I'm getting captcha prompts. Will try to fix that next. Notables were more important.