projectant

Good points, but continuing with the thought experiment, I think you fail to consider what might be a reality for your psychics. What if the psychics don't have perfect information, nor perfect control, but have, perhaps varying on the psychic in question, some amount of power that lets them see or control future numbers with some amount of probability, but not certainty?

In that case, they might win more often, but not every time. Given that so many things in nature follow a power curve or a bell curve, I think your presumed psychic abilities, we can assume, follow the same curves, and if most of your psychics then have "some ability" to predict these numbers, but not a certainty, then I think they are more likely to be frequent smaller winners.

For example, if you have an ability that let's you see a 4/8 of the future numbers, with 33% certainty, then one time out of three, you will win 4/8 of the numbers, and sometimes more than 4/8 if you're lucky.

TL;DR -- your presumed psychic abilities probably exist on a spectrum ( bell / power curve ) and likely most of your psychics do not have "perfect" future information.

PS - I have a feeling that psychics would prefer to play the stock market, than lottery. I just sense their expected payoff is higher in that case, probably because there are a lot more factors that affect a stock price, so even partial information across a lot of these seems to provide a better advantage, than partial information on 1 single list of numbers.

Clarance Jones http://archive.boston.com/business/articles/2011/11/05/frequ...

TL;DR - Audited by IRS but had 200 boxes of losing tickets & records in storage facilities, which the auditors apparently didn't want to search through. He ended up winning his defense against the state's tax claims as well.

How does he win so much? Is he psychic?

Hey there, Jemaclus! You are definitely welcome to submit a PR that includes the RNG as a multiline function. I'd merge it but I'd also keep the single line version.

Why?

Generally, I'll prefer code that can keep it's useful functionality within 5 lines, and this does.

Is the line "too long"? Not to me. My rule of thumb is if it is more than the width of Github atom editor on a non-handheld screen then it's too long. On my laptop it's 132 chars, but fits. Maybe another way to say it is, 140 chars or less, but I haven't decided about that!

And also, it's not disingenuous because, and this may be hard for you to believe but, I didn't actually write the rng as a multiline function then minify it. I'm good at writing RNGs, and I literally just wrote it on 1 line, tweaked in til it worked, and cut spaces. You can see history, here: https://gist.github.com/dosyago-coder-0/094497fdda0dbd7ef7f6... and the first change with the RNG is my first try, but it had some typos. The rng might look complex to you, but it's not. In my experience, it's a very simple generator, just looping endlessly over a state update function that uses xor, add and shift. I'm good at writing RNGs and I've had a lot of experience passing dieharder / practrand / smhasher etc. So it's easy for me to write an okay so-so "rng", in 1 line, like this. Impressive, right? To you, it seems like it had to have been / should be a multiline function. But to me, I'm fine to write it as a concise 1 liner, because I have more experience and aptitude at writing RNGs than you. That's all.

And I want this repo to be about that. People shouldn't have to dumb down their own code so everyone can understand it at first glance or agree that they would write it in the same way. The files ought not be constrained by 1 style, but everyone is free to have their own contribution, within some limits. The main ones being: it works, and it's 5 lines. This is not "code golf", and we're not trying to obfuscate, just keep it in 5 lines. Ultimately, I'll be the judge of what's too complex or not, and I'll make a note on your PR if I reject it. Meant to be a celebration of diverse styles and thinking, in concise little packages.

If you have some you feel are impressive, hit me up with a PR. I'd love to merge them in! Any language, py, java, whatever. Keep it coming :)

My ultimate aim is to make this a useful resource, and maybe an object of curiosity. Something people can browse on a Sunday afternoon, not too taxing, but maybe a place you can discover / get inspiration for some interesting code in a tiny package. I think keeping them 5 lines or less makes it easier to digest, and maximises the chance you can actually get influenced by some new way of coding or thinking that someone else does -- or just find a useful util. Anyway, I thought it was fun to do last night at 3 am, so let's see what happens. You and everyone are welcome to join in. Don't be shy with your good utils!

Could it be a chemical agent combined with RF or micowave field that activates it?

Seems like pure microwave would cause a range of random hallucinations and sensations. And also accidentally target people who were not spies / employees.

I think biological agent that's activated by EMF is more likely.

This happens. It's not good that it happens but we must expect it to happen.

What power to we have?

Change our perspective.

These online services which area now beginning to dip their toes into censorship / advertiser-hedged editorializing, are not to be seen as reliable ubiquitous platforms existing for the convenience of all. As much as they perhaps want to be seen as such, their actions belie this.

They are closed niches with particular stances, and their loyalty is never to us, despite marketing.

And we can treat them as such, we will be okay.

Backup your things. Use multiple providers. Use multiple accounts, a burner account for content against their editorial stance, and a longer lived account for other things. Run your own services. If you despise this state of affairs so greatly, form your own business services, and ape to take some of their market.

Tl;dr they are not our friends. Stop expecting them to not betray us, expect betrayal, and keep them at an appropriate distance.

Don't complain. Just start doing it if you want to protect yourself against it. I think github and npm can be included in this.

This is still very early prototype and there's a lot more to do. It's about more than getting selectors, they're just the basis. But I'm just putting it out here in case anyone finds it useful even at this early stage.

If you want to look at it you also need to clone https://github.com/dosyago-corp/pa-os-server

To run you need to run both projects at the same time.