You are here

Agreguesi i feed

next-20140826: linux-next

Kernel Linux - Mar, 26/08/2014 - 9:23pd
Version:next-20140826 (linux-next) Released:2014-08-26
Kategoritë: Kernel Linux

Early Bitcoin User Interviewed By Federal Officers

Slashdot.org - Mar, 26/08/2014 - 9:18pd
MrBingoBoingo (3481277) writes Recently a Bitcoin user reports being interviewed over their past use of a now defuct exchange service by agents from the FBI and Treasury Department. This encounter raises concerns that earlier Bitcoin users who entered the space inocuously and without ties to Dark Markets or The Silk Road might need to prepare for Law Enforcement questioning about their early Bitcoin related activities.

Read more of this story at Slashdot.








Xavier Claessens: OpenGlucose: continued

Planet GNOME - Mar, 26/08/2014 - 7:08pd

I started working on the UI to display the results:

It is made using a GtkApplicationWindow containing a WebkitWebView, the content is made with HTML/CSS/JS with jquery and the chart is made using jqplot.

To make testing easier, I also added a dummy device that has random data, it can be enabled by setting OPENGLUCOSE_DUMMY_DEVICE=1 in your env.

A lot more work is needed, but that’s a start.

Predictive Modeling To Increase Responsivity of Streamed Games

Slashdot.org - Mar, 26/08/2014 - 5:54pd
jones_supa (887896) writes Streaming game services always bump up against a hard latency limit based on the total round-trip time it takes to send user input to a remote server and receive a frame of game data from that server. To alleviate the situation, Microsoft Research has been developing a system called DeLorean (whitepaper) using predictive modeling to improve the experienced responsiveness of a game. By analyzing previous inputs in a Markov chain, DeLorean tries to predict the most likely choices for the user's next input and then generates speculative frames that fit those inputs and sends them back to the user. The caveat is that sending those extra predictive frames and information does add a bandwidth overhead of anywhere from 1.5 to 4 times that of a normal streaming game client. During testing the benefits were apparent, though. Even when the actual round-trip time between input and server response was 256 ms, double-blind testers reported both the gameplay responsiveness and graphical quality of the DeLorean system were comparable to a locally played version of the game.

Read more of this story at Slashdot.








Why Do Humans Grow Up So Slowly? Blame the Brain

Slashdot.org - Mar, 26/08/2014 - 4:03pd
sciencehabit (1205606) writes Humans are late bloomers when compared with other primates — they spend almost twice as long in childhood and adolescence as chimps, gibbons, or macaques do. But why? One widely accepted but hard-to-test theory is that children's brains consume so much energy that they divert glucose from the rest of the body, slowing growth. Now, a clever study of glucose uptake and body growth in children confirms this 'expensive tissue' hypothesis.

Read more of this story at Slashdot.








Federico Mena-Quintero: Mon 2014/Aug/25

