1526
1
US Mad (www.theregister.com)

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

1527
48
submitted 1 year ago by Wilshire@lemmy.ml to c/technology@lemmy.ml
1528
-1

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

1529
301
1530
8
DALL·E 3 (openai.com)

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.

1531
13
1532
144
1533
26
1534
2
1535
546
1536
81
1537
-11

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.

1538
395
submitted 1 year ago* (last edited 1 year ago) by Apollo2323@lemmy.dbzer0.com to c/technology@lemmy.ml

!textfiles@mastodon.archive.org - 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!

1539
67

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.

1540
52
1541
6
submitted 1 year ago* (last edited 1 year ago) by bahmanm@lemmy.ml to c/technology@lemmy.ml

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.

1542
52
submitted 1 year ago by Blizzard@lemmy.zip to c/technology@lemmy.ml

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

"Microsoft was responsible for the error."

1543
55
1544
195
submitted 1 year ago by Xepher@lemm.ee to c/technology@lemmy.ml

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.

1545
74
1546
177

Microsoft Paint is introducing support for both layers and transparency

1547
168
1548
72
submitted 1 year ago by zabadoh@lemmy.ml to c/technology@lemmy.ml

The included clip is pretty convincing...

1549
-4
submitted 1 year ago by cyu@sh.itjust.works to c/technology@lemmy.ml
1550
99

cross-posted from: https://derp.foo/post/245137

There is a discussion on Hacker News, but feel free to comment here as well.

view more: ‹ prev next ›

Technology

34728 readers
170 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