Nuffing.com

Atom Central recently published these four unreleased videos of atomic bomb testing in 1955. The footage, taken from Operation Teapot at the test site in Nevada, is in glorious HD so it’s pretty incredible but watch out for the blinding light. Even in a small little YouTube window, it hurts.

---

SPLOID is delicious brain candy. Follow us on Facebook, Twitter, and YouTube.

via Gizmodo
Watch previously unreleased footage of 1955 atomic bomb testing in glorious HD

I love me a good breakfast burrito. They’re great for when you’re on the go, and if you’re generous with the stuffing, they can really fill you up. But if you’re like most busy American men, you just don’t have time to whip up a breakfast burrito in the mornings. Sure, you could do one […]

via The Art of Manliness
Save Time and Money With Make-Ahead Breakfast Burritos

With the release of any new operating system, you’ll always find some quirks. El Capitan is a small enough update that it doesn’t have many annoyances, but they’re still around. Here’s how to fix some of its more annoying problems.

Disable SIP to Get Your System-Level Utilities Working Again

System Integrity Protection (SIP), is a new feature in El Capitan that protects system processes and folders so even a root user cannot get access to them. This is meant to protect your system against malware and other software that could mess with your computer. As you’d expect, this takes away some of your power as a user. Subsequently, you may run into problems with some utilities working with El Capitan. One example is the original version of Bartender, which has since been updated. Similar apps that change core features in OS X have the same problem, including TotalFinder and TotalSpaces. Most apps will likely update, but if you’re a power user and you’re comfortable turning the feature off, it’s possible. We do not recommend this unless you really know what you’re doing.

1. Reboot your Mac into Recovery Mode by restarting your computer and holding down Command+R until the Apple logo appears on your screen.
2. Click Utilities > Terminal.
3. In the Terminal window, type in csrutil disable and press Enter.
4. Restart your Mac.

SIP is now disabled. You can reenable it at any by following the above instructions and substituting csrutil enable in for the Terminal command.

Reset Spotlight’s Location by Clicking and Holding the Magnifying Glass in the Top Right

This one was driving me nuts. In El Capitan, you can now move Spotlight to wherever you want, which is great, but also means it pops up wherever you left it last. If you prefer to have a little more normalcy in your life, you can send Spotlight back to its default location by clicking and holding the Spotlight icon (the magnifying glass) in the menu bar.

Get the Old Mission Control Behavior Back

Mission Control no longer groups windows together by app, which in most cases is really nice, because you get a better view of exactly what you have open. However, if you want the old behavior back, where your thumbnails are stacked, it only requires changing one setting. Open up System Preferences > Mission Control and check the box next to “Group windows by application.”

Turn Off the Mouse Wiggle

When you wiggle your mouse in El Capitan, it gets bigger so you can easily find it on the screen. This is handy if you have a big monitor, but it’s pretty silly if you have a laptop. It’s also a pain if you use photo editing tools or play games. Thankfully, it’s easy to turn off. Head to System Preferences > Accessibility > Display and uncheck the box that says “Shake mouse pointer to locate.”

Update Your Apps

With every new operating system comes the headache of updating your apps. El Capitan isn’t terribly different than Yosemite, but that doesn’t mean updating won’t cause problems. This time around, some users are reporting that Office 2016 is crashing a lot, so if you’re an Office user, you might want to hold off until a fix is in place. Otherwise, you can always check out Roaring Apps for a list of compatible software.

Image remixed from Biro Emoke.

via Lifehacker
How to Fix OS X El Capitan’s Annoyances

The chocolate bomb intended to kill Winston Churchill became the stuff of wartime legend. But depictions of the device and other cleverly concealed explosives were only recently rediscovered.

During World War II, German sabotage experts invented an array of cleverly disguised bombs. At the time, Britain’s MI5 counter-sabotage and explosives unit, B1C, contained only three people—Victor Rothschild, scientist; his secretary, Teresa Georgina Mayor, later his wife; and Donald Fish, a police detective inspector. While we like to imagine huge wartime spy-tech operations like those portrayed in Captain America, many of the tiny unit’s efforts came of their own initiative and ingenuity.

Rothschild, scion of the wealthy Rothschild family, put his vast resources to use in the service of countering sabotage. He wanted an artist to depict the boobytrapped devices that were making their way into Britain: the chocolate bar, set to explode when a piece was broken off; army food tins with secret bombs beneath the food; transformed oil cans rigged to cause destruction. Rothschild once famously disabled an explosive concealed in a shipment of onions, describing his actions on the phone the whole time, so that if the bomb went off, they would know to go in another direction next time.