Planet GNOME - Mar, 26/08/2014 - 3:37pd
  • The Safety and Privacy team

    During GUADEC we had a Birds-of-a-feather session (BoF) for what eventually became the Safety Team. In this post I'll summarize the very raw minutes of the BoF.

    What is safety in the context of GNOME?

    Matthew Garrett's excellent keynote at GUADEC made a point that GNOME should be the desktop that takes care of and respects the user, as opposed to being just a vehicle for selling stuff (apps, subscriptions) to them.

    I'll digress for a bit to give you an example of "taking care and respecting the user" in another context, which will later let me frame this for GNOME.

    Safety in cities

    In urbanism circles, there is a big focus on making streets safe for everyone, safe for all the users of the street. "Safe" here means many things:

    • Reducing the number of fatalities due to traffic accidents.
    • Reducing the number of accidents, even if they are non-fatal, because they waste everyone's time.
    • Making it possible for vulnerable people to use the streets: children, handicapped people, the elderly.
    • Reducing muggings and crime on the streets.
    • Reducing the bad health effects of a car-centric culture, where people can't walk to places they want to be.

    It turns out that focusing on safety automatically gives you many desirable properties in cities — better urbanism, not just a dry measure of "streets with few accidents".

    There is a big correlation between the speed of vehicles and the proportion of fatal accidents. Cities that reduce maximum speeds in heavily-congested areas will get fewer fatal accidents, and fewer accidents in general — the term that urbanists like to use is "traffic calming". In Strasbourg you may have noticed the signs that mark the central island as a "Zone 30", where 30 Km/h is the maximum speed for all vehicles. This lets motor vehicles, bicycles, and pedestrians share the same space safely.

    Along with traffic calming, you can help vulnerable people in other ways. You can put ramps on curbs where you cross the street; this helps people on wheelchairs, people carrying children on strollers, people dragging suitcases with wheels, skaters, cyclists. On sidewalks you can put tactile paving — tiles with special reliefs so blind pedestrians can feel where the "walking path" is, or where the sidewalk is about to end, or where there is a street crossing. You can make traffic lights for pedestrians emit a special sound when it is people's turn to cross the street — this helps the blind as well as those who are paying attention to their cell phone instead of the traffic signals. You can make mass transit accessible to wheelchairs.

    Once you have slow traffic, accessible mass transit, and comfortable/usable sidewalks, you get more pedestrians. This leads to more people going into shops. This improves the local economy, and reduces the amount of money and time that people are forced to waste in cars.

    Once you have people in shops, restaurants, or cafes at most times of the day, you get fewer muggings — what Jane Jacobs would call "eyes on the street".

    Once people can walk and bike safely to places they actually want to go (the supermarket, the bakery, a cafe or a restaurant, a bank), they automatically get a little exercise, which improves their health, as opposed to sitting in a car for a large part of the day.

    Etcetera. Safety is a systemic thing; it is not something you get by doing one single thing. Not only do you get safer streets; you also get cities that are more livable and human-scaled, rather than machine-scaled for motor vehicles.

    And this brings us to GNOME.

    Safety in GNOME

    "Computer security" is not very popular among non-technical users, and for good reasons. People have friction with sysadmins or constrained systems that don't let them install programs without going through bureaucratic little processes. People get asked for passwords for silly reasons, like plugging a printer to their home computer. People get asked questions like "Do you want to let $program do $thing?" all the time.

    A lot of "computer security" is done from the viewpoint of the developers and the administrators. Let's keep the users from screwing up our precious system. Let's disallow people from doing things by default. Let's keep control for ourselves.

    Of course, there is also a lot of "computer security" that is desirable. Let's put a firewall so that vandals can't pwn your machine, and so that criminals don't turn your computer into a botnet's slave. Let's keep rogue applications (or rogue users) from screwing up the core of the system. Let's authenticate users so a criminal can't access your bank account.

    Security is putting an armed guard at the entrance of a bank; safety is having enough people in the streets at all times of the day so you don't need the police most of the time.

    Security is putting iron bars in low-storey windows so robbers can't get in easily; safety is putting iron railings in high-storey balconies so you don't fall over.

    Security is disallowing end-user programs from reading /etc/shadow so they can't crack your login passwords; safety is not letting a keylogger run while the system is asking you for your password. Okay, it's security as well, but you get the idea.

    Safety is doing things that prevent harm to users.

    Encrypt all the things

    A good chunk of the discussion during the meeting at GUADEC was about existing things that make our users unsafe, or that inadvertently reveal user's information. For example, we have some things that don't use SSL/TLS by default. Gnome-weather fetches the weather information over unencrypted HTTP. This lets snoopers figure out your current location, or your planned future locations, or the locations where people related to you might live. (And in more general terms, the weather forecasts you check are nobody's business but yours.)

    Gnome-music similarly fetches music metadata over an unencrypted channel. In the best case it lets a snooper know your taste in music; in the worst case it lets someone correlate your music downloads with your music purchases — the difference is a liability to you.

    Gnome-maps fetches map tile data over an unencrypted connection. This identifies places you may intend to travel; it may also reveal your location.

    But I don't have a nation-state adversary

    While the examples above may seem far-fetched, they go back to one of the biggest problems with the Internet: unencrypted content is being used against people. You may not have someone to hide from, but you wouldn't want to be put in an uncomfortable situation just from using your software.

    You may not be a reckless driver, but you still put on seatbelts (and you would probably not buy a car without seatbelts).

    We are not trying to re-create Tails, the distro that tries to maintain your anonymity online, but we certainly don't want to make things easy for the bad guys.

    During the meeting we agreed to reach out to the Tails / Tor people so that they can tell us where people's identifying information may leak inadvertently; if we can fix these things without a specialized version of the software, everyone will be safer by default.

    Sandbox all the things

    While auditing code, or changing code to use encrypted connections, can be ongoing "everyday" work, there's a more interesting part to all of this. We are moving to sandboxed applications, where running programs cannot affect each other, or where an installed program doesn't affect the installed dependencies for other programs, or where programs don't have access to all your data by default. See Allan Day's posts on sandboxed apps for a much more detailed explanation of how this will work (parts one and two).

    We have to start defining the service APIs that will let us keep applications isolated from the user's personal data, that is, to avoid letting programs read all of your home directory by default.

    Some services will also need to do scrubbing of sensitive data. For example, if you want to upload photos somewhere public, you may want the software to strip away the geolocation information, the face-recognition data, and the EXIF data that reveals what kind of expensive camera you have. Regular users are generally not aware that this information exists; we can keep them safer by asking for their consent before publishing that information.

    Consent, agency, respect

    A lot of uncomfortable, inconvenient, or unsafe software is like that because it doesn't respect you.

    Siloed software that doesn't let you export your data? It denies you your agency to move your data to other software.

    Software that fingerprints you and sends your information to a vendor? It doesn't give you informed consent. Or as part of coercion culture, it sneakily buries that consent in something like, "by using this software, you agree to the Terms of Service" (terms which no one ever bothers to read, because frankly they are illegible).

    Software that sends your contact list to the vendor so it can spam them? This is plain lack of respect, lack of consent, and more coercion, as those people don't want to be spammed in the first place (and you don't want to be the indirect cause).

    Allan's second post has a key insight:

    [...] the primary purpose of posing a security question is to ascertain that a piece of software is doing what the user wants it to do, and often, you can verify this without the user even realising that they are being asked a question for security purposes.

    We can take this principle even further. The moment when you ask a security question can be an opportunity to present useful informations or controls – these moments can become a valuable, useful, and even enjoyable part of the experience.

    In a way, enforcing the service APIs upon applications is a way of ensuring that they ask for your consent to do things, and that they respect your agency in doing things which naive security-minded software may disallow "for security reasons".

    Here is an example:

    Agency: "I want to upload a photo"
    Safety: "I don't want my privacy violated"
    Consent: "Would you like to share geographical information, camera information, tags?"

    Pattern Language

    We can get very interesting things if we distill these ideas into GNOME's Pattern Language.

    Assume we had patterns for Respect the user's agency, for Obtain the user's consent, for Maintain the user's safety, and for Respect the user's privacy. These are not written yet, but they will be, shortly.

    We already have prototypal patterns called Support the free ecosystem and User data manifesto.

    Pattern languages start being really useful when you have a rich set of connections between the patterns. In the example above about sharing a photo, we employ the consent, privacy, and agency patterns. What if we add Support the free ecosystem to the mix? Then the user interface to "paste a photo into your instant-messaging client" may look like this:

    Note the defaults:

    • Off for sharing metadata which you may not want to reveal by default: geographical information, face recognition info, camera information, tags. This is the Respect the user's privacy pattern in action.

    • On for sharing the license information, and to let you pick a license right there. This is the Support the free ecosystem pattern.

    If you dismiss the dialog box with "Insert photos", then GNOME would do two things: 1) scrub the JPEG files so they don't contain metadata which you didn't choose to share; 2) note in the JPEG metadata which license you chose.

    In this case, Empathy would not communicate with Shotwell directly — applications are isolated. Instead, Empathy would make use of the "get photos" service API, which would bring up that dialog, and which would automatically run the metadata scrubber.

    Resources

