VertexRed
Joined 10 years ago
Karma
51
Submissions
58
Member since
Aug 11
Recent submissions
Comment · 7 years ago
Comment · 9 years ago
I'd recommend using larger images resized to a smaller size or SVGs since the current checkboxes look blurry on iPhone.
Comment · 9 years ago
Looks cool, some things I would add:
- Increase vertical scroll after adding a widget.
- Add code detection from title to save some time:
- In the video you set the title to "Ruby Methods Example".
- Loop through the languages and change on match.Comment · 9 years ago
There isn't enough info to automatically close accounts just because they use the same name and profile photo as other users (keep in mind that profile pictures can be of anything such as a flag found through Google Images).
They probably only investigate and close imposters if they receive complaints from other users.
Comment · 9 years ago
This sounds more like encryption than compression and I don't understand how it could save space the majority of the unique data is still needed for each movie.
I hate to say it and I would love to be proved wrong, but my theory is that it was a hoax (an impressive one as he was able to convince big names) and I think he did it with encryption. Here's what I think: what's fairly established is that Sloot used "shared resources" which each user of the system was required to have in order to decompress/view the movies (here's a picture of the box with the shared resources: http://www.nethwork.nl/images/kastjesloot.jpg).
Now this box had one or multiple storage devices which stored encrypted copies of the hundreds of movies that he used for the demos (with perhaps some RLE to save space). The chipcard contained the secret key for each movie and here is how I think it worked:
1. The chipcard (8 KB in size) containing a secret key is inserted into the machine.
2. The source code is decrypted using the key and compiled for each run (this would explain why no one was able to get their hands on the source code).
3. The movie is extracted/decrypted from the shared resources by following the sequence provided by the secret key.
In other words, he got away with storing the full sized movies on the disks simply by saying that they were shared resources.
Once they got a few days away from the release the realization that he be exposed, caused the stress that lead to his unfortunate death.
Comment · 9 years ago
Another theory that I read was that Sloot had somehow linked analog and digital (he was supposedly a TV technician before) and that he was parameterizing data from an analog signal using a small amount of data.
Source: http://jansloot.telcomsoft.nl/Sources-1/More/CaptainCosmos/N... (comment by Koen near the bottom of the page).
Now conspiracy theory or not; one can't claim that it's not an interesting read since he privately demonstrated it to at least 20 people and was also able to get Philips to work with him.
Comment · 9 years ago
Nearly everything that you do on a page is trackable if you have JS enabled including how you moved your mouse on the page (https://api.jquery.com/mousemove/).
To keep the technical details short: the events are logged with JS and sent over either ajax or a websocket in the background as you navigate the site.
Comment · 10 years ago
If you want to add a huge improvement for this, then listen for the hash changes, and switch to the correct tab once changed so that they change when the back/forward buttons are pressed.
Comment · 10 years ago
The biggest issue that I can see with this is abuse.
Do you have a way of preventing email spam and outgoing DoS attacks?
Comment · 10 years ago
This is fun gag to play.
But something that would really awesome would be if you could call your script if an unknown command is run and have the script look for a command that's most similar to the misspelled one and ask if that's what the use meant (or even auto run the corrected command).
Comment · 10 years ago
But how will you install it on the phone?
They only allow installs through App Store.
Comment · 10 years ago
Wouldn't that require a jailbreak?
Comment · 10 years ago
It's 2016, everyone has JS enabled.
The ones that don't are most likely bots (now even that's changing thanks to projects like phantomjs).
It's affecting the quality of the web that you, as a user, are browsing.
> The proverbial cat is out of the bag, and you're not getting him back in.
The proposed solution is to maintain a global whitelist that each ad blocker is forced to respect.