Anonymous ID: 5c686e Feb. 12, 2018, 5:48 p.m. No.357596   🗄️.is 🔗kun   >>7777

>>357462

Great. I have to log the fucking timestamps of any number of unknown posts or tweets or images and observe time deltas between them. Fucking great.

 

Snowden says he built HEARTBEAT and it was authorized by 2 levels of mangement. He spells "explicitly" wrong as "explicited". Unknown if the misspelling is intentional of meaningful. Now I'm supposed to look at Snowden's background and figure out is HEARTBEAT refers to hardware or software or what. I assume software but know little of Snowden's background.

 

>>357467

ALL CAPS ANON claims will be banned when (((they))) catch on. LARPish. Who will ban them and why. DistractionLARP?

 

A church(?) stained glass windows. Black veiled figure again, with smoke around. Inside the church if mirror images of graffiti on outside of blocked up windows indicates correctly. Content of graffiti irrelevant?

 

Raven Rock pic related.

Anonymous ID: 5c686e Feb. 12, 2018, 6:05 p.m. No.357774   🗄️.is 🔗kun   >>7862

>>357467

A NSA-approved program, called HEARTBEAT. So OK this is what Snowden claims to have built with 2 levels of management approval.

Fucking APAR. Jargon for a program fix.

Fucking PMR number. Jargon for error reporting system used by software customers to report bugs and track bug fixes.

 

Error description "Q CAPTURE" and "Q APPLY". Possibly pertains to a queue management system that might be used between data capture from possibly an intelligence gathering sources/inputs, and a database. Q Capture suggests a software semaphore where one process obtains exclusive use of the queue … to prevent database conflicts by separate processes trying to modify the same data table simultaneously and overwriting one another's data. A heartbeat would be necessary to prevent the queue staying locked if something went wrong.

COMMIT_LSN likely pertains to a database. The purpose of Q CAPTURE sending a heartbeat message is not known. Perhaps the heartbeat indicates that the process that captured the queue is still working on the DB. If no heartbeat occurs another process would release the lock and fix the DB.

The exact nature of this bug and the bug fix is unclear to me but I am fairly certain it pertains to a database mangement system frontended by a queue management system.