mircea_popescu: no. l' = rnd(0, l) ; if l' < 256 l' = 256.

mircea_popescu: https://www.ti89.com/cryptotut/rsa3.htm << very handy rsa tutorial in that it uses base 10 and alphabet-indexing for letters. so one can actually rsa by hand and get a good model of what's going on. ☟︎

mircea_popescu: https://www.tvfagaras.ro/wp-content/uploads/2013/10/media_136471005390712700.jpg <<< supposedly, angela merkel with a coupla friends, at romanian nudist beach (costinesti) in teh 80s.

mircea_popescu: http://btcbase.org/log/2017-08-08#1695470 << it is actually worth it, the code is not that lengthy. ☝︎

mircea_popescu: PeterL +# IMPORTANT NOTE: if the cs is too small, messages have a chance to get decrypted by the wrong key << what is the logic behind this ? ☟︎

mircea_popescu: PeterL +MAXMESSAGE = << how did you derive the magic number ?

mircea_popescu: http://btcbase.org/log/2017-08-08#1695453 << you have to. we'd be the first people to move to a cheaper test algo if this was feasible, in tmsr-pgp etc. but as he correctly points out, most of the keys you make are weak. an important point to consider here is weakness propagation : one weak key can potentially expose other key exchanges, resulting in a chain of (unknowingly) lost secrecy. the design will have it ablate over t ☝︎

mircea_popescu: PeterL http://btcbase.org/log/2017-08-08#1695421 << is this supposed to interface with sina's item ? ☝︎☟︎

mircea_popescu: http://btcbase.org/log/2017-08-08#1695413 << the quality of this summer of forks fails to impress. ☝︎☟︎

mircea_popescu: http://btcbase.org/log/2017-08-08#1695378 << dude imagines he's doing the batshit insane camp any favours by publishing more batshit insane ? srsly, "moon prison" ? ☝︎

mircea_popescu: http://btcbase.org/log/2014-12-16#954309 << juice ref ☝︎

mircea_popescu: http://btcbase.org/log/2017-08-06#1694691 << hey, if there wasn't a bar to meet, how would we get rid of all the 99% useless males women keep spawning ? ☝︎

mircea_popescu: http://btcbase.org/log/2017-08-06#1694690 << republican computing seems to be migrating towards pretty much that in general. ☝︎

mircea_popescu: http://trilema.com/2015/varia-varietatis-or-your-all-about-the-mollusc-guide/#selection-153.0-153.35 << fine example of worse-than-office tripot.

mircea_popescu: http://btcbase.org/log/2017-08-06#1694672 << muchly depends. if the office is the usual usian horror, and the casino floor is the item from glamour shots, with the floozies and the hookers and so on, definitely. but the casino floor can be pretty depressing, especially in fucking arkansaw. and the office can be a total insoutenable legerete de l'etre style hospital, especially in eastern europe 1990s "media" or whatever "i'm ☝︎

mircea_popescu: http://btcbase.org/log/2017-08-06#1694676 << same thing they ran out of in iraq/afghanistan etc. i'd say "men" but it's not really it. you could say "people" but certainly not it. you know, non-retarded, non-gender-confused etc etc human beings. ☝︎

mircea_popescu: http://btcbase.org/log/2017-08-06#1694478 << i did read the log you pasted. ☝︎

mircea_popescu: http://btcbase.org/log/2017-08-06#1694393 << it's most likely deep in the bowels of bsd-bdb interactions. ☝︎

mircea_popescu: http://btcbase.org/log/2017-08-06#1694380 << there's no "we fixed X" outside of a rewritten p2p model. what exactly are you going to fix ? orphan chain reorgs take a lot of db resources as it is now. ☝︎

mircea_popescu: http://btcbase.org/log/2017-08-06#1694347 << the problem seems entirely like slow node struggliong with lengthy orphan chain. ☝︎☟︎

mircea_popescu: http://btcbase.org/log/2017-08-06#1694341 << the method is correct, but entirely unjustified effort for the possible payoff. nodes wedge because legacy bitcoin is shit, this sort of chrome polishing you propose is to be reserved for actually written code imo. ☝︎

mircea_popescu: http://btcbase.org/log/2017-08-05#1694272 << you've looked at these neh ? it's a very strict format, first line the command, 2nd line the otp. what last year's codes fits this format ? ☝︎