>>6753

Here's some Java code for testing values using your method:

https://pastebin.com/PxKGHme8

I'm using a different Sqrt function–the link from the source is in the code; I modified it a bit. So far it's working as intended.

The css file is included in case anyone wants to skin it–just comment out the relevant line in the code if not (located in the "start" method).

I've got to go over things and see how everything relates. Had a big revelation yesterday after a prayer in frustration (see "old bread rehash"). I think I'm almost caught up :)

>>6774

Thanks again VQC—the more I look at the grid, the more I find. So many relationships and patterns; it's magnificent :)

I'm thinking this may be where the recursive algorithm starts to come in? With an 'e' over 300 digits in length, it seems like a few more rounds of squaring and storing results might be called for. It's so satisfying to watch that number get chopped down to something comprehendable, even if it's just play-acting.

>>6812

Forgot trip.

VQC, I don't think I can edit the article as I'm basically barebacking. But don't you want credit for this? And if so, how should you be given it? Twitter handle?

I'm sure it will all come in time. As magnanimous as you are, though, do you think it might be a good idea to claim credit?

Consider how many brilliant inventors there are that most people have never heard of–maybe you're comfortable knowing that God sees your good acts, and J know this to be true and reward enough. But there is something to be said about the hijacking of the message; we have no idea how Doug Engelbart saw things, but we know exactly what the men who pirated his ideas think–they're still venerated to this day.

Then again, maybe that has more to fo with corruption than anything. I can't imagine there will be much joy from the bad actors in Europe once we fly their dirty laundry.

I hope this is not what you mean when you speak of sacrificing yourself to this. I really hope you're just referencing the money you stand to lose by sharing the idea rathing than capitalizing on it…

>>6816

That was not my point. My point was this: when a message is received, if the messenger isn't there to interpret, pretenders will certainly be more than willing to make the interpretation. This is trivially easy to prove: the New Testament is rife with Jesus condemning the Pharisees and Sadducees for twisting the Word of God to their benefit; similarly, we have the Catholic Church's storied history, Buddhist monks in designer fashions, hundreds of nuclear bombs for every nuclear reactor, etc.

There is a reason why the membership of the Council on Foreign Relations is structured as it is: those in media, social media and higher ed twist our perception of right and wrong, while bankers, international corporations and government officials do wrong. By placing their members at the critical distribution points of our shared reality, they've managed to put rings in our collective noses and bring us to heel.

Rest assured—in the absence of an intervention of Biblical proportions, this knowledge will be used (in large part) to deliver porn before it is used to save lives. Maybe it really wouldn't matter if Chris revealed himself–Doug Engelbart wasn't hiding; it's just that nobody cared to solicit his views.

>>6817

I understand, in a very personal way. I went down that path and ended up just short of homelessness. I got your "three rivers"(?) reference awhile back, but didn't want to bring it up–shitty way to introduce oneself.

It's your message to give–God gave you the understanding for a reason, and this student will respect the teacher's wishes. At this point, I have no idea what I will (or even can) do with the knowledge, but I pledge to you that, so long as I make money off of it, and I have a way of contacting you (or vice-versa), neither you or any member of your family will want for their share.

>>6821

Thank you for sharing your insight, Hobo–these are wise considerations. I know nothing about cryptocurrencies; I would be lying if I didn't hope to get a few bitcoins out of this, but I never expected there to be any left by the time I caught up. It sucks, given that I've probably invested over 2k hours toward the Q movement and this by now; that could've translated into enough scholarships that I wouldn't have to work while going to school. But money can't buy this (unless Chris is giving private lessons somewhere).

I honestly think it is inevitable that cryptocurrencies go down, once this knowledge is out–if not from one of us, then from the next ones who draw the connection. We have no idea who is monitoring this thread; my guess is that some are prepared just as you have described. Once the news spreads that RSA has been broken, there will be a rush to sell. It is Chris' wish to let this news out, none here will deny it; it would be best to cash out asap, imho.

Also, as you have mentioned—I think there's a lot to be said for doing the right thing. From the outset, I felt that the real test here was not whether we could be one of the first to understand the language of Creation, but what we did with that knowledge. This point in time is precarious–it feels, for lack of a better word, "pregnant." If we are reaching a pivotal point in our existence–one in which the Veil is lifted and we come face-to-face with our Creator, I wouldn't want to have to explain why $2 Billion worth of bitcoin was spent developing dildos that could read one's mind and be several places at once.

