What's good about the Blogger if you dont blog , ? yes.
(re-)starting with a lot of diodes 1N4148 + 2N3906 , 2N3904
trying 2-def a microbe-hour csc flip-flop ... it's below the lower half of the kHz range |
to induce re triggering - takes deviating from std. about 170 Hz operation (amazingly valid for full possible supply range ???) |
teh prev. "defined" crash-ware (oldies)
~ about 30kHz op.-s |
. . . . . . . . . i finally get this memory cell working . . . . . . . . . 20kHz write (with ultra cool power draw) . . . WHAT WAS UPLOADED WAS 2048x1512px133KB(136733bytes) WHAT YOU ARE LOOKING AT IS 1600x1181px263KB(268929bytes) ??? -- SORRY I GOT IT WRONG AGAIN SO GOOGLE HAD TO "FIX" IT - g.d. perverts - they just can't leave anything untouched . . . . . . ok, (it's just) yet another totally unnecessary "optimization" by Google ________ come on it's just a few lines to add to your server code (run 1-ce(onece) per img. upload) to tell whether you managed to increase 1-st - the i-net bit traffic on each(every) future page request 2-nd - thus everyone elses' wait time (making i-net slowwer) . . .ok that's about how fast we runn off the fossil fuels , but ? what i suppose to do ? chk each time if my img.-s're ok ?? and if not ? split'em into smaller frames , ? write extra code for each frame ? (uploading 4 images (3 extra file headers) instead of 1) ???? delete the "not successful" upload from "blogger album" (takes to wait all blog images to load b4 you can delete any particular 1 OR navigate from 1-st to requred to delete 1) - in "one word" make a day full of job out of what should've taken 2 minutes why i always have to take a day free to uplaod single image - IT JUST SO ABSURD AS IT IS . . . sorry i don't need to purpose my salary to figure out another "virtual task" - i don't get your game to be honest (perhaps you're just stupid or smth. out of my reach) |
this is not a ready to use stuff
a snapshots from on going research dev.
it's like @ this Z-up the grid does THAT
[eof]
No comments:
Post a Comment