For the project of documenting their efforts, Donald Fish recommended his son, a young draughtsman named Laurence Fish, who had honed his technical drawing chops on Alvis cars. There was no end of crafty devices to draw; along with assassination attempts, the Germans meant to conceal the bombs on British ships, where they would pass unnoticed until explosion. Aside from everyday items, the drawings show schematics for more complex explosives like magnetic limpet mines, which also targeted ships.

Rothschild had discovered many such traps and learned to disarm them, but he needed a record, intended to become a manual for others to recognize and neutralize the devices. He commissioned Laurence Fish via letters marked “Secret,” and the results are an incredibly detailed array of technical artwork. Fish’s attention to detail and precision drawing in a pre-computer age is incredible and, from the space of years, quite beautiful.

After the war, the drawings were thought to be lost, until the Rothschilds recently found them in “deep storage” in a chest of drawers. Victor Rothschild’s daughter Victoria sent them to Fish’s widow, Jean Bray. Bray hopes that the drawings will find a home in a museum or archive. Her favorite shows a complex, 21-day timer with a rotating disk. The BBC describes Fish’s rendering, which no doubt saved lives:

At the top, it says, in especially bold letters, “Do not unscrew here.” At the bottom, equally bold, are the words: “Unscrew here first.”

I hope the drawings find their way to a museum where they can be seen after so much time away from public appreciation. The disguised devices were ingenious, but so were the people who found, disarmed, and drew them for posterity.

[BBC]

Images: Antony Thompson/TWN

via Gizmodo
Lost for 70 Years, These Drawings Show Germany’s Sneakiest World War II Boobytraps

 Hold on to your 1.21 gigawatts. Amazon is offering the Back to the Future trilogy for free to Prime members for the whole month of October.
This year marks the 30th anniversary for BTTF. Super fans may recall October 21, 2015, is also the date Marty McFly heads into the future to see what can be done about his kids. Read More

via TechCrunch
‘Back To The Future’ Trilogy Is Free For Amazon Prime Members In October

Every year the FBI compiles the most accurate and impartial accounting of crime in the United States. The “FBI Uniform Crime Report” is available online for all to see. It gives people the opportunity to understand trends in … Read More

The post FBI: Violent Crime Continues 12 Year Downward Trend … “Gun Violence Epidemic” Debunked Again appeared first on The Truth About Guns.

via The Truth About Guns
FBI: Violent Crime Continues 12 Year Downward Trend … “Gun Violence Epidemic” Debunked Again

