Re^5: Who gave (and continues to give) Tye his authority for his autocratic domination of PerlMonks?

[hippo]

Hmmmm. First guess would be that Hanlon's Razor applies here.

You've been very active on this site for a long time; perhaps you have just hit an unexpected limit (total time on, total nodes (written or read), something like that?) which the underlying code treats as a less-than-graceful failure. I've seen systems which run perfectly for years and then suddenly all hell breaks loose because a DB field was originally set up as INTEGER instead of BIGINT years ago and finally some user has clocked it.

Have a nice cup of tea, count to 10 and then report it as a bug. We'll see what happens after that.

[Buk]

Ah! You mean I hit that 140053 limit for 18-bit intgers?

Or could it be that 19706 write-ups is a fundemental constant of the universe; like absolute-0 or some such?

Or maybe I'm just paranoid; and making this whole issue up.

Or ...

[Anonymous Monk]

see Re^5: Who gave (and continues to give) Tye his authority for his autocratic domination of PerlMonks? (300 meditations archive size limit), why is 300 nodes the limit? Cause somebody either on purpose or on accident set the limit

OTOH, did you check the headers, especially cookie expiration date? Could be a timezone/daylightsavingstime type glitch where the cookie doesn't get transmitted because it expired -- so you login successfully, and then no cookies are sent

If you really are the-buk -- can you rant with more common vocabulary? :)

otoh remember when your browser was messing/corrupting your posts with stray tags?

Maybe your machine/dsl-firewall got malwared and its eating the cookies?

[Buk]

Maybe your machine/dsl-firewall got malwared and its eating the cookies?

But only those for userid BrowserUk, but not this one. Right.

Oh, and suddenly stopped this morning.