Join our Folding@Home team:
Main F@H site
Our team page
Support us: Subscribe Here
and buy SoylentNews Swag
We always have a place for talented people, visit the Get Involved section on the wiki to see how you can make SoylentNews better.
laserfusion writes:
"CNET is reporting on a massively-mono-player gaming experiment. From the article :
In what can only be described as the best thing to happen to Valentine's Day, about 12,000 people are participating in a collective game of Pokemon Red on the live game-streaming service Twitch, all by simply typing in directions in the comment box in a messy frenzy. Not every single one of the viewers is mashing in commands of course, but because anyone with a Twitch account can comment on a public stream, any viewer is a potential player in this wacky experiment.
Currently there are 80,000 players. Despite all the noise and trolls, they were able to make progress in the game and multiple goals have been achieved. Now there is a new control mode "democracy" in which the most popular commands in every 10 seconds are executed. "Democracy" and "anarchy" modes can be switched by a 75% vote."
"The Bill & Melinda Gates Foundation, the primary backer for the inBloom educational grading and service (which also acts as a platform for third-party applications), is catching flak for its role in encouraging the outsourcing of US Education. The article (cited by RMS today) argues that though the Common Core is a scary new concept that takes power away from state and local school governance, the real danger is allowing corporate enterprises to have so much control over our classrooms. The Washington Post also reports a case where Pearson included corporate logos and promotional materials inside its test booklets."
CoolHand writes:
"Sci-Tech Today talks about the role of technology in the Olympics from a unique perspective:
Every advance in the ever-accelerating juggernaut of sports technology threatens to widen the divide between Olympic haves and have-nots. Well-sponsored teams and rich governments pay top-end scientists and engineers to shape their skis, perfect their skates, tighten their suits, measure their gravitational pull.
I'm no luddite, but this seems to make these sports more about who can afford the best tech, and less about the true spirit of the games: bringing the best athletes from all countries together to compete. How can it be about the athletes, when some of the best athletes may never win due to lack of funding/tech?"
Popeidol writes:
"In November, India took the next step in their space program by launching their Mangalyaan Mars orbiter. The orbiter won't arrive for a while yet, but they've managed to get some public attention for a different reason: the fact that the entire mission costs only 75 million dollars, substantially less than the budget for the hit movie 'Gravity.'
While the question of wages is bound to come up (it was only 15% of the budget of the project), I think we can all agree that bringing down the cost of interplanetary space travel to a level attainable by the ultra-rich is a good step forward."
So, as I write this, day one has officially come to an end. I'm still somewhat in shock over it. Last night when I was editing the database to change over hostnames and such, I was thinking, man, it would be great if we got 100 regular users by tomorrow. Turns out I was wrong. By a factor of ten. Holy cow, people. I'm still in a state of disbelief, partially due to the epic turnout, but also because our very modest server hardware hasn't soiled itself from the influx (the numbers are, well, "impressive" is a way to put it). Anyway, I wanted to do a bit of a writeup of where we stand now, what works, and what doesn't. Check it out (and some raw numbers) after the break! Warning, it is a bit lengthy.
As some of you may have noticed, we've had a couple of hiccups today, but all and all, it was a huge smashing success for day one, and you, the community, made it possible. Here's our version of the good, the bad, and the ugly.
The Good!
Articles, Commenting, and User Profiles: As the basic life blood of any website, these features need to work 100%, be usable for both staff and for the community. As many are aware, we had an issue with story submission; the problem here was that Slashcode has a "Human Confirmation" module which basically went nuts after we launched. That's been fixed, and submissions should work from any user, and from ACs. As for user registration, this is working, but we've had issues with emails either getting placed into the spam bin, or dropping into the nether regions. We're still looking into this, and hope to have it addressed soon. As for user features (referred to as the Zoo in code), things like Friends/Foes/etc. are all working as expected.
Moderation: Of all the bits of Slashcode that needed tweaking, this is the only one that required a rewrite. As it's difficult to test any code that depends on a huge group of users, we went live knowing that this was going to need ongoing massaging. I won't go into the nitty-gritty here, but suffice to say we're keeping a very close eye on it. Basically, modpoints are issued if you're logged in and actively browsing on the site, and expire four hours after being issued. The UI doesn't accurately reflect this, as this change was made a couple hours ago, and the templates don't provide enough granularity to show hours vs. days. For those who are curious, I did a write up the original slash system (and why it had to go) here, and a second one going into details behind the current implementation, and the thought process that went into it here. Comments welcome.
Site Responsiveness: Appears to be good all around, despite the very modest hardware we're running on. Slash does plenty of caching with memcache, and varnish is helping loads. I don't expect any short term issues with us getting overloaded based on our current capacity and the resources we're utilizing. If there's one thing slash excels at, it is at being an incredibly scalable chunk of perl.
Development Portal: Up and running on our local FusionForge installation. Like the main site, this one also having some email issues, but we're manually approving accounts as they come in. The current latest code can be found there, as well as our bug trackers. The SSL issue is known, and we've got a proper certificate waiting to be installed. The git repository for the site is there (as well as mirrored on github) if you want to dive in. Feel free to drop in at ##altslashdot on irc.freenode.net if you have questions.
Statistics: Slash's internal stats engine is mostly working, but is slightly skewed due to Varnish. We can get realistic numbers by combining slash's numbers with those from the host itself. Needless to say, I was impressed.
The So-So!
Journals: On a technical level, these are working as best as we could expect. The problem is there's a lot of missing functionality, either in stuff that you expect to be there, and isn't, or stuff the other site has that we don't. The biggest glaring omission is the missing "Submit for Submission" button. I'm not sure if it's just not existent, or the HTML for it fell off the templates. It would not be the first feature we had to reconnect to the rest of slash. (Next/Prev article was another one). To be honest, overhauling this entire section is on my wish list, and I have some thoughts on this that I will eventually write down, discuss, and perhaps even implement.
Topics: Oh boy ... for a simple feature, this proved incredibly irritating to get to work, resulting in us hosing the site horribly for several hours. In the end, it required implementing the topics one by one in the database by hand then trying to get backslash to cooperate. This feature is somewhat over-engineered due to the fact that every article requires at least one "Topic" and a "Nexus", which is a section of the site which can exist as a subdomain. For the most part, these are implemented, but are all sharing the same icon (the art wasn't quite available by go-live). Expect to see icons sometime soon. The topics.pl page however is glitching out, for reasons I can't completely understand. For the most part, it's functional.
UTF-8: Believe it or not, we do support it (and it was pretty simple to get working, but it's not 100% bug free. This seems to be mostly related to the internal HTML validator slash uses on incoming comments, but the results are mixed based on your operating system, your browser, and the phases of the moon. If you want to see the UTF-8 in actual for yourself, check out here and here.
The Bad!
Search: Mostly hosed. The backend requires Sphinx, and possibly patching MySQL. It seems to be broken on the other site, as well, when I tested it, so at least we're not alone in this department. It does work for searching based on authors/comments by user, thus it was left in place. Just don't expect it to work for general queries right now.
The Skin: We've had ongoing CSS and theming issues since slash was installed. Considering what we had when we started, it's somewhat impressive that it's usable at all. PrestonL and many, many others on IRC contributed CSS fixes, and a proper fix for the user's page went live late today. I need to go through the logs and get an exact list of contributors so I can all give them the proper kudos and put them in the AUTHORS file.
Static HTML Pages: Slash comes with a fair number of static pages, like the About and Help pages. Most of these pages are there, but are either horribly out of date (for example, anything related to slashcode), horribly wrong (moderation), or just nonexistent. Basically, if it is documentation related to the site, the odds are that it's either 404ing or just wrong. Fixing this is mostly a matter of writing them and putting them in the correct places.
The Ugly! Welcome to the top (or perhaps bottom) issues currently plaguing the site today, those that have no easy resolution. Help is especially needed for all the below.
D2: As many people no doubt noticed, we launched with the old D1 system. While perfectly functional, it has a *very* 1997 feel to it, and there are users that do prefer the more dynamic D2 system. This wasn't some conspiracy to launch an entirely Web 1.0 website (which happens to mostly work with NCSA Mosaic), but due to the fact that most of it is missing. We have the actual code and backend stuff, but none of the javascript that makes it work. Furthermore, even if we did, it would be the rather ugly version that had the "floating box of doom" (since that code is from that era). The switch in the UI creeped back in after go-live, but functionally it might as well not be there. I'd like to give the D1 system a SLIGHT facelift (similar to the old Greasemonkey script for Slashdot), yet make sure this site always works correctly. Ideas and volunteers welcome.
Firehose: It's essentially the same story as D2, except I'm not even sure that all the backend code is there for it. If we want it, it's basically a burn and rewrite.
Tags: Unlike the other two, we've got most of bits for them. They're just not exposed anywhere on the skin. It's probably possible to bring them back if the community feels that they add value, but it will require someone who knows HTML, javascript, and Template::Toolkit to do it.
Meta-moderation: This is a case where the implementation itself is questionable. We've got all the code for this, but it's broken. When the other site rolled out firehose, they broke this. It appears all the logic is in place, it just needs minor brain surgery. The problem is, the old moderation system was built on a fundamentally wrong premise that got lucky, and I'm honestly not sure many people ever metamodded in anything approaching significant value. This entire feature needs a rethink in light of the moderation rework.
Theming Engine: Slash's theme engine is an example of evolution, not of intelligent design. Basically, if we want multiple themes, it requires multiple Apache instances, running different vhosts for different Nexuses. If I lost you, the take away is its pretty damn ugly. Its not unsalvagable, most of the themed bits live in the database, and it might be possible to make themes user-selectable (it appears some work was done to implement this in slash before being abandoned).
Backslash: Most of you are probably "WTF is backslash." It's slash's version of an admin panel, and it was clearly never designed for mere mortals. We've smacked most of the bugs out of it, but it remains somewhat awkward to use, and for suadmins, it is possible to actually break the site with a misclick (we've already done it and put slashd in an infinite loop). For the most part, the story editors is "relatively" usable, and I finally smote the long standing 500 error. For end users, the biggest thing on this to know is that the two-man system isn't enforced. Articles will be flagged yellow or red (depending on the author) on the master list, but nothing actually prevents those from going live. Furthermore, there's very little in terms of sanity checking, and it's far too easy to accidentally publish something. I just ask the community bears with us as we fight our backend tools.
Mod_perl: And we get to the 600-pound gorilla in the corner. Slash is tied to mod_perl 1.3 and mod_perl is tied to Apache 1.3. If you know Apache, you can guess the problem. If not, it's basically summed up as this: 1.3 is EOL, and has been for some time. There are no "known" CVEs, which helps, but I think everyone wants us to get to supported server software ASAP. This is compounded by the fact that mod_perl development appears to have ceased, and no version exists thats compatible with Apache 2.4. While not an IMMEDIATE problem, it's something we need to figure out for longer term plans for. There's been talk on going to FastCGI or a similar solution, but no definite long term plans have been made. At least one serious effort was historically made to try and update the codebase to 2.0, and MOST of the Apache binder stuff is relatively self-contained. At least we're not alone on this, the few slashcode sites that we're aware of (aside from the other site, which Netcraft reports running Apache 2.2) are still running 1.3.
Final Remarks, and Server Information, and Day 1 Stats
Wooo, still with me? Good. The long and short of it is we're doing pretty well overall, but there's a lot of work that still needs doing. If you want to jump in, grab the code and join us on IRC, all contributions are welcome. After this post goes live, I'm going on a hiatus to try and get my life/work balance back in order. I hope to return in a week or two to help the dev team digging. As always, I'll be available on IRC should something (like the mod script) needs my attention.
A couple^Wsome^Wlot of people have been asking about the server hardware, who is UID #1 (Anonymous Coward), and what the day one counts were. I'm pleased to announce that we are hosted on Linode, specifically, two Linode 2048s running Ubuntu 12.04 LTS. Average server load during day 1 was between 10-20% percent, spiking occasionally when we had to flush caches out for config changes.
In the last 24 hours, we used over 7 GiB(!) of bandwidth, served to 3630 distinct IP addresses. As of midnight tonight EST, the daily stats email dropped out of slashd, so I'm going to repost most of it here. Please note the bandwidth stats from slash are skewed as it is behind Varnish. For the most part, only the actual HTML of a given page is uncached for logged in users. Enjoy.
SoylentNews Stats for 2014-02-17 UIDs IPIDs Pages total: - - 76164 (2123.8 MB) static total: - - 5722 gstatic total: - - 7827 grand total: 916 3630 78372 (2140.9 MB) secure total: - - 0 total hits: 103059 posts: 267 333 comments: 607 1502 17478 (412.1 MB) index: 868 1818 14931 articles: 738 2298 12508 (573.6 MB) search: 224 568 1841 (31.4 MB) journals: 276 394 1572 (25.2 MB) users: 652 812 5390 (105.0 MB) rss: 55 172 2208 (17.1 MB) other: 43 52 2086 (37.0 MB) formkeys: 1732 rows total comments: 837 posted yesterday submissions: 28 submissions sub/comments: 82.1% of the submissions came from comment posters from this day ------------------------ Yesterday | 2 days ago | 3 days ago Avg Hits Per Article: 962.2| 168.4| 0.0 Avg Comments Per Article: 58.0| 16.4| 6.2 Pages From RSS By Section ------------------------------------------------ Section Pages UIDS IPIDS Main Page 524 36 169 For Main Page Pages IPs Bandwidth Users total: 76164 3600 2123.8 MB 916 index: 14931 1818 644.1 MB 868 comments: 17478 1502 412.1 MB 607 articles: 12508 2298 573.6 MB 738 search: 1841 568 31.4 MB 224 rss: 2208 172 17.1 MB 55 other: 2086 52 37.0 MB 916 ----------------------- Top stories viewed by article.pl: 1885 14/02/17/0148235 Dopefish Welcome to the World of Tomorr 865 14/02/17/1745207 mattie_p What "News for Nerds" Sites Sh 725 14/02/17/0745210 Dopefish Environmentalists Concerned Ab 613 14/02/16/2220240 NCommander Announcing UTF-8 Support on So 608 14/02/16/1331209 NCommander Massive Site Progress - Status 560 14/02/17/145204 LaminatorX Australia spied on US law firm 531 14/02/17/0818240 Dopefish MIT Students Subpoenaed Over T 514 14/02/17/1453216 LaminatorX Find those bugs! 510 14/02/16/2318242 Dopefish AIDS Deniers Use Bogus Copyrig 413 14/02/17/0814201 Dopefish Wondering Where Microsoft Bing 393 14/02/16/0731223 mattie_p Global Warming Finally Debunke 385 14/02/17/180204 Cactus Desalination Project in Califo 292 14/02/17/1734251 mattie_p Coal Mine Fire Threatens Power 292 14/02/16/237205 Dopefish CD Projekt RED Considering The 277 14/02/12/0715245 NCommander Welcome to SoylentNews! 268 14/02/16/0327202 Cactus Kickstarter Hacked 257 14/02/17/1630228 mattie_p 3D Printers for Kids 210 14/02/13/0412219 NCommander Reworking Moderation Access 182 14/02/16/2059230 mattie_p Amazon Electric Fish Inspire U 176 14/02/15/189225 mattie_p Tuna Hearts Damaged by Oil Pol 175 14/02/16/217209 Dopefish How Facebook Can Be Addictive 172 14/02/14/201241 mattie_p Google Buys Lease On NASA's Fa 170 14/02/16/2032248 mattie_p China Plans World's Longest Tu 167 14/02/16/1115247 Dopefish PPACA/Obamacare Website Develo 160 14/02/16/2119211 Dopefish Germany Beefing Up Spy Defense ----------------------- Hour Hits Hits/sec 00 1027 0.29 ######## 01 1144 0.32 ######### 02 1282 0.36 ########## 03 1171 0.33 ######### 04 726 0.20 ###### 05 2891 0.80 ######################## 06 4595 1.28 ###################################### 07 3356 0.93 ############################ 08 3377 0.94 ############################ 09 2940 0.82 ######################## 10 2895 0.80 ######################## 11 2991 0.83 ######################### 12 3622 1.01 ############################## 13 3992 1.11 ################################# 14 3896 1.08 ################################ 15 3853 1.07 ################################ 16 4019 1.12 ################################# 17 4110 1.14 ################################## 18 3881 1.08 ################################ 19 4504 1.25 ##################################### 20 4558 1.27 ###################################### 21 4685 1.30 ####################################### 22 4112 1.14 ################################## 23 4745 1.32 ########################################
aliks writes:
"The practical applications of quantum encryption may be getting closer. A paper published in Physical Review Letters by Vedran Dunjko, Petros Wallden, and Erika Andersson presents a way to use Quantum Digital Signatures without requiring long term quantum memory.
Phys.org
provides a summary:
Quantum digital signatures (QDSs) allow the sending of messages from one sender to multiple recipients, with the guarantee that messages cannot be forged or tampered with. Additionally, messages cannot be repudiated; if one recipient accepts a message, she is guaranteed that others will accept the same message as well. While messaging with these types of security guarantees are routinely performed in the modern digital world, current technologies only offer security under computational assumptions. QDSs, on the other hand, offer security guaranteed by quantum mechanics. All of the variants of QDSs proposed thus far require long-term, high quality quantum memory, making them unfeasible in the foreseeable future. Here, we present a QDS scheme where no quantum memory is required, which also needs just linear optics. This makes QDSs feasible with current technology."
[Ed. Note] The Physical Review Letters link has all the fun details, but Phys.org provides a more understandable article for the layperson.
combatserver writes:
"While The Guardian and The New York Times reported on the NSA targeting of data leaked by popular mobile apps, independent sources produced highly-detailed articles--accompanied by source material--that paint a much broader picture of NSA capabilities and intent. Recent restrictions imposed on journalists--a result of corporate influence, editorial decisions, and threats against journalists--combined with the ease of establishing a website, might be driving a new era in journalism.
The Intercept recently announced a shift towards independent reporting with the creation of their own news outlet, free of the constraints imposed on journalists by 'Big Media' and governments. Glenn Greenwald, Laura Poitras and Jeremy Scahill have joined forces to provide the world with an alternative, perhaps blazing a path towards a fundamental change in how news is reported and distributed. SoylentNews can play a significant role in this shift towards journalistic freedom--we share many common core-ideals, and can give voice to independent news sources.
The Big Question: How will 'Big Media' and governments react to this shift in journalism?"
Papas Fritas writes:
"Michael Kitchen at Marketwatch reports that when companies in the US are hacked for customer information they often seem to react to such thefts with little more than a sigh and a shrug if they even report it at all. But in South Korea, they don't mess around with ID theft.
South Korea's financial-services regulator announced Sunday that three firms which suffered the theft of consumers' data last year would be barred from issuing any new credit cards or extending any loans for three months. In addition, the executives at the companies involved showed their contrition by going before television cameras and making deep bows and personal apologies. Some executives reportedly resigned over the incident, even though the alleged ID thieves were caught and arrested. The South Korean Financial Supervisory Commission (FSC) said the companies had 'neglected their legal duties of preventing any leakage of customer information.'"
ticho writes:
"For the first time, a team of chemists and engineers at Penn State University have placed tiny synthetic motors inside live human cells, propelled them with ultrasonic waves, and steered them magnetically. It's not exactly 'Fantastic Voyage', but it's close. The nanomotors, which are rocket-shaped metal particles, move around inside the cells, spinning and battering against the cell membrane.
'As these nanomotors move around and bump into structures inside the cells, the live cells show internal mechanical responses that no one has seen before,' said Tom Mallouk, Evan Pugh Professor of Materials Chemistry and Physics at Penn State. 'This research is a vivid demonstration that it may be possible to use synthetic nanomotors to study cell biology in new ways. We might be able to use nanomotors to treat cancer and other diseases by mechanically manipulating cells from the inside. Nanomotors could perform intracellular surgery and deliver drugs non-invasively to living tissues.'"
Lagg writes:
"We're in a climate where it's easy to accuse a company of spying on you by various means with a distinct possibility that you could be right, but sometimes a reality check is needed. A Reddit user recently posted a thread accusing Valve of writing code for VAC that iterates your DNS cache and sends the hashed entries to their server. The proof provided of this was a prettied disassembly (that was not easily reproducible due to how VAC loads symbols) that showed only that VAC was indeed iterating the DNS cache, which any knowledgeable programmer understands is not exactly an uncommon thing to do, as no socket code was to be seen. Today, Gabe Newell responded to these allegations by confirming that no they do not in fact snoop your cache entries.
There are probably a few things to learn from this, including not trusting a screenshot of code that looks complex without actually understanding what it's doing. A lack of any level-headed investigation is a bad idea and it's important to handle these situations before they snowball into a mob (as Redditors are bound to do)."
nobbis writes "Java 8 Early Access Release Candidate Available. Early Access Release Candidate 2 was made available for download last week. Lambda Functions and a new Date Time API are major features of Java 8, with some lesser known performance enhancements, which are discussed by Drew Stephens in his blog Atomic Number Implementation. Oracle's head Java Evangelist Simon Ritter gives a run through of new features in this presentation to the Virtual Java User Group. Project Jigsaw has been delayed again and is now scheduled for release with Java 9."
The bug report looks healthy and Java 8 is due for release on March 17th -- St. Patrick's Day.
An anonymous coward writes:
"In March, 2013 Tim Berners-Lee, the inventor of the World Wide Web, proposed adopting DRM into the HTML standard, under the name Encrypted Media Extensions (EME). Writing in October 2013, he said that "none of us as users like certain forms of content protection such as DRM at all," but cites the argument that "if content protection of some kind has to be used for videos, it is better for it to be discussed in the open at W3C" as a reason for considering the inclusion of DRM in HTML.
The Electronic Frontier Foundation has objected, saying in May of last year that the plan 'defines a new "black box" for the entertainment industry, fenced off from control by the browser and end-user'. Later, they pointed out that if DRM is OK for video content, that same principle would open the door to font, web applications, and other data being locked away from users.
public-restrictedmedia, the mailing list where the issue is being debated, has seen discussion about forking HTML and establishing a new standard outside of the W3C."
Earlier this month, a Tesla parked in a Toronto garage caught fire. This does not seem to be charger related, as the Model S was not plugged in to a charger at the time. While Tesla fires have been in the news lately, this one was unique in that there was no collision involved.
Tesla said it has definitively determined that the Toronto fire did not originate in the battery, the charging system, the adapter or the electrical receptacle, noting that these components were untouched by the fire.
Google acquires SlickLogin: dogs go wild!
SlickLogin, an Israeli start-up, is behind the technology that allows websites to verify a user's identity by using sound waves. It works by playing a uniquely generated, nearly-silent sound through your computer speakers, which is picked up by an app on your smartphone. The app analyses the sound and sends a signal back to confirm your identity.
The firm confirmed the acquisition on its website but did not provide any financial details of the deal.
Too bad they don't still put whistles inside packages of Cap'n Crunch cereal!
Hey, just a heads up on our Day 1 status. I've made some tweaks to the moderation script to handle the surge of users we've gotten, so modpoints should start flowing more easily. I'm making a few more tweaks right now that should get this working as expected (I am going to have to purge out the point in system to reset the script though, so if you have modpoints right now, don't be surprised if they suddenly vanish into the ether.
We know there have been some issues with both registration and submitting stories. On the registration front, some of our emails have been marked as spam, so if you're not getting them, check spam filters. In addition, for the last half an hour, we had a problem with a human confirmation check breaking, which just got cleared. We'll keep you apprised of any updates to this. As for story submissions, this looks like an artifact of a human confirmation script that got re-enabled when we went live. It should be working properly now for logged in users, as well as AC, though I'll be keeping an eye on it. I hope to have a more verbose tech write-up of the site sometime tonight.