Feed aggregator

  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.

Bugtraq: Seagate Media Server stored Cross-Site Scripting vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Mon, 04/23/2018 - 00:00
Seagate Media Server stored Cross-Site Scripting vulnerability

Bugtraq: [slackware-security] gd (SSA:2018-108-01)

SecurityFocus Vulnerabilities/Bugtraq - Mon, 04/23/2018 - 00:00
[slackware-security] gd (SSA:2018-108-01)

Bugtraq: WebKitGTK+ Security Advisory WSA-2018-0003

SecurityFocus Vulnerabilities/Bugtraq - Mon, 04/23/2018 - 00:00
WebKitGTK+ Security Advisory WSA-2018-0003

Bugtraq: [SECURITY] [DSA 4174-1] corosync security update

SecurityFocus Vulnerabilities/Bugtraq - Mon, 04/23/2018 - 00:00
[SECURITY] [DSA 4174-1] corosync security update

More rss feeds from SecurityFocus

SecurityFocus Vulnerabilities/Bugtraq - Mon, 04/23/2018 - 00:00
News, Infocus, Columns, Vulnerabilities, Bugtraq ...

Intel Is Giving Up On Its Smart Glasses

Slashdot - Sun, 04/22/2018 - 23:05
Intel is planning to shut down the New Devices Group (NDG), and cease development on the Vaunt smart glasses project that was revealed earlier this year. The glasses are unique in that they use retinal projection to put a display in your eyeball. "There is no camera to creep people out, no button to push, no gesture area to swipe, no glowing LCD screen, no weird arm floating in front of the lens, no speaker, and no microphone," reports The Verge. Intel issued a statement announcing the plans: "Intel is continuously working on new technologies and experiences. Not all of these develop into a product we choose to take to market. The Superlight [the codename for Vaunt] project is a great example where Intel developed truly differentiated, consumer augmented reality glasses. We are going to take a disciplined approach as we keep inventing and exploring new technologies, which will sometimes require tough choices when market dynamics don't support further investment." From the report: It was always unclear how precisely Intel intended to bring the Vaunt glasses to market, though sources indicated that Intel wanted to find a partner with retail expertise to partner with. Jerry Bautista, the lead for Vaunt, told me back in December that Intel was "working with key ecosystem hardware providers -- whether they're frames or lenses and things like that. Because we believe there's a whole channel to people who wear glasses that's already there." The story was first reported by The Information.

Read more of this story at Slashdot.

Your Next Job Interview Could Be With a Racist Bot

Slashdot - Sun, 04/22/2018 - 22:04
An anonymous reader quotes a report from The Daily Beast: Companies across the nation are now using some rudimentary artificial intelligence, or AI, systems to screen out applicants before interviews commence and for the interviews themselves. As a Guardian article from March explained, many of these companies are having people interview in front of a camera that is connected to AI that analyzes their facial expressions, their voice and more. One of the top recruiting companies doing this, Hirevue, has large customers like Hilton and Unilever. Their AI scores people using thousands of data points and compares it to the scores of the best current employees. But that can be unintentionally problematic. As Recode pointed out, because most programmers are white men, these AI are actually often trained using white male faces and male voices. That can lead to misperceptions of black faces or female voices, which can lead to the AI making negative judgments about those people. The results could trend sexist or racist, but the employer who is using this AI would be able to shift the blame to a supposedly neutral technology. Companies are also having people do their first interview with an AI chatbot. "One popular AI that does this is called Mya, which promises a 70 percent decrease in hiring time," reports The Daily Beast. "Any number of questions these chatbots could ask could be proxies for race, gender or other factors."

Read more of this story at Slashdot.

Silicon Valley Investors Wants to Fund a 'Good For Society' Facebook Replacement

Slashdot - Sun, 04/22/2018 - 18:34
Silicon Valley angel investor Jason Calacanis just announced the "Openbook Challenge," a competition to create a replacement for Facebook. "Over the next three months, 20 finalists will compete for seven $100,000 incubator grants," explains long-time Slashdot reader reifman. "Their goal is to find startups with a sustainable business model e.g. subscriptions, reasonable advertising, cryptocurrency. etc. And they want it to be 'good for society.'" Jason Calacanis writes: All community and social products on the internet have had their era, from AOL to MySpace, and typically they're not shut down by the government -- they're slowly replaced by better products. So, let's start the process of replacing Facebook... We already have two dozen quality teams cranking on projects and we hope to get to 100... This is not an idea or business plan competition. We're looking for teams that can actually build a better social network, and we'll be judging teams primarily based upon their ability to execute... Keep in mind, that while ideas really matter, Zuckerberg has shown us, execution matters more. Calacanis has even created a discussion group for the competition...on Facebook. And his announcement includes a famous quote from Mark Zuckerberg. "Don't be too proud to copy."