Federico Mena-Quintero: Sun 2014/Jul/27

Planet GNOME - Mar, 26/08/2014 - 3:37pd

Magdalen Berns: REMINDER: GNOME Shell Magnification Feedback Survey 2014

Planet GNOME - Mar, 26/08/2014 - 3:05pd
Wee reminder of the GNOME Shell Magnification feedback survey. So far there have been 8 respondents which is great but it would be even greater to have some more! So far the survey result seems to suggest that slow performance and degraded graphics are a problem for users... But don't take my word for it: try it out, see what you think and feedback with your verdict if you will! Results will be published soon.
BackgroundThe GNOME Shell Magnifier was first authored in a commit by Colin Walters in 2010, since its birth it's benefited from several contributions made by various developers so to alleviate any confusion there may be about the Magnifiers roots, the complete Magnifier git log is as follows.

2014-06-24js: Adapt to GSettings API changeJasper St. Pierre1-2/+22014-02-13Magnifier: clip the UI group clone to the allocationGiovanni Campagna1-1/+22014-02-13Magnifier: use the system noise texture for the dead areaGiovanni Campagna1-0/+42014-02-13Magnifier: don't listen for focus/tracker events if the magnifier is not activeGiovanni Campagna1-6/+232014-02-13Magnifier: demote exceptions reading focus/caret positionGiovanni Campagna1-2/+162014-02-13Magnifier: fix a warning when calling setActive() with the same valueGiovanni Campagna1-7/+102014-02-08Magnifier: Restore crosshairsMagdalen Berns1-75/+562014-02-05Magnifier: take x,y from center of focused widgetMagdalen Berns1-1/+22014-02-04Magnifier: Disable unredirect when activeMagdalen Berns1-2/+62013-09-13Magnifier: don't initialize if we don't need itGiovanni Campagna1-59/+802013-09-12ShellGlobal: use MetaCursorTracker to query the pointer positionGiovanni Campagna1-3/+32013-09-07Remove unused functionsMagdalen Berns1-80/+02013-09-05Magnifier: Implement focus and caret trackingMagdalen Berns1-20/+1352013-08-19Replace ShellXFixesCursor with MetaCursorTrackerGiovanni Campagna1-10/+102012-08-31magnifier: Don't use some deprecated APIsJasper St. Pierre1-14/+152012-08-31magnifier: Don't set the size of the uiGroupJasper St. Pierre1-2/+02012-08-31magnifier: Round the uiGroup to integer positionsJasper St. Pierre1-1/+12012-08-31magnifier: Use PointerWatcher to poll the mouse pointerJasper St. Pierre1-9/+62012-08-31js: Fix up for Clutter.Color changesJasper St. Pierre1-5/+22012-08-06magnifier: Using properly 'color-saturation'Alejandro Piñeiro1-5/+52012-08-06magnifier: 'color-saturation' is a double not a booleanAlejandro Piñeiro1-1/+12012-07-13magnifier: Fix grayscale effectFlorian Müllner1-0/+12012-07-09magnifier: fix a copy/paste typoCosimo Cecchi1-1/+12012-07-06Add a grayscale effectJasper St. Pierre1-0/+492012-05-16Magnifier: Add brightness and contrast functionalityJoseph Scheuhammer1-0/+612012-05-16Magnifier: Add brightness and contrast functionalityJoseph Scheuhammer1-1/+2322012-05-02Refactor show()/hide() sequencesJasper St. Pierre1-4/+12012-01-26magnifier: Handle screen size changesRui Matos1-4/+332011-12-15Do not use the default stageJasper St. Pierre1-1/+12011-11-24Port everything to class frameworkGiovanni Campagna1-15/+92011-11-04magnifier: Use enum from gsettings-desktop-schemasFlorian Müllner1-37/+232011-10-11*.js: Make emacs modelines consistentDan Winship1-1/+12011-02-17magnifier: Adjust for removal of 'show-magnifier' keyFlorian Müllner1-6/+102011-02-13magnifier: crosshairs opacity is now a doubleBastien Nocera1-7/+72011-02-11Move magnifier schemas to gsettings-desktop-schemasThomas Wood1-1/+12010-12-03magnifier: Fix DND when the magnifier is activeFlorian Müllner1-0/+32010-12-03Fix redundant calls to global.get_pointer()Owen W. Taylor1-23/+192010-12-03Improve the algorithm for proportional mouse trackingOwen W. Taylor1-4/+92010-12-03Refactor Magnifier.ZoomRegion to avoid permanent Clutter.CloneOwen W. Taylor1-346/+3362010-11-01magnifier: Sync MouseTrackingMode values with the gsettings enumFlorian Müllner1-3/+32010-09-16Add Universal Access status indicatorGiovanni Campagna1-0/+62010-09-10Bug 622414 - Port magnifier to GSettingsMilan Bouchet-Valat1-151/+992010-07-18Clean up unused includesFlorian Müllner1-3/+02010-06-25Missed some 'Shell.GConf' references in switch to GSettings.Joseph Scheuhammer1-12/+122010-06-18Migrate to GSettingsMilan Bouchet-Valat1-25/+262010-05-19minor js cleanupsDan Winship1-3/+32010-05-17magnifier: use global.get_pointer instead of gdk_window_get_pointerDan Winship1-10/+52010-05-13Don't use double quotes for things that don't need to be translatedMarina Zhurakhinskaya1-17/+172010-05-11Add missing magnifier files from the last commitColin Walters1-0/+1484
The magnifier could do with some work. It currently has 17 unresolved issues in Bugzilla which are as follows

