OUTER HEAVEN

File: hiroyuki-lied.png (1MB, 2678x4000px) Image search: [Google]

1MB, 2678x4000px

bump for interest

>>58100000

you expect someone to read all this shit?

>>58104648
the three pics I posted here sum it up

File: 1390356596031.jpg (33KB, 512x672px) Image search: [Google]

33KB, 512x672px

>>58104575
>https://endchan.xyz/POLAK/res/15.html
WTF is all this?

>>58104648
Yeah fatty, start reading.

>>58104575
of course it's larping you spasticated chucklefuck

So what's the end game of a cyberwar with russia and the shut down of most of the internet?

>>58104701
quite elaborate and lengthy just for some LARP on endchan, where only few will read it, hu?

>>58104721

Could be mental illness

>>58104721
Yeah, seems a little too meaty for a LARP

Someone explain

>>58104727
Spend some time on /x/, people go to extreme lengths to tell a story.

Dungeons and Dragons for the 21st century

>>58104724
that shit is rampant man.

>>58104575
That's nothing. You can't catch Podesta.

>>58104753
It's almost like you'd have to pay a bunch of people to do this

File: shut it down or sumthin.jpg (7KB, 225x225px) Image search: [Google]

7KB, 225x225px

I don't know what to believe anymore.

>>58104575
What is it?

>>58104822
Found another post here

>>>/pol/thread/103843493

What's the path people take to end up in a back room at the NSA or FSB working day and night to tear down the world's software and prepare/participate in cyber warface against another nation and the citizens?

File: 3wv1ktS.jpg (461KB, 1920x1080px) Image search: [Google]

461KB, 1920x1080px

>>58104860

Probably mathematics, maybe strong computer engineering, and strong programming knowledge and then you get noticed and recruited.

Shitposting on chans and writing shit code all day won't get you involved.

Bump for interest.

All we, if we are not smart enough to understand the explanation given, can do is share this info with more competent people so they can find out if it is true.

nice video game screenshot. very believablae

simple summary:
> Wikileaks releases large insurance files from time to time
> they contain info that is very incriminating for governments
> the files are encrypted, keys only to be released in case of death or danger
> since mid Oct. many people assume Assange is dead and only faked to be alive still
> Wikileaks seems comprimised, too since Assange has gone missing
> people are working on decrypting the insurance files since
> everytime they try to release the keys they get shut down immediately
> now they explain to everyone how to get the keys themselves
> they also work on releasing the files in various ways
> it seems there will be a big event / outage when they do
> today is the day they planned for release
> we share the info

HOW TO GET THE KEYS (AND MORE) FROM THE BLOCKCHAIN:

The goal is to make very simple code that is easy to use and understand so that everyone can do this. This is a rough explanation of how it works.

There are two main approaches users are taking to decode messages in the blockchain. Scanning transactions, let's call this 'tx scanning', and scanning blocks, let's call this 'block scanning'. The main reason users are not yet able to see meaningful content is because both approaches have to be combined.

>>58105206
Thanks for the summary

>>58105206
https://endchan.xyz/POLAK/res/15.html

>the explanation how to get the keys

>>58105237

TX SCANNING:
When you scan by transactions, you look for a transaction number (tx id), and decode its contents. When you know the tx id, you can easily see which wallets were involved. Some messages require you to combine the decoded data from multiple tx ids. You can identify which tx ids are relevant by looking at transaction histories of the wallets involved. This strategy is used for the 'Cablegate Backup'. In that case, the list of tx ids is directly told to the readers in the first message. However, you can compile this list on your own by 'tx crawling'. To do this, follow these steps:
. For each tx, look at the wallets that received money and find those that spend it (in this case it is only one per tx).
. For that wallet, look at its transaction history and find a transaction that follows a similar pattern, i.e., it involves multiple wallets and only one spends the funds.
. Continue doing this until you are not able to see the pattern repeat itself.

File: 1479164538153.jpg (149KB, 800x820px) Image search: [Google]

149KB, 800x820px

go back to /pol/

>>58105257
BLOCK SCANNING:
When you scan by block, you will be able to find encoded data more easily but it is harder to extract the tx id and wallets. One benefit of block scanning is that you can explicitly search for file headers and important strings. For example you can directly search for the magic numbers in GPG files. When you find one of these, you can then tx crawl from that starting point in order to get all pieces of the file. More concretely, if you want to find the Cablegate Backup with a block scanner, you could search for the magic number of Zip files. Then, when one is found, you can find the tx id that contains it, and finally tx crawl to get all the pieces. Yet, file headers are just one of the many other patterns that can be used to find important transactions. Examples of others are:
. Magic numbers: Look for the first bytes in different types of file. 'file' can be used in UNIX.
. Ability to compress: Compress the decoded output. If the size is reduced, the output is possibly a message or part of a file.
. Text: If the decoded output has text, it might have information.
. Keywords (Very important): Search for relevant keywords, e.g., checksums for files in Wikileaks.org, checksums for the insurance files, hashes, dates, names, time stamps, etc.
. Reversibility: Some messages are in reverse and need to be flipped. This should be tried both before and after decoding.