Read more of this story at Slashdot.

Could We Fund a Universal Basic Income with Universal Basic Assets?

Slashdot - Sun, 04/22/2018 - 15:34
Universal Basic Incomes aren't really the issue, argues Fast Company staff writer Ben Schiller. "It's how you find $2 trillion to pay for it." One answer may come in the form of "universal basic assets" (UBA). UBA can mean a fund of publicly-owned infrastructure or revenue streams -- like Alaska's Permanent Fund which pays residents up to $2,000 a year from state oil taxes. Or, it can mean actual assets that drive down the cost of living, like tuition-free education and free public broadband. There are lots of proposals going around now that fall into these two camps... Entrepreneur Peter Barnes has called for the creation of a Sky Trust that would both limit the amount of carbon dioxide in the atmosphere and provide revenue from carbon taxes. These "carbon dividends" solve two problems at once: income inequality and climate change. He would also tax corporations for using natural resources, on the thinking that the atmosphere, minerals and fresh water around us represent a "joint inheritance." He would also tax speculative financial transactions and use of the electromagnetic spectrum. The U.K. think-tank IPPR recently proposed a similar "sovereign wealth fund owned by and run in the interests of citizens." It would finance the fund with "a scrip tax of up to 3% requiring businesses to issue equity to the government, or pay a tax of equivalent value," sales of land owned by the U.K. monarchy, and higher inheritance taxes. Blockchain can help. Blockchain technology could offer a way to divide publicly-owned infrastructure so it's genuinely publicly-owned. We could issue tokenized securities in the assets around us giving everyone a stake in their environment. Then they could trade those tokens on exchanges, like they were cryptocurrencies, or use the tokens as collateral on loans.

Read more of this story at Slashdot.

NYT: Lynchings Around the World are Linked To Facebook Posts

Slashdot - Sun, 04/22/2018 - 11:37
An anonymous reader quotes the New York Times: Riots and lynchings around the world have been linked to misinformation and hate speech on Facebook, which pushes whatever content keeps users on the site longest -- a potentially damaging practice in countries with weak institutions and histories of social instability. Time and again, communal hatreds overrun the newsfeed unchecked as local media are displaced by Facebook and governments find themselves with little leverage over the company. Some users, energized by hate speech and misinformation, plot real-world attacks. A reconstruction of Sri Lanka's descent into violence, based on interviews with officials, victims and ordinary users caught up in online anger, found that Facebook's newsfeed played a central role in nearly every step from rumor to killing. Facebook officials, they say, ignored repeated warnings of the potential for violence, resisting pressure to hire moderators or establish emergency points of contact... Sri Lankans say they see little evidence of change. And in other countries, as Facebook expands, analysts and activists worry they, too, may see violence. A Facebook spokeswoman countered that "we remove such content as soon as we're made aware of it," and said they're now trying to expand those teams and investing in "technology and local language expertise to help us swiftly remove hate content." But one anti-hate group told the Times that Facebook's reporting tools are too slow and ineffective. "Though they and government officials had repeatedly asked Facebook to establish direct lines, the company had insisted this tool would be sufficient, they said. But nearly every report got the same response: the content did not violate Facebook's standards."

Read more of this story at Slashdot.

Many Amazon Warehouse Workers are on Food Stamps

Slashdot - Sun, 04/22/2018 - 09:34
Many of Amazon's warehouse workers have to buy their groceries with food stamps through America's Supplemental Nutrition Assistance Program, reports the Intercept. In Arizona, new data suggests that one in three of the company's own employees depend on SNAP to put food on the table. In Pennsylvania and Ohio, the figure appears to be around one in 10. Overall, of five states that responded to a public records request for a list of their top employers of SNAP recipients, Amazon cracked the top 20 in four. Though the company now employs 200,000 people in the United States, many of its workers are not making enough money to put food on the table... "The average warehouse worker at Walmart makes just under $40,000 annually, while at Amazon would take home about $24,300 a year," CNN reported in 2013. "That's less than $1,000 above the official federal poverty line for a family of four." In addition Amazon uses temp workers who may also be on food stamps, notes the article, adding that in 2017 Amazon received $1.2 billion in state and local subsidies, while effectively paying no federal income tax. "The American people are financing Amazon's pursuit of an e-commerce monopoly every step of the way: first, with tax breaks, subsidies, and infrastructure improvements meant to lure fulfillment centers into town, and later with federal transfers to pay for warehouse workers' food."