618397norNorLinugnome-shellUNCO20Hz polling when magnifier is enabled646942norNorLinugnome-shellUNCOdesktop zoom has some oddities in multi-head mode649535majNorLinugnome-shellUNCOMagnifier turns the screen blue when notifications are received in the message tray666612minNorLinugnome-shellUNCOWallpaper is visible with magnifier when modal dialog is attached to a maximized window669192minNorLinugnome-shellUNCOD-Bus: org.gnome.Magnifier.setActive incomplete.672325norNorLinugnome-shellUNCOMagnifier freezes shell when activities screen invoked708985norNorLinugnome-shellUNCOMouspointer disappears in Fullscreengames with magnifier enabled710191norNorLinugnome-shellUNCOMagnifier: Taking a screenshot crashes gnome-shell710194norNorLinugnome-shellUNCOMagnifier: View is poor quality because the image is not scaled710470criNorLinugnome-shellUNCOWayland: Reliable crash when typing in a text view with the magnifier enabled720714norNorLinugnome-shellUNCOMagnifier: Focus Tracking should only track the Active Window when gnome-terminal is running in background720715norNorLinugnome-shellUNCOMagnifier: Focus Tracking flipps on left screen edge in some cases720716norNorLinugnome-shellUNCOMagnifier: Focus Tracking should focus "objects" more complete720723norNorLinugnome-shellUNCOMagnifier: Focus Tracking should jump more smooth to the next focus point.725129norNorLinugnome-shellUNCO[RFE] Move the magnified screen area with a keyboard shortcut728848criNorLinugnome-shellUNCOSwitching the magnifier on makes Gnome-shell so unstable that it is impossible to switch it off.633573norNorLinugnome-shellNEWMagnifier should turn off when screen blanked

