Technology

34713 readers
118 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
1426
1427
1428
 
 

If you noticed something funky going on with Salesforce and its software-as-a-service empire today, it's not you: it's recovering from an hours-long outage.

As of writing, Salesforce said at 1829 UTC (1130 PT) in a status update that all of its clouds are returning to normal after suffering about a four-hour downtime.

Well, all except for Salesforce's Tableau and Mulesoft, which remain down or affected to some extent.

The IT breakdown started at 1448 UTC, and we're told by the enterprise software giant this hit "customers across multiple clouds including, Commerce Cloud, Mulesoft, Tableau, Core, Marketing Cloud Account Engagement, Marketing Cloud Intelligence, and Omni Channel."

As a result, "users are unable to log into Salesforce or access any of their services," the biz admitted.

Two hours later, the team said its ClickSoftware, Trailblazer, and Data Cloud products were also affected. At first a third-party cloud provider was thought to be to blame for intermittent networking issues causing Salesforce services to fail.

Then the tech titan said, actually, a cloud provider wasn't at fault, and Salesforce engineers "successfully executed a rollback to mitigate the issue." By 1752 UTC, the biz said its cloud systems were getting back on track, and customers should be able to log in and use their applications as usual, as long as those apps weren't Tableau or Mulesoft.

1429
 
 

Philip Paxson's family are suing the company over his death, alleging that Google negligently failed to show the bridge had fallen nine years earlier.

Mr Paxson died in September 2022 after attempting to drive over the damaged bridge in Hickory, North Carolina.

A spokesperson for Google said the company was reviewing the allegations.

The case was filed in civil court in Wake County on Tuesday.

Mr Paxson, a father of two, was driving home from his daughter's ninth birthday party at a friend's house and was in an unfamiliar neighbourhood at the time of his death, according to the family's lawsuit.

His wife had driven his two daughters home earlier, and he stayed behind to help clean up.

"Unfamiliar with local roads, he relied on Google Maps, expecting it would safely direct him home to his wife and daughters," lawyers for the family said in a statement announcing the lawsuit.

"Tragically, as he drove cautiously in the darkness and rain, he unsuspectingly followed Google's outdated directions to what his family later learned for nearly a decade was called the 'Bridge to Nowhere,' crashing into Snow Creek, where he drowned."

Local residents had repeatedly contacted Google to have them change their online maps after the bridge collapsed in 2013, the suit claims.

1430
 
 

The Climate of Misinformation report by Climate Action Against Disinformation looked at Meta, Pinterest, YouTube, TikTok and Twitter for their content moderation policies and efforts to mitigate inaccurate information such as climate denialism. The group, which is made up of dozens of international climate and anti-disinformation organizations including Greenpeace and Friends of the Earth, released the report to draw attention towards climate misinformation on major platforms and makes the claim that big tech has become a “complicit actor” in accelerating the spread of climate denial.

Twitter’s low rank in the survey was because it failed to meet almost any of the organization’s criteria for climate misinformation policies, which ranged from having clear and publicly available information on climate science to having clearly articulated policies on what actions the company will take against the spread of misinformation. The report noted that billionaire tech mogul Elon Musk’s purchase of the company last year added to the confusion over how policies are enforced and how the company makes content decisions.

“Elon Musk’s acquisition of the company has created uncertainty about which policies are still standing and which are not,” the report stated.

Twitter received its only point in the report for fulfilling one of the researchers’ requirements that platforms have an easily accessible and readable privacy policy. Twitter was also the only platform to lack a clear reporting process for flagging harmful or misleading content for higher review.

Tech platforms have long struggled with creating effective or coherent policies on content moderation, while events such as the Covid-19 pandemic and the 2020 US presidential election resulted in swaths of misinformation circulating online. Amid conservative backlash and labor cuts in the tech industry, many companies have also deprioritized content moderation and opened the door to potential surges in misinformation on their platforms.

Although the other platforms fared better, none ranked especially high on the report’s scale – Pinterest scored highest with 12 points out of a possible 21. Issues ranged from a lack of clear definitions of what constituted climate misinformation, failure to enforce existing policies in a transparent way and a lack of proof that companies apply these policies equally across different languages. None of the companies release public reports on how their algorithmic changes affect climate misinformation, according to the report.

The organization’s authors advocate for a number of changes to big tech’s policies, including establishing clear guidelines on climate and updating privacy policies to show when private data is being sold to advertisers that could be linked to the fossil fuel industry.

1431
1432
 
 

subject

1433
0
US Mad (www.theregister.com)
submitted 1 year ago by [email protected] to c/[email protected]
 
 

Surprisingly good comments section. Even got one poster saying “Comeonguys, stop being so anti-US.”

1434
1435
 
 

Joysticks replacing keyboards for example What impact could it have on the design of the computer?

1436
1437
 
 

cross-posted from: https://psychedelia.ink/post/521936

DALL·E 3 understands significantly more nuance and detail than our previous systems, allowing you to easily translate your ideas into exceptionally accurate images.

1438
1439
1440
1441
 
 

In the ever-evolving world of software development, staying ahead of the curve is essential. As we enter 2023, the landscape of developer tools continues to expand and innovate. To help you navigate this dynamic field, we've curated a list of the best 10+ essential developer tools that every software engineer, coder, and developer should consider integrating into their workflow.

1442
 
 

[email protected] - A silly milestone we passed sometime this year: The Internet Archive now emulates (to various degrees, of course), over 250,000 pieces of software, hardware, and electronics, thanks to the effort of a dozen emulation projects and all of them running in the browser. Live again, ancient software!

