Given that in principle, a hashing function is meant to produce a unique output for any input, would that mean if you could reverse the hash, you could reconstruct a huge input?
I listen to the same album of calming music every single night. I don't want it to be factored into the algorithms because I listen to it so disproportionately more than literally anything else. I don't actually listen to music more than a few times a week on average just for context.
I have a reminder on my phone set to select private session before I play this album so that it doesn't influence my personalized playlists, wrap up, or anything else personalized. In the months that I have been doing this, I have now forgotten to hit private session before hitting play twice. Last night was the second time.
It is really frustrating to me that we can't just delete played tracks from what gets included in the algorithm. The personalized stuff based on what I listen to is the whole reason I'm on Spotify in the first place.
This is making me afraid to listen to my calming music. It is the same album of calming music that they put me to bed with when I was a kid. First on cassette tape, then we found it on CD. I just found it on Spotify.
I am so happy I get to listen to this music again, but I would like to do so without that getting in the way of the music recommendations or other personalized benefits I get from Spotify based on my music taste.
I have started to compulsively check and double check and triple check that I have private session selected. This should not be that big of a problem. Just incorporate a way to remove played tracks. It shouldn't be that difficult and it's interfering with my life at the moment.
Does anyone have any advice on what to do from here moving forward?
On July 18th we should go to the YT hq and force them to delete all the bad youtubers and make the algorithm far for everyone. Whose with me
I've done this before using an older system with non-rolling-codes. It worked out great. I used an SDR dongle to capture the bits, and I programmed an arduino to replay it through an RF transmitter board I purchased. This particular gate however serves multiple neighbors with their own key fob. The product I'm trying to reverse-engineer boasts that it uses both encryption and rolling-codes. I have a feeling that this device is much easier to crack than advertised - or this level of security is mainly targeting outsiders who do not already own a key fob (a non resident). Perhaps if I take enough samples right after each other, I can study a pattern in the bits and understand the data/algorithm.
The system fob brand is a "Doorking, "DKS", Microplus 8069. As when I did this before using the simpler system for a different gate, I glanced at the FCC documents to find that the RF range is around ~315 MHz. Having glanced at the FCC docs again for the new system, I lucked out...it's around ~317 MHz. These RF transmitter boards might work if I can figure out the other roadblocks. FCC docs: https://fccid.io/LSD8068TX.
I'd love to figure out this riddle! Can anyone here point me in the direction of reverse-engineering this algorithm and/or helping me understand whether or not cloning this fob would even work?
The data:
Here is some info I've gathered from 4 successive clicks recorded via RF SDR and translated from a sine-wave to bits:
There is about 224 bits of data in each packet.
The first noticeable pattern is the ~16 bits (2 bytes) in the beginning of each click of the fob. It's always the same sequence of on/off/on/off. Then there is a byte of 0's. The first ~24 bits of data seems to be consistent.
This then turns into the meat of the data. There is about ~200 bits of data transmitted after the first sequence. Out of about 200 bits, the last ~96 bits (12 bytes) or so seem to always be the same.
I am wondering if there is any way to interpret some of this data (or if there are any other things to note). Perhaps the 1st part of the data (which is always the same) identifies the fob as belonging to this community (or just queues up the receiver to start listening), while the tail end (last ~96 bits) is the encryption bits used to decrypt after the code is transmitted and received. The first 104 bits of the "meat" (13 bytes or so after the initial 3 byte
... keep reading on reddit β‘
Captain Ahab, Jim Jones Followers, Custer, the list goes on.....
it is really sad. I wonder how long before they get the memo that the party is over?
Related Accounts:
- /u/alleninstitute
Introduction: >Hi Reddit. We are R. Clay Reid and Nuno Maçarico da Costa, researchers at the Allen Institute for Brain Science. To truly understand the brain, we need to understand the connectome: how it's wired. The mouse brain has ~70M neurons and hundreds of billions of connections. As part of a collaborative effort to map every connection in a cubic millimeter of mouse brain, we started with a circuit that fits within a cubic millimeter and contains 100,000 neurons and hundreds of millions connections. Even at this scale, the effort has been immense.
>Allen Institute scientists sectioned that piece of cortex into 25,000 ultra-thin slices, and then used an automated electron microscopy pipeline called piTEAM to image these slices. We filled a room with electron microscopes and, over the course of six months, took 125,000,000 of high-resolution photographs of brain circuitry and assembled them into a 3-D volume.
>In collaboration with Princeton University, the entire multi-petabyte dataset was segmented using machine learning to extract brain circuitry. This entire process is analogous to creating Google Maps from the raw images in Google Earth. The result is the most detailed anatomical reconstruction of neurons and their connections to date. Eventually, we will register these reconstructions to other properties of cells such as their physiology and their gene expression, creating and integrated body of knowledge of brain cells across many spatial scales, from organelles to circuits.
- Relevant article in Nature Communications.
(Somewhat natural or rustic noun or adjective) + (Any location or thing where something can "be in")
Try it yourself!
>> python3 genfortune.py from intelliname
- Badger House
- Bone Table
- Rose Canyon
- White Town
- Sandy Canyon
- Night Corner
- Bull Mountain
- Stone Castle
- Ivy Rock
- Dreamer Gate
- Blade Hill
- Oak Pass
- Sun Town
- Tall Beach
- Flower Tale
- Ocean House
- Tall Tale
- Flower Castle
- Battle Tale
- Bottle Town
- Black Tale
- Blue Table
- Red River
- Timber Pass
- Torch River
- Night Table
- Stone River
- Badger Tree
- Echo Mountain
- Lantern Run
- Star Peak
- Gallows Bridge
- Red House
- Wind Town
- Ivy Path
This post at http://www.reddit.com/r/privacy/comments/27zoyu/reverse_algorithm_that_identifies_private/ was censored by Lugh at /r/privacy.
Using DNA, blood, a strand of hair, or any available genetic data, researchers from Whitehead Institute of Biomedical Research in Cambridge, MA, Tel Aviv University and the National Geographic have developed a reverse algorithm that can reveal private information. Like your name, surnames, SSN, identity, address and well as other private information, including your geographic locations, the names and SSNs of your relatives, etc. A news alert was put out by http://www.aftau.org/site/News2?page=NewsArticle&id=17947 but they took it down after I started asking them too many questions. The Whitehead Institute of Biomedical Research in Cambridge, MA also took down their site after some of us started asking them intrusive questions. Anyone who knows more details, please share.
Likewise, the LDS (Mormon) Church has started compiling such information from area hospitals, labs, clinics and from the Intermountain Health Care Group. If anyone knows more about this too, please share.
Hi,
Recently, SimpleLogin made a change in the generation algorithm for reverse alias. But finally, a rollback will be done soon. If you don't know about this, more information can be found here : https://simplelogin.io/blog/reverse-alias/
The reason for the rollback is :
>However thanks to our users, we realized that this change wasnβt ideal as the original sender address can be programmatically extracted by your mailbox service, even if you have PGP enabled. PGP indeed only encrypts the email body and leaves the email headers like From, To, Subject fields in plaintext.
This is a totally valid reason to take in count all the possibilities (and from my point of view, this is another reason I like SL, they don't just go in a way "and that's it, the users will have to adapt" like too many services ;) ).
But what about the Sender Address Format in the settings?
>When your alias receives an email, say from: John Wick <john@wick.com>, SimpleLogin forwards it to your mailbox. Due to some email constraints, SimpleLogin cannot keep the sender email address in the original form and needs to transform it to one of the formats below.
I guess any value of this setting could also be programmatically extracted by the mailbox, am I wrong?
The link contains some general information about rotation algorithms, C source code, and a benchmark table/graph.
https://github.com/scandum/rotate
The conjoined triple reversal, as the name suggests, is a triple reversal variant that significantly increases locality by conjoining the three separate reversals where possible.
Hey sorry if this isnβt allowed but I recently tried to figure out the ranking system used for cricket batsmen and obviously it wasnβt very statistically sound. I was wondering what tools there are or how (or if) you would go about trying to reverse engineer an algorithm like this in a more sound manner. Thanks
Hey Lugh: here's the source you wanted (https://web.archive.org/web/20130429234250/http://www.aftau.org/site/News2?page=NewsArticle&id=17947), so don't you dare delete this now asshole -
Using DNA, blood, a strand of hair, or any available genetic data, researchers from Whitehead Institute of Biomedical Research in Cambridge, MA, Tel Aviv University and the National Geographic have developed a reverse algorithm that can reveal private information. Like your name, surnames, SSN, identity, address and well as other private information, including your geographic locations, the names and SSNs of your relatives, etc. A news alert was put out by http://www.aftau.org/site/News2?page=NewsArticle&id=17947 but they took it down after I started asking them too many questions. The Whitehead Institute of Biomedical Research in Cambridge, MA also took down their site after some of us started asking them intrusive questions. A lamer archived version is at https://web.archive.org/web/20130429234250/http://www.aftau.org/site/News2?page=NewsArticle&id=17947. Anyone who knows more details, please share.
Likewise, the LDS (Mormon) Church has started compiling such information from hospitals, labs, clinics and from the Intermountain Health Care Group. If anyone knows more about this too, please share.
Both the LDS Church and the Whitehead Institute-Tel Aviv University-National Geographic alliance aim to build a global database according to the Whitehead site that they took down.
Edit: The archived version at https://web.archive.org/web/20130429234250/http://www.aftau.org/site/News2?page=NewsArticle&id=17947 is the modified version that makes TAU researchers look like privacy advocates. The original version clearly showed all researchers were excited at the possibility of using DNA data to unearth privacy details of individuals. They also don't mention the complicity of National Geographic in collaborating with them. Fuckers at both the Whitehead Institute of Biomedical Research in Cambridge, MA and Tel Aviv University took down their page after I started asking them too many questions. Then they put up a changed heavily-watered-down version which is now archived.
