Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Why? (Score 5, Insightful) 131

Why exactly do we feel the need place captchs in front of viewing/reading documents? Google's entire business revolves around a robot reading every webpage on the planet in order to index them. I've seen a lot of websites start using Distil recently because they don't want people scraping the content of their sites. But all this does is lead to tons of annoyances for regular users. (And as an aside, Distil is trivial to get around, and I've been paid to write scripts for a handful of different people to do so, so Distil is certainly a huge waste of money for anybody paying them).
What happened to an open web where we can all share and read content freely?

Comment Re:University of Minnesota (Score 1) 111

According to http://ark42.com/unicode/emoji... it has steam on Android 4.4's font and the free font some Linux systems might tend to use by default. It also happens to have a face and eyes on Twitter and iOS/OS X. On Windows 7+ and Android 4.1-4.3 there is neither steam nor a face though.

Comment Re:This is why calling them emoji is wrong (Score 1) 111

Emoji is a Japanese-origin word (the E is pronounced like "A"). It literally means picture character. Here is the Kanji if you're interested - https://translate.google.com/?...

Emoticon is an English word (The E is pronounced like "E") combining Emotion and Icon. It describes how we use punctuation and other regular glyphs to make pictures such as :)

Comment What versions are vulnerable? (Score 3, Insightful) 155

How do you know if your WordPress or Drupal site is vulnerable? If the version number is greater than zero of course!

Seriously. Unless all you need is a Geocities-type page with some static text and animated GIFs on the cheap, stay away from WordPress and Drupal!

Comment Re: It's not Nest, it's Google (Score 1) 268

They should have probably spun off different brands to protect the evil they did from killing off Collections in YouTube last year, or how Google My Tracks will just *stop working* for no reason after April 30 because they don't want to update it with material design. Yes, they pushed out a minor update to the widely used Android app that does nothing other than check the date and have it stop working after this month. Talk about evil.

Comment Re:alternate email address (Score 1) 108

I do this with my own domain, and I don't do it in a way that makes it obvious (such as including .facebook for facebook's email address).
I manually edit /etc/mail/virtualusertable and make a random alias and leave myself a comment about what it's for, every time I'm about to sign up for something on a new site. So far, I've had to disable aliases for Mozilla's Bugzilla, Invisible Fence, 1-800 Contacts, and Hansons, along with a few other really obscure places. The amount of spam that went to those aliases was very high, and a lot of it was Christian Newsletters. I even emailed a few of them and they replied from their personal yahoo address and *insisted* that I must have signed up on their site, because they would never send spam. So far, I have not received this phishing email, but I suspect I might not get it. My server rejects email with lower than default spamassassin scores because I can train it solely with my own personal email.

Comment Spam (Score 3, Informative) 108

Using Outlook.com for email is a bad idea. So much legitimate email is never delivered, and you won't know what you're missing. It doesn't go to spam or junk or anything. They just delete email and don't warn you. You might as well set your primary MX record to because email with outlook is about that useful.

Comment Re:Updated Policy: (Score 2) 372

95% of Han Unification doesn't seem like a problem to me. The slight stylistic differences between Chinese and Japanese where it's just a matter of "these tiny strokes point slightly left in Chinese and slightly right in Japanese" can still easily be understood no matter what font. Even slightly more stylistic differences don't actually cause any problems. For example, these two Kanji: http://jisho.org/search/%23kan... and other Kanji that have these shapes inside of them. The fonts tend to show the Chinese version: In the first, the top line is the same as the 3rd/4th, but Japanese usually write the top like a tiny dot almost, as seen in the stroke diagram graphic. In the second Kanji (scroll down), the last stroke is vertical in Chinese, but diagonal and connected differently in the Japanese version. Japanese people, in my experience, don't seem to have any problem with these kinds of differences.

Other more major differences caused by Kanji simplification over the years has also resulted in two codepoints in Unicode, so the Chinese and Japanese characters that *historically* had the same drawing, are now actually usable in either language still. For example, https://translate.google.com/?... shows the Japanese and simplified Chinese "fish". Japanese still use 4 dots on the bottom, Chinese use a line. This was given two codepoints and doesn't seem to be a problem. Many other differences were given two codepoints and Chinese fonts typically don't include any definition for the Japanese version and vice-versa.

The example I gave in my original post, about the Kanji meaning "leader" is one that really baffles me. Why was such a major difference in drawing merged into only one codepoint, and why was it never separated out into two codepoints in the next version of Unicode? There are other Kanji with major difference in appearance that share a single codepoint because of Han Unification, and these ones cause a lot of trouble. Japanese people typically don't recognize the Chinese version of "leader" as having any meaning at all. It's just scribbles to them, and when a webpage or document tries to display Japanese text but Windows or whatever decides to fall back to a Chinese font, the entire meaning is lost, because of Unicode.

Comment Re:Updated Policy: (Score 2) 372

The issue isn't how many characters exist. There is room to add more characters to Unicode when missing ones are found. The big failure of Unicode is Han Unification, which is basically like saying "Well the character A in America has the same *meaning* as the character B in Canada, so let's only issue one codepoint for A/B" and now when you type an A on your American computer, all Canadian's see a B because their fonts render the exact same character differently. This happened with many common characters that have the same *meaning* in Chinese and Japanese, but are drawn completely differently. As an example, try to copy the Kanji at http://jisho.org/search/%E5%B0... into MS Word and compare the Meiryo font vs Microsoft YaHei font.

Comment Re:Updated Policy: (Score 1) 372

Quite frankly, Unicode works well right now, provided you use UTF-8 or UTF-32. UTF-16 and surrogate pairs is really quite an ugly hack, and 16-bits are obviously not enough when we need nearly 21 bits to encode all the existing characters already. UTF-8 is quite elegant (compatible with ASCII, but easily countable and self-synchronizing) and UTF-8 can easily be extended to 31 bits, should we need more codepoints in the future. UTF-16 can't be extended in any easy way and will just become a nightmare to support, should future versions of Unicode decide to start using codepoints above U+10FFFF

Slashdot Top Deals

"Our vision is to speed up time, eventually eliminating it." -- Alex Schure