Read more of this story at Slashdot.

What Happens When Restaurants Go Cashless

Slashdot - Sun, 04/22/2018 - 07:34
There's a new trend starting: restaurants that won't accept cash. USA Today reports: Restaurant owners say ordering is faster from customers who slap down plastic instead of dollars, cutting a few seconds out of the process. But most of the benefits appear to accrue to the restaurants: less time taken counting bills, reduced pilferage, no armored-car fees or fear of stickups. It's a risky strategy. For starters, upscale Millennials -- among the most coveted of diners because of their youth and affluence -- prefer to pay in cash, according to Bankrate.com data. Also, more than a third of Americans between the ages of 18 and 37 do not have a credit card. For customers, patronizing restaurants that don't take cash means one less payment option when they need a quick meal during an all-too-short lunch hour. Plus, it raises questions about whether it discriminates against cardless teens and the poor... A committee in Chicago is weighing Alderman Edward Burke's proposed requirement that merchants accept cash. Massachusetts has had a Discrimination Against Cash Buyers rule on the books since 1978... Lana Swartz, co-editor of the book Paid: Tales of Dongles, Checks, and Other Money Stuff, says "One of the cornerstones of American capitalism is everyone's money is equal." Meanwhile, the Associated Press reports: Many business owners would rather be cashless. Cash actually costs money -- banks charge fees for cash deposits and to handle coins... And counting and checking cash and preparing it for deposit takes up time a manager could spend with staff or customers... Millions of consumers use little or no cash. In a survey released last month by the financial services company Capital One, only 21 percent of 2,000 people questioned said cash was their most common way to pay for things. But going cashless isn't a slam-dunk. Some customers who want to use cash point to a statement on paper money: "This note is legal tender for all debts public and private." However, the Federal Reserve says on its website that private companies can make their own policies about cash unless there is a state law saying otherwise. One Houston restauranteur changed his mind about going cashless, saying "You can't compete if you think you're going to create a whole set of rules and expect people to follow them." One Chicago restauranteur admits that "it has generated the most negative pushback of anything we've ever done," estimating revenue fell 2% just from angry cash customers who never returned. But he persisted because his eight restaurants had experienced six burglaries, break-ins or armed robberies over the last eight years -- and got "dozens and dozens" of counterfeit bills from customers -- while by going cashless, he no longer has to pay for bank fees and armored car pickups.

Read more of this story at Slashdot.

Former Reddit Executive Sees 'No Hope' For Reddit

Slashdot - Sun, 04/22/2018 - 06:34
An anonymous reader quotes former Reddit product head Dan McComas: I think, ultimately, the problem that Reddit has is the same as Twitter and Discord. By focusing on growth and growth only and ignoring the problems, they amassed a large set of cultural norms on their platforms. Their cultural norms are different for every community, but they tend to stem from harassment or abuse or bad behavior, and they have worked themselves into a position where they're completely defensive... I really don't believe it's possible for either of them to catch up on the problem. I think the best that they can do is figure out how to hide this behavior from an average user. I don't see any way that it's going to improve. I have no hope for either of those platforms. I just think that the problems are too ingrained, in not only the site and the site's communities and users but in the general understanding and expectations of the public... I don't think that they're going to be able to turn these things around... I fundamentally believe that my time at Reddit made the world a worse place. And that sucks, and it sucks to have to say that about myself... I've got a lot of advice for start-ups, and it's not very fucking complicated. It's just: Think about the impact that you want to have on your users and on the people consuming your content and do the right thing... Don't be idiots about it. You're people, you see what's going on, you see trends that are forming, just fucking do something. It's not that hard.

Read more of this story at Slashdot.

Eventbrite Claims The Right To Film Your Events -- And Keep the Copyright

