I totally agree that this is completely bogus - I use ljseek all the friggin' time (with running a rec comm checking and looking up previous posts is a day-to-day job, basically) and never ever have I seen it have a post THAT HAS *NOT* BEEN F-LOCKED *AFTER* IT WAS POSTED.
Meaning that, if this post was not f-locked when ljseek added it to their database, and you f-locked it 15 seconds after the fact, it *would* still be findable. If it were posted as f-locked right off the bat, it would not be found.
Anyways, checking this is easy enough: do a search for any of your f-locked posts you *know* you have not unlocked, or post a locked test-post, wait about 24 hours (ljseek parses lj about every 12 hours, if I recall correctly), the search for it. If you find it, my bad, but I doubt you will - I cuss out ljseek and everyone who posts comm-locked posts often enough when I can't find them in my searches to have a little experience with this.
no subject
Meaning that, if this post was not f-locked when ljseek added it to their database, and you f-locked it 15 seconds after the fact, it *would* still be findable. If it were posted as f-locked right off the bat, it would not be found.
Anyways, checking this is easy enough: do a search for any of your f-locked posts you *know* you have not unlocked, or post a locked test-post, wait about 24 hours (ljseek parses lj about every 12 hours, if I recall correctly), the search for it. If you find it, my bad, but I doubt you will - I cuss out ljseek and everyone who posts comm-locked posts often enough when I can't find them in my searches to have a little experience with this.