When changing a MySQL table or column to a new character set that uses more bytes than the old character set, you need to first check if any schema changes are needed to accomodate the change. For example, changing character sets from latin1 to utf8 is an increase from 1 to 3 bytes, and changing from utf8 to utf8mb4 is an increase from 3 to 4 bytes. The MySQL reference manual has a helpful page with some details on this, but I want to add some examples to show how this schema prep can be accomplished.
There are three different types of length limits to take into consideration:
Index
Column
Row
In this post I will focus on index length limits, and I’ll save columns and rows for future posts. Read on for details.
Index Length Limits
The specific limits depend on which MySQL version and storage engine is used, and whether innodb_large_prefix is enabled (assuming MySQL 5.5 or higher). If you want to learn from about innodb_large_prefix you may want to read this post. A common example here is an index on a varchar(255) column in the utf8 character set without innodb_large_prefix. That index uses 765+2=767 bytes, so it conforms to the 767 byte limit per column of an InnoDB index without innodb_large_prefix. If I change that column to utf8mb4 then the index requires 1022 bytes, which causes the DDL to fail.
Here’s an example:
“`
mysql> create table if not exists varchar_test (
-> id int auto_increment primary key,
-> str varchar(255)
-> ) engine = InnoDB DEFAULT CHARSET=utf8;
Query OK, 0 rows affected (0.08 sec)
mysql> alter table varchar_test add index str_index (str);
Query OK, 0 rows affected (0.15 sec)
Records: 0 Duplicates: 0 Warnings: 0
mysql> alter table varchar_test DEFAULT CHARSET=utf8mb4;
Query OK, 0 rows affected (0.02 sec)
Records: 0 Duplicates: 0 Warnings: 0
mysql> alter table varchar_test modify column str varchar(255) CHARACTER SET utf8mb4;
ERROR 1709 (HY000): Index column size too large. The maximum column size is 767 bytes.
“`
For the record, here are the index length limits I need to worry about in a character set change:
InnoDB indexes are limited to 3072 bytes
MyISAM indexes are limited to 1000 bytes
Without innodb_large_prefix, InnoDB index columns are limited to 767 bytes
In order to identify all of the indexes that I need to change, I run the following two queries on information_schema. (I tried to add the correct size for all relevant data types, but in case I forgot a data type or a new data type is added I put in a large default value to return false positives so I can go in and fix the query). These queries can be easily modified for a change to another character set such as utf8, utf16, utf32, etc.
Query #1:
“`
— Show me all index columns that will exceed the length limit if I change to utf8mb4
set @new_character_set = ‘utf8mb4’;
select table_schema, table_name, engine, index_name, column_name, column_type,
sub_part, index_column_length_in_bytes
from
(
select t.table_Schema,t.table_name,t.engine,s.index_name,c.column_name,
c.column_type,c.data_type,c.character_maximum_length,c.character_octet_length,
s.sub_part,c.character_set_name,cs.maxlen,
coalesce(
(
case
when s.sub_part is null then (cs.maxlen * c.character_maximum_length)
else (cs.maxlen * s.sub_part)
end
),
(case (c.data_type)
when ‘tinyint’ then 1
when ‘smallint’ then 2
when ‘mediumint’ then 3
when ‘int’ then 4
when ‘bigint’ then 8
when ‘decimal’ then 4
when ‘float’ then 4
when ‘year’ then 1
when ‘date’ then 3
when ‘datetime’ then 8
when ‘time’ then 3
when ‘timestamp’ then 4
else 1000000
end)) as index_column_length_in_bytes
from information_schema.statistics s
inner join information_schema.columns c on c.table_schema = s.table_schema
and c.table_name = s.table_name
and c.column_name = s.column_name
inner join information_schema.tables t on t.table_schema = c.table_schema
and t.table_name = c.table_name
inner join information_schema.character_sets cs on cs.character_set_name = @new_character_set
where s.index_type != ‘FULLTEXT’
) sub_query
where index_column_length_in_bytes > (
select case
when engine = ‘MyISAM’ then 1000
when engine = ‘InnoDB’ and (select max(innodb_large_prefix) from (
select variable_value=’ON’ as innodb_large_prefix from information_schema.global_variables where variable_name = ‘innodb_large_prefix’ union select 0 as innodb_large_prefix
) sub_query) = 1 then 3072 else 767
end
)
order by table_schema, table_name, index_name;
“`
Query #2:
“`
— show me all indexes that will exceed the length limit if I change to utf8mb4
set @new_character_set = ‘utf8mb4’;
select table_schema, table_name, engine, index_name, columns_in_index, index_length_in_bytes
from
(
select t.table_schema,t.table_name,t.engine,s.index_name,
group_concat(concat(s.column_name,
case
when s.sub_part is null
then ”
else concat(‘(‘,s.sub_part,’)’)
end
) order by s.seq_in_index) as columns_in_index,
sum(coalesce(
(
case
when s.sub_part is null
then (cs.maxlen * c.character_maximum_length)
else (cs.maxlen * s.sub_part)
end
),
(
case (c.data_type)
when ‘tinyint’ then 1
when ‘smallint’ then 2
when ‘mediumint’ then 3
when ‘int’ then 4
when ‘bigint’ then 8
when ‘decimal’ then 4
when ‘float’ then 4
when ‘year’ then 1
when ‘date’ then 3
when ‘datetime’ then 8
when ‘time’ then 3
when ‘timestamp’ then 4
else 1000000
end
)
)) as index_length_in_bytes
from information_schema.statistics s
inner join information_schema.columns c on c.table_schema = s.table_schema
and c.table_name = s.table_name
and c.column_name = s.column_name
inner join information_schema.tables t on t.table_schema = c.table_schema
and t.table_name = c.table_name
inner join information_schema.character_sets cs on cs.character_set_name = @new_character_set
where s.index_type != ‘FULLTEXT’
group by t.table_schema,t.table_name,t.engine,s.index_name
) sub_query
where index_length_in_bytes > (
select case
when engine = ‘MyISAM’ then 1000
else 3072
end
)
order by table_schema, table_name, index_name;
“`
Once I identify the affected indexes, I need to resolve each one either by shortening the sub-part of one or more columns in the index, removing columns from the index, decreasing the length of the column, or deciding not to change the character set of the relevant tables/columns.
via Planet MySQL
Prepping your MySQL indexes for a character set change