I was looking over that wave equation originally posted in general #2—without knowing all of the functions, you can still get some idea of how everything is working. The key is what followed the equation:

>as |fi| approaches ∞, acos(((1-(fi/(fi-1))).5))5)/3) approaches π, and, of course, acos(((1-(fi/(fi-1))).5))5)/3)-π then approaches 0"

Once you substitute π for the 'acos(…)" equation, it renders down into a pretty basic trig function which is in turn modified by other functions whose effects (if not methods) are pretty familiar. For instance, the 'l' function will affect the amplitude of the wave, and the 'k*' part will affect the phase. The 'j' function seems to affect the period, but I wouldn't know without more research. The 'j' and 'l' functions are time varying as well.

It's worth noting that if the 'acos(…)' function tends toward π, with its ratio of the i'th iteration of the Fibonacci sequence over the i'th iteration of the Fibonacci sequence - 1, there is a similar function just to the right of it that is getting closer to π as well–just at a much slower rate. But the difference between them, even after only 8 iterations, is relatively small.

I made a graph on Desmos with some dummy variables for j, k, and l; one of them is set to the 8th iteration, the other one tending toward a large number of iterations at a point where the left-side equation is about 500x closer than the right toward infinity.

So it's four series/summations running in tandem, some of them functions dealing with time and other factors, and as those numbers grow larger it gets closer and closer to what I would expect is as good of an approximation as anyone might ever need–kind of like going from an 8-bit image, to 16, 32, 64, etc. I'm pretty sure anybody familiar with quantum mechanics at that point would have decided it was time to listen closely.

Here's the link:

https://www.desmos.com/calculator/3wkhcwllmx

Guys, pretty sure I got something big.

Pics related use the following color code:

Red for primes

Dark red for Fermat primes

Blue for semiprimes

Green for squares, cubes, etc, with darker green == higher power

In the 2nd image, notice how certain squares seem to follow the curve of the spiral on the left side . If the spiral can largely be described by n >= (e * e / 8), some of the squares on the left look like they could be described by a similar functions. I decided to look for similar patterns inside the spiral, and I found some. Lots of them.

"BigTreeShrunk.png" is a smaller version of a huge file I've uploaded here:

https://anonfile.com/W5pdsff8b9/BigTree.png

(~7k x 28k, but only 2.8 MB)

In the larger version, you can zoom in on the values for the first 't' entry. If you follow the pathways down, you'll notice that they're almost all continuous & hit sequential prime numbers.

I used the following method: starting from a prime, I would add an even number 'g'. From then on, I added g + 2, g + 4, g + 6, g + 8…etc. In that fashion I was able to hit as many as 29 primes in a row–from 41, 43, 47, …, to 971. It might have gone even further if I'd made a larger image.

The line in the center is somewhat of an exception–it hit a Fermat number (257), then a square, semiprime, two primes, semiprime, four primes, semiprime, then 6 primes when it hit the bottom; it was like a motorcycle that hit a bump then started righting itself.

Several sequences end up on squares–I usually didn't bother taking them further. Also, it may be confirmation bias but it seemed to me like a lot of the sequences converged on Fermat numbers.

There's a lot to learn from this–I haven't even looked for patterns in the other direction, and there are tons more than I can see but haven't mapped out yet. Thus far I've only looked at things in terms of 'c'. But I'm pretty blown away.

Please tell me you guys didn't figure this out seven months ago.

Side note, I came across an interesting article yesterday:

https://www.quantamagazine.org/mathematicians-discover-prime-conspiracy-20160313/

>Among the first billion prime numbers, for instance, a prime ending in 9 is almost 65 percent more likely to be followed by a prime ending in 1 than another prime ending in 9. In a paper posted online today, Kannan Soundararajan and Robert Lemke Oliver of Stanford University present both numerical and theoretical evidence that prime numbers repel other would-be primes that end in the same digit, and have varied predilections for being followed by primes ending in the other possible final digits.

Paper mentioned in article is attached.

Also, the sequence from 41, 43, 47, …, consists of 40 primes, all the way to 1681.

Here's a quick code snippet for anyone wanting to test how far a sequence goes:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

public static void startSequence(){

int n = <your first prime>;

int m = <the first even number to add to your prime>;

int count = 0;

while(n < 4096 && (PRIMES4096.contains(n) || FERMATPRIMES.contains(n))){

count++;

n += m;

m += 2;

}

System.out.println("count: " + count + ", Last n value: " + n);

}