Any recommendations for backing up (private) keys? Like pgp keys for example? I consider printing them on paper, as text or QR code. Anything better than that?
Periodically copy them to an encrypted external (thumb) drive and keep that in a safe place. Use two if you want to store one of them off-site. Piece of cake with LUKS and dm-crypt on any modern Linux distro. Just use a long passphrase that you can remember.
AFAIK, quite some components (Hadoop, Kafka, Spark, etc) of a typical big data stack are JVM based. Scala is JVM. And quite some people hate Java. That could be an answer.
For people with just some basic computer graphics background that don't know what this "deferred rendering" is: when this technique became popular, these [1] slides were popular and inspired many.
It even inspired a WWII plane game to use deferred rendering, which optimizes for having many lights on an object. Even tho they for the most part had only one light source (the sun)...
Many lights is not the only advantage. There are some deferred decalling techniques that I could see be very useful to a flight simulator for terrain drawing, for example.
I've been looking at the game engine 'Leadwerks', and impressed with what I see. Apparently uses deferred rendering. Means bigger environments and more lights possible from what I read. Good hardware is needed though as it eats VRAM. Beyond that, as a designer-dev, I suppose I don't need to know too many details about it.
I guess it is because of the use of amplitude modulation [1], where the envelope ("strength") of the carrier (that is some higher frequency signal) follows the signal that is modulated onto it (speech, in this video). With say FM it wouldn't work, I presume.
If you listen to an FM signal interpreted as AM you can often still make out the audio, it'll just be very clipped and noisy. That was the result when I did this with an RTLSDR, at least
I think that learning of (and avoiding) the Granny Knot [1] is the best I ever learned about shoelace knots. If your shoelaces occasionally get loose while walking, check it.
> As the linked article mentions, the solution was to optimize a massively-parallel algorithm by finding coherent rays that can be efficiently calculated together. It's a batch method: start casting a bunch of rays, identify similar rays and group them, calculate collisions for each group, cast reflected rays, identify similar rays and group them, etc. What I like about it conceptually is that in a way it treats light as a field rather than as individual directed rays.
How does this differ from "coherent ray tracing" and "ray packets", like people have been doing the last 15 years?
They're generating millions of rays to trace them at the same time, so they should be able to use packet tracing and they seem to use that [1]. Incoherent rays can be extremely troublesome when tracing packets, as you could be entering a branch of the BVH for just a few rays in the packets and in that case you're wasting a large part of the SIMD vector. There has been some research to alleviate that [2, 3] and creating more cohorent batches alleviates it even more. One of the other big problems of packet tracing is that there is no good way to handle motion blur, but if they're generating millions of rays at once they can just create packets with rays that are all in the same time interval.
I've already gone beyond my understanding of the technical details. The paper probably goes into it (linked in the sibling), and it also looks like it cites Wald.
Just noticed it also has the proof-of-concept city scene I mentioned on the last page.
The most likely explanation is they sent her a message saying pseudonyms are not allowed, and asking for her real name. She replies something like 'My real name is XYZ, here is ID to prove I am a real person, but I do NOT wish to use that name, please continue to call me ABC on the site' but Facebook simply went ahead and changed her name from ABC to XYZ against her wishes. No secret data mining, information collection or machine learning required.
One explanation is that Facebook collects its users contact lists.
That way, it can create 'shadow-accounts' for people that don't have yet a Facebook account. So when/if that person finally creates a Facebook account with some data tying him/her to a shadow-account, Facebook can directly propose relevant contacts and already knows a lot about that person, including his/her real name.
This doesn't suprise me at all. Big data-hungry companies like Facebook or Google know A LOT about you. I'd say they even know a lot of things about their used that their used don't even know about.
I'd be very surprised if Facebook didn't know my parents' names, my kids names, my shoe size and any other piece of information I haven't provided explicitly.
Just assume that anything that you entered on any website, or that you mentioned directly or indirectly to anyone on Facebook is available to Facebook.
In the creepiest of worlds I imagine this: on a non FB website with a FB "share" button on it, I congratulated a friend on her birthday five years ago. When she gets a FB account for the first time tomorrow, Facebook already has her shadow account with good Guesses of her details, including the birthday and real name.
he could meant JDK, the server runtime many things in Java. and I know the thread Im posting. you do not need to tell me. You do not need to mention it like that.