>>58105267
Both scanners have to be used. The starting points for the searches should be Wikileak's wallet, important dates (for example, during the DDoS attacks), previous messages and checksum hashes. The Cablegate Backup was a bit simpler than the more recent messages. In that case, only one wallet spent the funds in each transaction, and simply looking at wallet's next transaction was enough to find all the pieces. Newer messages are bit more complicated. Some of the wallets that receive money make multiple transactions with no encoded data before proceeding with the 'real' transaction. Moreover, in a lot of cases, all wallets involved spend the funds (not just one). Therefore, the crawler has to keep track of all wallets that receive funds, and all future transactions of that wallet while using techniques (like those above) to detect encoded data. A transaction tree should be kept and the pieces of each files should be combined in multiple orderings.

If you implement the process described above you will find all the keys, other backups and other files that are not released. One way to test your code is to search for checksum hashes for files that have already been published at a specific date. There are multiple messages in the blockchain that include file hashes and dates.

>>58104724
this
You'd be suprised what the imagation of a schzoid dreams up, they can be clever people too so I wouldn't put it past you that this is an elaborate LARPing.

That being said it could be true. Don't get caught up romanticising espionage, you'll feel silly if it's literally nothing

>>58105288
I take this as possibility, of course.
But IF there is something to it we should not ignore it.
It is up to more competent people to find out.

>>58105288
>you'll feel silly if it's literally nothing

It's entertaining, like a good book, either way

>>58105288
Seriously, it happens like once a month on /x/ and the best way to get your LARP/viral shit rolling is to put it somewhere no one will read it and then go somewhere far more popular and feed the whole "I stumbled across this/I think this is being suppressed" spiel. Putting this shit in as obtuse a place as possible actually lends it legitimacy in the minds of those who want to believe, it makes it more secret.

╠╣Є└ þ

мҼ

│g│

File: 1482318545307.gif (1MB, 720x404px) Image search: [Google]

1MB, 720x404px

>>58105206
TO ALL "this is a conspiracy" TARDS:

https://www.youtube.com/watch?v=_sbT3_9dJY4

look it up yourselves!
assange was killed!
this interview is faked!

>>58105354
Don't you think it makes far more sense that RT edited that statement to make Assange come across as more damning to the US than he might have been rather than him being dead? they do that all the time.

>>58105354

The tech is there to fake an interview like this

https://www.youtube.com/watch?v=ohmajJTcpNk

Do you people also think that all of /baph/ was larp?

>>58105354
That was a cut probably to remove a slur, stutter, or pause in his speech.

It is literally the most common piece of interview editing done ever to help fit the most amount of content into the least amount of time.

File: 1478846979518m.jpg (113KB, 576x1024px) Image search: [Google]

113KB, 576x1024px

>>58105391
Why are you spamming this in every Asdanges thread britfag. This is literally Alex Jones tier trash. That tech is obviously CGI, every movie you see is obvious CGI. The closest tech demos to real life renders can be identified as CGI.

But no
>Asdanges is kill because I saw PJW say so.

Neck yourself crumpet nigger.

HOLY FUCK MODS STICKY THIS THREAD ALREADY

>>58104575
>The part about PS3s
I remember that article about the air force; this is 100% /pol/kiddie LARP garbage.

>>58106519
HOLY FUCK KILL YOURSELF ALREADY

this is shit is even more bullshit than pizzagate

>>58106574
>Shut it down
Yeah no. Fuck off

>>58104575
This is cringeworthy as fuck.
If they had info they wanted to realise, they would actually release it. Anyone going around calling themselves "operation skye" obviously has nothing better to do than think up codenames.

>>58105625
>Do you people also think that all of /baph/ was larp?
God no. They were well below LARP - LARPers know that they're playing make-believe.

>>58104575
Fuck off with this stupid bullshit
>>>/pol/

>>58106652
Anon please read
>>58105206
>>58105354
>>58105391


I'll be honest, I voted for trump mainly because of youtube videos like >>58105354

File: ASUS-ROG-GT51CA-Malaysia-Launch-13-370x260.jpg (32KB, 370x260px) Image search: [Google]

32KB, 370x260px

lol what kind of nerd speak is this

this is /g/ god damnit, let's post speccys and discuss about GPUs

>>58104575
/g/ is dead. It's a consumer board, not a tech board anymore. /prog/ WAS where the real shit WAS at.

>>58106696
> I voted for trump mainly because of youtube videos like >>58105354
You just fucked up.

>>58104860
Hack secret shit, and got on their radar. You either get cart blanche to do whatever you want if you accept or get sent to a floating black site prison in the middle of the indian ocean.

>>58107844
pretty obvious which one most people would pick.

>>58107898
You'd be surprised at how many moralfags hack stuff out of some self righteous sense of justice and would choose the latter.
Either that or they're too autistic like Gary Mckinnon and that lulzec faggot who's gonna get extradited to the US.

>>58107731
Don't we have a programming general for that though?

>>58106696
you don't belong here

File: 1475173411249.jpg (41KB, 375x500px) Image search: [Google]

41KB, 375x500px

>>58107499
yes goyim, lets us discuss my wares and cease any mention of this topic shall we?

>>58105206
I have one of these "insurance" files here. I have had it for a decade and its almost 2GB in size.

But all this sounds like nonsense to me.

>>58111730
I'm certain anon was joking and making fun how how modern /g/ is just consumer bullshit.