[QUOTE=LaurV;386997]No need to look to any status page, just to the sequence in discussion on fdb. All of them were over a top, say 116 digits sometime in their past, and in (my, your, Dubslow's etc) database we don't have sequences at 113 digits. Even if the "tables" are not really actual, te sequence in discussion does not exhibit a top over 116 digits after the deep of 8 digits, so it can't be a merge. If it would merge with something, as you personally said, it will jump immediately from "where you left it" to the last top of that "something" (which is over 116 digits) and than (eventually) back at 113. Except if it (unfortunately) merged with a sequence which is "corrupted" in the DB. But that is not the case. [/quote]OK, I didn't know what the lowest sequence in the DB is currently, since I haven't taken an overall look at things lately, but knowing that is a quicker way. Good to remember. I guess a merge with a broken sequence should be obvious, too, so that's ruled out. Still too bad that that low a dip did not pau off....[quote]Just to be sure, I also have checked it against my db after I posted (which db is not updated since long time, i.e.since I was talking about it in september or so, but everything is over 115 digits) and didn't find anything.[/QUOTE]I remembered that you had said something about getting a current status on everything locally right after I hit submit, but did not go back and edit because I got busy. Sorry, next time I might remember sooner.

This also prompted me to start an update on my local status (and "all open sequences" backup). Scary, when I checked just now I see that I haven't pulled everything since May. Where did the time get to?

Thanks schickel for checking, and thanks Laurv for your explanation and checking.

The hijacking of that sequence continued overnight. With the size of the composites and how quickly it is being advanced, it's not due to Factor Database workers.

Having trouble with the script right now. It is timing out on line 37. I suspect it could have something to do with my updating Cygwin. I will hopefully get to fixing/manually updating soon. My new job is taking most of my energy currently.
Edit just realized I can't access allseq.txt on dubslow's site. edit2: or dubslow's site at all

My router shat itself this morning, and took all my port forwards with it... give me an hour or so.

[QUOTE=Dubslow;387048]My router shat itself this morning, ....[/QUOTE]
Lovely metaphor.

[QUOTE=Batalov;387053]Lovely metaphor.[/QUOTE]

Well that's about as apt a description as I cared to create. According to IRC/Mumble, around 4 am the internet died; when I woke up I tried to trouble shoot, but only got as far as "power cycling the router allows me to connect to it (e.g. view firmware) for ~10-30 seconds before all its lights turn on and stay on (even lights that shouldn't be), at which time my OS says the cable is disconnected".

After running for a few hours with the hardware switch in AP mode, I moved it back to Router mode which spontaneously started working, but with the config utterly gone.

So, I called it like I see it.

In a probaby-unrelated matter (though it very well could be), my ISP did something so that I'm no longer in their DMZ -- I'll fix that tomorrow.

Taking 815736.

Dropping 135612, 279816, 428928, 914788. Taking 783804, 807288.

As I still can't access Dubslow's page I have done a manual update.

Dropping 21930, 32796, 49600, 89448, 95136, 112968, 215748, 408810

Taking 991608.