If you like my work as a volunteer contributor to GNOME and past Google Summer of Code (GSoC) student to GNOME and Scientific Ruby, then please consider helping me meet the cost of my trip to the GSoC Mentor Summit in San Jose this October in support of my contributions to FOSS by donating using the link below.



Linux 3.17-rc2 Release Marks 23 Years of the Linux Kernel

Slashdot.org - Mar, 26/08/2014 - 2:01pd
An anonymous reader writes Linus Torvalds released Linux 3.17-rc2 today in commemoration of the 23rd anniversary of the original kernel announcement. It was on 25 August 1991 that he announced his new OS project to the Minix users list.

Read more of this story at Slashdot.








Lubuntu Blog: LXPanel 0.7.0 released

Planet UBUNTU - Mar, 26/08/2014 - 1:39pd
A huge update to the GTK+ panel was released. See the list below for some changes. Full log of changes can be fund in git. Lots of new functionalities like:

  • new plugin ‘launchtaskbar’ combining ‘launchbar’ and ‘taskbar’
  • replaced ‘pager’ plugin with former ‘wnckpager’ one
  • allowed drag applications from system menu plugin
  • using human readable sensor names if available (like ‘Core 0′, etc)
  • renamed button to configure plugin from ‘Edit’ to ‘Properties’
  • etc.

Soon in Lubuntu repositories. More info here.

Via LXDE Blog

850 Billion NSA Surveillance Records Searchable By Domestic Law Enforcement

Slashdot.org - Mar, 26/08/2014 - 1:15pd
onproton (3434437) writes The Intercept reported today on classified documents revealing that the NSA has built its own "Google-like" search engine to provide over 850 billion collected records directly to law enforcement agencies, including the FBI and the DEA. Reporter Ryan Gallagher explains, "The documents provide the first definitive evidence that the NSA has for years made massive amounts of surveillance data directly accessible to domestic law enforcement agencies." The search engine, called ICREACH, allows analysts to search an array of databases, some of which contain metadata collected on innocent American citizens, for the purposes of "foreign intelligence." However, questions have been raised over its potential for abuse in what is known as "parallel construction," a process in which agencies use surveillance resources in domestic investigations, and then later cover it up by creating a different evidence trail to use in court.

Read more of this story at Slashdot.








3.17-rc2: mainline

Kernel Linux - Mar, 26/08/2014 - 12:36pd
Version:3.17-rc2 (mainline) Released:2014-08-25 Source:linux-3.17-rc2.tar.xz PGP Signature:linux-3.17-rc2.tar.sign Patch:patch-3.17-rc2.xz
Kategoritë: Kernel Linux

The Evolution of Diet