Slashdot - Sun, 04/22/2018 - 05:18
Eventbrite lets you sell tickets online for your events. An anonymous reader reports on Eventbrite's newly-updated merchant agreement. The merchant agreement specifies that you "grant permission to Eventbrite and its agents to enter onto and remain on the premises (including real property, fixtures, equipment, or other personal property) where your event is hosted...with personnel and equipment for the purpose of photographing and recording the Premises, both internally and externally in connection with the production of digital content on the date of your event(s) and any other dates reasonably requested by Eventbrite (for example, during setup and breakdown for the event) (the 'Shoot')." But in addition, you're also granting them permission to record and use footage of all your attendees and speakers, "in any manner, in any medium or context now known or hereafter developed, without further authorization from, or compensation to." And after that Eventbrite "will own all rights of every nature whatsoever in and to all films and photographs taken and recordings made hereunder, including without limitation of all copyrights therein and renewals and extensions thereof, and the exclusive right to use and exploit the Recordings in any manner, in any medium or context now known or hereafter developed..." You're even responsible for obtaining all the clearances and licenses "necessary to secure Eventbrite the permissions and rights described above," and you also release Eventbrite from any claims that may arise regarding use of the Recordings, "including, without limitation, any claims of defamation, invasion of privacy, or infringement of rights of likeness, publicity or copyright." "So, yeah. No," tweeted Ars Technica's national security editor. "Eventbrite is now off my list for recommended event organizing tools."

Read more of this story at Slashdot.

GitHub Launches Bot-Powered Learning Lab for New Developers

Slashdot - Sun, 04/22/2018 - 04:34
An anonymous reader quotes VentureBeat: GitHub is launching a new bot-powered learning lab to help budding developers get up to speed on all things GitHub... The GitHub Learning Lab, which officially launched Thursday, builds on GitHub's prior history of training people, except this time GitHub is using bots to expedite the learning process. There is no videoconferencing or webcasts here. "After training thousands of people to use Git and GitHub, the GitHub Training Team has established a tried-and-true method for helping new developers retain more information and ramp up quickly as they begin their software journeys," the company said in a blog post. "And now, we're making those experiences accessible to developers everywhere with GitHub Learning Lab." The bot helps users work through issues in a repository environment, passing comment on any work that you do while checking over pull requests -- notifications of changes you've made -- in a similar fashion to how a human project lead might do. If the bot isn't able to help with a specific question you have, there are humans on hand too via the GitHub Learning Lab forum, which includes outside experts and members of GitHub's in-house training team.

Read more of this story at Slashdot.

Lycos Finally Discontinues Its Free Email Service

Slashdot - Sun, 04/22/2018 - 03:34
Long-time Slashdot reader williamyf writes: You may think of it as the end of an era, or as the final nail in the coffin. Today Lycos, one of the pioneering web portals of the '90s, notified all it's users that "On May 15th, 2018, we will no longer be offering free Lycos Mail accounts." They have been very upfront about the reason: "Q: Why are you doing this? A: Providing mailboxes costs us money, and we no longer make enough from ads to support the cost of the mailboxes." At it's heyday, Lycos was acquired by Terra Networks (a division of Telefonica), then sold to Daum Communications in Korea and then to Ybrant Digital in India. The search engine and other parts (like Angelfire, Tripod and Gamesville) continue working. In the meantime, instructions are provided to download all your mail via POP3 for offline archiving, or to upgrade to Paid Accounts.

Read more of this story at Slashdot.

Doctors Tried To Lower $148K Cancer Drug Cost; Makers Tripled Its Price

Slashdot - Sun, 04/22/2018 - 02:34
Slashdot reader Applehu Akbar writes: Imbruvica, a compound that treats white blood cell cancers, has until now been a bargain at $148,000 per year. Until now, doctors have been able to optimize dosage for each patient by prescribing up to four small-dose pills of it per day. But after results from a recent small pilot trial indicated that smaller doses would for most patients work as well as the large ones, its manufacturer, Janssen and Pharmacyclics, has decided on the basis of the doctors' interest in smaller dosages to reprice all sizes of the drug to the price of the largest size. This has the effect of tripling the price for patients, and doctors have now put off any plans for further testing of lower dosages. The researchers are retaliating by urging clinical investigators to test whether the expensive pill could be safely given every other day -- and by calling on America's public health regulators to investigate the drug's pricing.

Read more of this story at Slashdot.

Lyft Announces It Will Make All Rides Carbon Neutral