1443
 
 

Today, Elon Musk and Israeli Prime Minister Benjamin Netanyahu livestreamed a discussion largely focused on the future of AI on Musk's platform X, formerly known as Twitter.

1444
1445
6
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 
 

cross-posted from: https://lemmy.ml/post/5193714

A few days DHH (from 37signals) wrote about how they moved off the cloud and how that has helped reduce their costs by a good measure.

Well, earlier today, he announced the first bit of tooling that they used as part of their cloud exit move: Kamal - which is already at version 1.0 and, according to DHH, stable.


I took a quick look at the documentation and it looks to me like an augmented and feature-rich Docker Compose which is, to no surprise, rather opinionated.

I think anyone who's had experience with the simplicity of Docker Swarm compared to K8s would appreciate Kamal's way. Hopefully it will turn out to be more reliable than Swarm though.

I found it quite a pragmatic approach to containerising an application suite with the aim of covering a good portion of a the use-cases and requriements of smaller teams.


PS: I may actually try it out in an ongoing personal project instead of Compose or K8s. If I do, I'll make sure to keep this post, well, posted.

1446
 
 

cross-posted from: https://lemmy.zip/post/2965946

"Microsoft was responsible for the error."

1447
1448
 
 

cross-posted from: https://lemm.ee/post/8552498

After six years of reviewing a variety of Wyze security cameras at Wirecutter, we’ve made the decision to suspend our recommendation of them from all our guides.

On September 8, 2023, The Verge reported an incident in which some Wyze customers were able to access live video from other users’ cameras through the Wyze web portal. We reached out to Wyze for details, and a representative characterized the incident as small in scope, saying they “believe no more than 10 users were affected.” Other than a post to its user-to-user online forum, Wyze Communities, and communication to those it says were affected, the company has not reached out to Wyze customers, nor has it provided meaningful details about the incident.

We believe Wyze is acting irresponsibly to its customers. As such, we've made the difficult but unavoidable decision to revoke our recommendation of all Wyze cameras until the company implements meaningful changes to its security and privacy procedures.

The concern is not that Wyze had a security incident—just about every company or organization in the world will probably have to deal with some sort of security trip-up, as we have seen with big banks, the US military, Las Vegas casinos, schools, and even Chick-fil-a. The greater issue is how this company responds to a crisis. With this incident, and others in the past, it’s clear Wyze has failed to develop the sorts of robust procedures that adequately protect its customers the way they deserve.

We spoke about this incident to peers, colleagues, and experts in the field, such as Ari Lightman, professor of digital media and marketing at Carnegie Mellon University; Jen Caltrider, program director at Mozilla’s Privacy Not Included; and Wirecutter senior staff writer Max Eddy. All of them agree the central issue is that Wyze has not proactively reached out to all its customers, nor has it been adequately accountable for its failures. “When these sort of things happen, [the company has to be] very open and transparent with [the] community as to why they screwed up,” Lightman explained. “Then the company has to say, ‘Here’s exactly what we’re going to be doing to rectify any potential situation in the future.’”

If this were the first such incident, we might be less concerned. However, it comes on the heels of a March 2022 Bitdefender study (PDF), which showed that Wyze took nearly three years to fully address specific security vulnerabilities that affected all three models of Wyze Cams. The company did eventually alert customers of the issue, and it notably guided them to stop using the first-generation Wyze Cam because “continued use of the WyzeCam after February 1, 2022 carries increased risk, is discouraged by Wyze, and is entirely at your own risk”—but that was long after the serious vulnerability was first discovered and reported to Wyze, on multiple occasions, without getting a response.

The fundamental relationship between smart-home companies and their customers is founded on trust. No company can guarantee safety and security 100% of the time, but customers need to be confident that those who make and sell these products, especially security devices, are worthy of their trust. Wyze’s inability to meet these basic standards puts its customers and its devices at risk, and also casts doubt on the smart-home industry as a whole.

In order for us to consider recommending Wyze’s cameras again, the company needs to devise and implement more rigorous policies, as most of its competitors already have. They need to be proactive, accountable, and transparent. Here’s what we expect from Wyze in the event of a security incident:

  • Reach out to customers as soon as possible: Send an email to all customers, send push notifications in the app, put out a press release, broadcast in the Wyze Communities online forum.
  • Describe the issue in detail and state precisely who was affected (and who wasn’t).
  • Explain specifically what steps are being taken to aid affected customers and what if any actions the customer needs to take on their own.
  • Follow-up with customers to let them know the issue has been resolved.

For anyone who has Wyze cameras and intends to continue using them, we recommend restricting their use to noncritical spaces or activities, such as outdoor locations. If you are looking for an alternative, better camera options are available—even for smart-home users on a budget.

This isn’t the first time Wirecutter has pulled a smart-home device due to concerns over accountability. In 2019, in response to a data breach at Ring, we retracted our endorsement of all of the company’s cameras. We eventually returned to reviewing Ring gear, and in some cases recommended them to our readers, after the company made a series of significant improvements to its programs and policies.

We continue to recommend Wyze lighting, since we consider them lower-risk, lower-impact devices—a security breach of a light bulb, for instance, wouldn’t give someone a view of your living room. Should Wyze change course and adopt more substantial policies like those above, we will be happy to resume testing and considering them for recommendation.

1449
 
 

Microsoft Paint is introducing support for both layers and transparency

1450
 
 

The included clip is pretty convincing...

view more: ‹ prev next ›