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.
51 karma · joined August 11, 2016
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.
- 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.They probably only investigate and close imposters if they receive complaints from other users.
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.
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.
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.
Do you have a way of preventing email spam and outgoing DoS attacks?
The ones that don't are most likely bots (now even that's changing thanks to projects like phantomjs).
And thanks for the downvote.
Sure, there should be regulations but it shouldn't lead to large fees and make it difficult to pay or receive payments online.
If you just mean making pages online then things are probably easier now thanks to Bootstrap and all the useful jQuery plugins.
Sadly I don't think it'd be much use for anyone since Archive.org takes care of all archiving.
The only time that I'd see screenshots come handy is for live previews.
+ it's still possible to deactivate the updates but you have to dig a little deeper to do it.
In most cases though (brace yourself for an unpopular opinion) it's enough to setup a simple dedicated server for about $20-$60 per month.
Now I did read the comments that mentioned how getting a dedicated server is a waste of valuable time, but honestly you'll most probably be able to get it setup in a day, you'll also learn how web servers work along the way and you won't have to depend on third-party cloud services (yet).
Here's a great guide from DigitalOcean on how to setup a modern dedicated HTTP server with MYSQL: https://www.digitalocean.com/community/tutorials/how-to-inst...
When they're out the hard working ones will have programming skills which will help with the job hunt.