Slashdot.org - Mar, 26/08/2014 - 12:35pd
An anonymous reader writes Here's a story from National Geographic that looks at the historical diets of people from around the world and what that diet might look like in the future. From the article: "So far studies of foragers like the Tsimane, Arctic Inuit, and Hadza have found that these peoples traditionally didn't develop high blood pressure, atherosclerosis, or cardiovascular disease. 'A lot of people believe there is a discordance between what we eat today and what our ancestors evolved to eat,' says paleoanthropologist Peter Ungar of the University of Arkansas. The notion that we're trapped in Stone Age bodies in a fast-food world is driving the current craze for Paleolithic diets. The popularity of these so-called caveman or Stone Age diets is based on the idea that modern humans evolved to eat the way hunter-gatherers did during the Paleolithic—the period from about 2.6 million years ago to the start of the agricultural revolution—and that our genes haven't had enough time to adapt to farmed foods."

Read more of this story at Slashdot.








NRC Analyst Calls To Close Diablo Canyon, CA's Last Remaining Nuclear Plant

Slashdot.org - Hën, 25/08/2014 - 11:51md
An anonymous reader writes Michael Peck, who for five years was Diablo Canyon's lead on-site inspector, says in a 42-page, confidential report that the Nuclear Regulatory Commission is not applying the safety rules it set out for the plant's operation. The document, which was obtained and verified by The Associated Press, does not say the plant itself is unsafe. Instead, according to Peck's analysis, no one knows whether the facility's key equipment can withstand strong shaking from those faults — the potential for which was realized decades after the facility was built. Continuing to run the reactors, Peck writes, "challenges the presumption of nuclear safety."

Read more of this story at Slashdot.








NRC Analyst Calls For Closure of Diablo Canyon, CA's Last Remaining Nuclear Plant

Slashdot.org - Hën, 25/08/2014 - 11:51md
An anonymous reader writes Michael Peck, who for five years was Diablo Canyon's lead on-site inspector, says in a 42-page, confidential report that the Nuclear Regulatory Commission is not applying the safety rules it set out for the plant's operation. The document, which was obtained and verified by The Associated Press, does not say the plant itself is unsafe. Instead, according to Peck's analysis, no one knows whether the facility's key equipment can withstand strong shaking from those faults — the potential for which was realized decades after the facility was built. Continuing to run the reactors, Peck writes, "challenges the presumption of nuclear safety."

Read more of this story at Slashdot.








Nicholas Skaggs: Ubuntu Phone Translations Needed

Planet UBUNTU - Hën, 25/08/2014 - 11:16md
As we continue to iterate on new ubuntu touch images, it's important for everyone to be able to enjoy the ubuntu phone experience in their native language. This is where you can help!

We need your input and help to make sure the phone images are well localized for your native language. If you've never contributed a translation before, this is a perfect opportunity for you to learn. There's a wiki guide to help you, along with translation teams who speak your language and can help.

Don't worry, you don't need a ubuntu phone to do this work. The wiki guide details how to translate using a phone, emulator, or even just your desktop PC running ubuntu. If nothing else, you can help review other folks translations by simply using launchpad in your web browser.

If this sounds interesting to you and the links don't make sense or you would like some more personal help, feel free to contact me. English is preferred, but in the spirit of translation feel free to contact me in French, Spanish or perhaps even German :-).

Happy Translating everyone!

P.S. If you are curious about the status of your language translation, or looking for known missing strings, have a look at the stats page kept by David Planella.

Facebook Cleans Up News Feed By Reducing Click-Bait Headlines

Slashdot.org - Hën, 25/08/2014 - 11:07md
An anonymous reader writes "Facebook today announced further plans to clean up the News Feed by reducing stories with click-bait headlines as well as stories that have links shared in the captions of photos or within status updates. The move comes just four months after the social network reduced Like-baiting posts, repeated content, and spammy links."

Read more of this story at Slashdot.








Michael Meeks: 2014-08-25: Monday

Planet GNOME - Hën, 25/08/2014 - 11:00md
  • Chewed mail, caught up with the weekend backlog of customer mail, partner pieces etc. Product and consulting meetings. J. kindly filing the backlog of expenses; unwound some accomodation issues for Bern.

Whole Organ Grown In Animal For First Time

Slashdot.org - Hën, 25/08/2014 - 10:20md
An anonymous reader writes British scientists have produced the first working organ grown from scratch in a living animal. Reprogrammed cells created in a lab were used in a mouse to produce a thymus. The organ was created using connective tissue cells from a mouse embryo and were converted into a different cell strain by changing a genetic switch in their DNA. The resulting cells grew into the whole organ after being injected. It has only been tested on mice so far, but researchers at Edinburgh University say that within a decade the procedure could be effective and safe enough for humans. The findings were published in Nature Cell Biology.

Read more of this story at Slashdot.








Faqet

Subscribe to AlbLinux agreguesi