Slashdot - Sun, 04/22/2018 - 01:34
Lyft announced it will spend millions of dollars to make all its rides carbon neutral. An anonymous reader quotes CNN Money: The San Francisco-based ride-hailing company announced Thursday that it will pay for a range of environmentally beneficial projects to compensate for the emissions from the millions of car journeys it provides every week. The tactic, known as carbon offsets, is a way for Lyft to do something about climate change without changing its business model. Lyft will fund initiatives including forestry projects, renewable energy ventures and capturing emissions from landfills. The efforts will put Lyft among the 10 largest voluntary offset programs in the world, according to 3Degrees, the renewable energy company Lyft is partnering with to find suitable projects... Lyft will track how many miles its drivers cover -- and the make and model of their vehicles -- to calculate exactly how many emissions it must offset. The company will not limit itself just to the carbon footprint from when passengers are in Lyft vehicles, but will also include the mileage its drivers rack up on their way to pick people up. Lyft co-founder John Zimmer believes that within their first year they'll offset over a million metric tons of carbon -- "equivalent to planting tens of millions of trees or taking hundreds of thousands of cars off the road." Zimmer told CNN that "With great scale comes great responsibility."

Read more of this story at Slashdot.

Can Tesla's Batteries Power Puerto Rico?

Slashdot - Sun, 04/22/2018 - 00:34
An anonymous reader quotes Electrek: Almost 1 million ratepayers of the Puerto Rican Electric Power Authority on the island of Puerto Rico were reportedly without power Wednesday during an island-wide blackout. But a few hundred locations with Tesla Energy storage systems were able to keep the lights on, according to CEO Elon Musk... Some of those locations include very critical services. For example, Tesla deployed a series of Powerpack systems on the Puerto Rican islands of Vieques and Culebra for a sanitary sewer treatment plant, the Arcadia water pumping station, the Ciudad Dorada elderly community, the Susan Centeno hospital, and the Boys and Girls Club of Vieques. Furthermore, the automaker's energy division also deployed a solar+battery system at a hospital in Puerto Rico... It was also reported that the Puerto Rican government was considering Tesla's plan for a series of microgrids to help bring back power on a larger scale. The government has confirmed that they "presented several projects in remote areas that would allow entire communities to be more independent" and they also "presented a proposal to the Authority for Public-Private Partnerships for the deployment of a large-scale battery system designed to help stabilize the entire Puerto Rico electricity network." The proposal, involving de-centralized local solar farms, "should prove more resilient to natural disaster," Electrek reported earlier, adding " and of course, it would be a lot cleaner than their currently mostly fossil fuel-based power generation." Already Tesla batteries are "live and delivering power" at 662 locations, Elon Musk tweeted Wednesday. Meanwhile, CNN reports that one Puerto Rico resident spent three weeks building his own solar power system using $7,500 in parts -- which will ultimately prove cheaper than the $350 a month he was spending to run a gas generator (and waiting as long as six hours in the long gas lines). They're not revealing his name "because he's concerned someone may try to steal his new system."

Read more of this story at Slashdot.

Wells Fargo Agrees to $1 Billion Fine Over Home and Auto Loan Abuses

Slashdot - Sat, 04/21/2018 - 23:34
Wells Fargo got hit with a $1 billion fine Friday -- the largest ever issued by America's consumer protection agency. An anonymous reader quotes Reuters: Taken together, the mortgage and auto programs ensnared more than 600,000 customers and will require nearly $300 million in refunds, the bank has said. The programs allowed Wells Fargo to earn fees from unneeded car insurance and penalties on mortgage paperwork that the bank had botched. For homebuyers, Wells Fargo promised to "rate lock" or freeze the interest rate for borrowers who got their mortgage paperwork finished within a few weeks. When that deadline slipped and it was the bank's fault, Wells Fargo could blame the customer. The penalty for late mortgage paperwork often topped $1000, according to a borrower lawsuit... Drivers stung by insurance fees were wrongly pushed into policies that they did not need... Insurers working for Wells Fargo pushed policies onto more than 500,000 customers who already had coverage, the bank has said. The penalty comes 18 months after Wells Fargo "admitted it opened sham accounts for customers -- a practice that likely ensnared millions... Wells Fargo agreed to the new $1 billion fine "without admitting or denying wrongdoing."

Read more of this story at Slashdot.

Syndicate content