faufay kangie alecko
Trinidad Baltzell
Many happy returns to New Order "Blue Monday" (FAC73) on it's 40th Anniversary. The biggest selling 12" of all time, probably the greatest dance record of all time and undisputedly the most influential. For the anniversary, Jamie Stevens has reworked the original into an epic, special anniversary remix exploring deeper, ambient moods and melancholy electronica territory as Jamie Stevens does so well.Follow: @jamiestevens@musictodiefor
It's great to have this version out there. I started working on this during the first COVID lockdown here in Melbourne in 2020. Seemed only fitting to finish it off for the anniversary of Blue Monday's release. I hope you enjoy this rather different take channeling Martin Hannett and a smattering of Disintegration-era The Cure.
Cities, transit agencies, and mobility companies trust Remix with their transportation-related data. We are committed to keeping data secure and can provide details about our security measures to current and prospective customers and partners upon request.
This page details how we protect our platform, the data it stores, and the people that depend upon it.
All of the application infrastructure for Remix is currently managed by Amazon Web Services (AWS) and Heroku, a subsidiary of Salesforce. All data is stored in data centers managed by Amazon. These data centers have received ISO 27001 and SOC certifications, Federal Information Security Management Act (FISMA) Moderate Authorization, and accreditation from the U.S. General Services Administration.
Sensitive data is ingested, processed, and stored in an isolated, secured environment in AWS, referred to as a partner data account. Aggregation is done within the partner data account, and only the aggregated data leaves it. The isolated account requires additional steps for Remix developers to access, including a written approval process and specialized training.
Our cloud providers and centralized logging and alerting system provide intrusion detection capabilities that alert us of suspicious and malicious behavior. The feeds include information from network events, internal-system events, and vulnerability / threat intelligence feeds.
Our APIs and web front-ends are all configured to use the latest TLS version (once broadly supported by browsers and our cloud hosting providers), check for a valid, signed, domain-specific certificate and use a strong set of cryptographic protocols. Our encrypted-by-default philosophy also means that we don't support fall-back to unencrypted communications (e.g. https -> http).
We classify data according to type and sensitivity and use that classification to define which systems are authorized to access and store different types of data. The data sensitivity classification is used in the risk assessment process to determine the appropriate level of security controls..
Remix has a policy to limit direct access to databases and backups to Remix engineers. Access to sensitive data is limited strictly to people who need it to do their jobs. We review access periodically and offboard people who no longer need access. Each developer has unique credentials and 2 factor authentication is enforced.
Remix uses AWS and Heroku to store customer data and documents. These databases have network-level isolation via Virtual Private Clouds (VPCs) and access is controlled via Access Control Lists (ACLs). Our policy is to automatically deny any traffic which is not explicitly allowed to or from a database. In addition to network isolation, all data is encrypted at rest and in transit.
Remix employs role-based access controls to manage access to servers containing application data. These controls are designed to require authorized employees to use individual account and authentication credentials to gain access. Remix controls access to servers and data stores through authentication handled with key-based SSH sessions. We operate on the Principle of Least Privilege, which is designed to access to a system is only granted if absolutely required to serve a legitimate business need. Our policy is that employees only have access to data and systems they need to do their job.
The Remix codebase is currently stored in GitHub and requires multi-factor authentication and team-based authorization to view or edit. All changes to the codebase are logged with the name of the person making the change, the time, and precisely which lines of code changed. All changes to code running on production servers is peer-reviewed with specific attention paid to security prior to being deployed. An audit trail is kept for all changes to code running in production.
Remix has formalized hiring policies and procedures, performance management, and termination practices. Access to company systems is removed as soon as possible once it is no longer needed. Remix conducts comprehensive pre-hire background checks to the extent permitted by law.
Our developers review secure coding standards applicable to the environments, languages, and platforms they're working in. These standards may include ensuring access control of data, sanitizing input / output values, and logging violations that could indicate an attack or vulnerability.
We currently use AWS Secrets Manager and AWS Parameter Store for storing and managing all secrets in the partner data account. Secrets are automatically rotated on a regular schedule. All secrets are encrypted-at-rest, using signing keys managed through AWS Key Management Service, and encrypted-in-transit via TLS secured connections. Access to specific secrets is restricted to the services which need access, and the Remix engineers who maintain those services.
Remix periodically brings in an external team to test our security, including audits for compliance and penetration tests. Assessments are based on current attack trends and verification of best practices (e.g. OWASP Top 10). Findings are reviewed and remediated by our technical teams.
Our mission is to help build more livable cities. We make software tools that cities use to understand multi-modal urban transportation systems and improve safety, access to mobility, and sustainability in their communities. Where those tools incorporate mobility data, our contracts with cities and mobility companies govern our access to data and limit what we can and cannot do with it.
The study, by a team at University College London, comes after decades of research showing that both loneliness and infrequent contact with friends and family can, independently, shorten a person's life. The scientists expected to find that the combination of these two risk factors would be especially dangerous.
To find out, the team studied 6,500 men and women ages 52 and older. All of them had answered a questionnaire back in 2004 or 2005 that assessed both their sense of loneliness and how much contact they had with friends and family. The researchers looked to see what happened to those people over the next seven or eight years.
And Steptoe says he was surprised by the result. "Both social isolation and loneliness appeared initially to be associated with a greater risk of dying," he says. "But it was really the isolation which was more important."
At first, it looked like people who reported greater levels of loneliness were more likely to die, Steptoe says. But closer analysis showed that these people were also more likely to have other risk factors, like being poor and having existing health problems. Once those factors were taken into account, the extra risk associated with loneliness pretty much disappeared, Steptoe says.
But people who spent very little time with friends and family, or at social events, were more likely to die regardless of income or health status, the team reports in the Proceedings of the National Academy of Sciences.
It's not clear why social isolation is linked to mortality. But one possibility is that having other people around has practical benefits as you get older, Steptoe says. For example, they may push you to go see a doctor if you are having symptoms like chest pain, he says. And if you were to lose consciousness, they would call for help.
"It doesn't negate the loneliness work that's been done to date," says Bert Uchino, a University of Utah psychology professor. He says this study may have reached a different conclusion than earlier ones because people's definition of loneliness is changing in the Internet age.
"People ... may think that they're connected to other people because they're on Facebook," Uchino says. So they may not report feeling lonely. But that sort of connection, he says, may not have the health benefits of direct contact with other people.
The different result might be because this study looked at people in the U.K., while many earlier studies looked at people in the U.S., says University of Chicago psychologist John Cacioppo. So in the U.K., where the culture values a "stiff upper lip," people who live alone may be "less likely to admit to feeling lonely than are residents of the U.S.," he says.
And it's easy for people to do things that alleviate both isolation and loneliness, Uchino says. "Have lunch with somebody," he says. "Take a walk. Give them a phone call. I think those are all important ways that we need to stay connected with our relationships. And I think, in the long term, it can help us."
-- Be sure to grab this morning's printed IndyStar! We include our annual coupon for free admission at the Indiana State Fair, good this Wednesday only. At IndyStar.com, we also round up other ways fairgoers can save.
2. I'm STILL wincing: Pacers' Paul George suffered a gruesome leg break in a USA Basketball scrimmage Friday night and, thankfully, underwent a successful surgery. As father Paul George Sr. said this weekend, it's almost certain the Indiana Pacers have lost All-Star forward Paul George for the season, says IndyStar's Nat Newell. He notes that of five NBA teams that lost their leading scorer to injury or free agency after posting a .660 winning percentage (roughly 55 wins) or better in the past 10 years, on average these teams only went on to win half as many games.
c01484d022