[-] [email protected] 53 points 1 year ago

Fourteenth Amendment to the United States Constitution

Section 3: Disqualification from office for insurrection or rebellion

Section 3. No person shall be a Senator or Representative in Congress, or elector of President and Vice President, or hold any office, civil or military, under the United States, or under any State, who, having previously taken an oath, as a member of Congress, or as an officer of the United States, or as a member of any State legislature, or as an executive or judicial officer of any State, to support the Constitution of the United States, shall have engaged in insurrection or rebellion against the same, or given aid or comfort to the enemies thereof. But Congress may, by a vote of two-thirds of each House, remove such disability.

[-] [email protected] 59 points 1 year ago

After decades of license strangleholds by the likes of MPEG LA and Microsoft, it's refreshing to see open codecs adopted in mainstream hardware and APIs. Hooray for progress!

[-] [email protected] 64 points 1 year ago* (last edited 1 year ago)

Epic cons:

Also:

  • Epic has already been caught scanning and collecting data from files on people's hard drives that are totally unrelated to Epic or its games.
  • Epic's habit of interfering with game availability, through exclusivity deals.

Ties with Tencent (super anti-consumer chinese state-owned megacorp)

To be more clear about it, Tencent is Epic's largest investor, so they obviously have a great deal of influence over and access to anything they want from Epic (likely including user data) and they directly benefit from Epic's growth.

Steam pros:

Also:

  • Actively funding and supporting development of linux gaming technologies for more than a few years now, to the point where linux is now very much a viable gaming platform.

Steam cons:
Drm

Given that DRM on Steam is entirely up to each game publisher, I don't think it's appropriate to list under "Steam cons". I'm not even sure that any of my Steam games have DRM.

If you mean that most Steam games expect to find an instance of Steam running, you should know that is not DRM, and it's trivially replaced with the open-source Goldberg Emulator or a similar tool.

Gog
I don’t know anything besides the fact that it has drm-free games

Another plus for GOG is that they let you download games with a web browser. No special app required. (I think Itch.io does this as well.)

[-] [email protected] 68 points 1 year ago

This seems like a step in the right direction. Much like language translation, doing it on-device is the only way to preserve people's data agency / privacy.

103
submitted 2 years ago by [email protected] to c/[email protected]
56
submitted 2 years ago by [email protected] to c/[email protected]
254
submitted 2 years ago by [email protected] to c/[email protected]
[-] [email protected] 66 points 2 years ago* (last edited 2 years ago)

It's not just Protonmail.

Blacklists like these aggressively and unapologetically collect all privacy-focused email domains they find, including simple forwarding and tagging services. With more and more sites using these lists to reject or black-hole email addresses, it has become difficult to protect one's self from spam and cross-site account tracking.

Dear web developers, please don't use these lists. Well-intended or not, they are privacy and user-hostile.

58
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]
1
submitted 2 years ago by [email protected] to c/[email protected]
42
Nuclear Reactor Simulator (dalton-nrs.manchester.ac.uk)
submitted 2 years ago by [email protected] to c/[email protected]
25
submitted 2 years ago by [email protected] to c/[email protected]
93
submitted 2 years ago by [email protected] to c/[email protected]
18
submitted 2 years ago by [email protected] to c/[email protected]
37
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

The latest Battle.net update is broken in Wine (and Proton), creating a blank gray window where the launcher UI should be.

If you had it installed before yesterday, your WINEPREFIX probably still contains the previous version in drive_c/Battle.net/Battle.net.14494 . In that case, deleting the (newer) Battle.net.14542 sibling folder and restarting should work around the problem for now.

Note that the new version will be downloaded again at each launch, so you'll have to perform this workaround every time, until it (hopefully) gets fixed. Alternatively, you can remove write permission to the drive_c/Battle.net folder to prevent downloading new versions, and remember to restore it later.

UPDATE:

Proton-like Wine builds are patched to work around the problem if you set the WINE_SIMULATE_WRITECOPY=1 environment variable. I verified this with a Wine-GE build.

I don't know if that patch will make it into mainline Wine, but CodeWeavers seem to be supporting the same environment variable.

93
PipeWire 1.0.0 released (gitlab.freedesktop.org)
submitted 2 years ago by [email protected] to c/[email protected]

The PipeWire project is immensely proud to announce the 1.0 release of PipeWire.

It is API and ABI compatible with previous 0.3.x releases.

[...snip...]

Happy Holidays!

Highlights

  • Fix a memfd/dmabuf leak when uploading buffers while shutting down.
  • Handle concurrent jack_port_get_buffer() calls because ardour seems to be doing this.
  • Improve time reporting (less jitter) in ALSA when using IRQ.
  • Many doc improvements.

PipeWire

  • Respect PIPEWIRE_DLCLOSE everywhere, remove pw_in_valgrind().
  • Remove a warning when a client tries to change ignored properties.

Modules

  • Fix a memfd/dmabuf leak when uploading buffers while shutting down.
  • Fix a potential segfault when copying mix structures. (#3658)
  • Avoid races in setrlimit in module-rt.
  • Fix a memory leak in filter-chain.
  • Set rtp.ptime on senders, not receivers.
  • The ROC modules were ported to ROC 0.3

SPA

  • Improve time reporting (less jitter) in ALSA when using IRQ. (#3657)
  • Add latency param query in libcamera.
  • Fix some compiler warnings.
  • The EVL plugin was updated.

Bluetooth

  • LC3 codec and compatibility improvements.

Pulse server

  • Fix emission of events when a sink/source state changes. (#3660)

JACK

  • Improve transport and time handling. Use unique ids to make consistent snapshots of the current time and transport.
  • Avoid enumerating port params that we are not going to use.
  • Optimize buffer reuse.
  • Handle concurrent jack_port_get_buffer() calls because ardour seems to be doing this. (#3632)

Docs

  • Many doc improvements.
  • Add man pages for pw-dump, pw-loopback, modules, pipewire-pulse.
  • Manpages are now made with Doxygen.
  • Add docs for pulse-modules
38
submitted 2 years ago by [email protected] to c/[email protected]

This release rolls up a bunch of features, perf improvements and bug fixes / workarounds as usual.

Features

DXR enabled by default

VKD3D_CONFIG=dxr is default now, and no longer needed. There are some special cases where DXR is not enabled by default. The only such current example is "Hellblade: Senua's Sacrifice" on Deck which force-enables DXR if it is supported, even on Deck. New semantics are:

  • dxr: Force-enable DXR, even when it is considered unsafe
  • nodxr: Disable DXR
  • dxr11: Removed. dxr already implied DXR 1.1 anyway

Sampler feedback

This feature was the last feature required for FL 12.2 and is implemented through emulation. As demonstrated in the implementation docs, all native implementations of this feature are fundamentally broken in some way. There's also no known game that ships requiring this feature, so we just consider this a checkbox feature.

DX Ultimate (FL 12.2) now exposed by default

On RDNA2+ and Turing+ we can finally expose the DX Ultimate feature set!

Misc

  • Implement a bunch of missing "Vulkan-on-D3D12" features
    • IndependentFrontAndBackStencilRefMaskSupported
    • TriangleFanSupported
    • DynamicIndexBufferStripCutSupported
    • DynamicDepthBiasSupported
    • NonNormalizedCoordinateSamplersSupported
    • MismatchingOutputDimensionsSupported
    • PointSamplingAddressesNeverRoundUp
    • RasterizerDesc2Supported
      • Explicit line rasterization mode
    • NarrowQuadrilateralLinesSupported
    • AnisoFilterWithPointMipSupported
  • Implement missing MSAD instruction in DXIL, allowing FSR3 to run
  • Implement some esoteric DXR features
    • Implement support for multiple mismatching global root signatures in DXR
      • Fixes crash in Battlefield V
    • Implement support for LOCAL_ON_EXTERNAL dependencies in DXR
      • Fixes DXR in Warhammer: Darktide
  • Implement support for ExecuteIndirect + Mesh shaders with state changes
    • Currently unused by games

Performance

  • Improve performance of NV_device_generated_commands and NV_device_generated_commands_compute by reordering and batching command preprocessing
    • We have observed 15% FPS gains in Halo Infinite on RADV
    • 1-2% in Starfield in some test locations
    • Needs pending Mesa work to land to take advantage of this improvement
  • Tune memory allocation patterns for DGC preprocess buffers
    • Avoids a lot of allocation churn
    • Greatly reduces CPU overhead on NV

Workarounds

  • Work around RADV bug causing GPU hang in RE4: Separate Ways DLC
  • Work around RADV bug causing GPU hang in Lords of the Fallen
  • Work around Witcher 3 bug causing broken shadows and GPU hangs when enabling DXR
  • Work around Cyberpunk 2077 bug when RT is enabled, where game would cause spurious GPU hangs due to accessing descriptor heap out of bounds
  • Work around Windjammers 2 bug causing random crashes on startup
  • Add support for VK_EXT_image_compression_control to allow for more fine-grained workarounds for broken games running on RADV
  • Enable NV_device_generated_commands_compute on latest NV beta drivers
    • 545.x drivers are still disabled until a fix can be confirmed on shipping drivers
  • Remove CURB_MEMORY_PSO_CACHE workaround on Mesa 23.2+
    • Should reduce overhead in PSO creation

Fixes

  • Misc dxil-spirv changes to fix various bugs in game shaders as usual
  • Fix Jurassic World Evolution 2 crashing when enabling DXR
  • Fix some deprecation warnings in Meson build system
    • Some submodule locations moved, which may cause minor disruption
[-] [email protected] 59 points 2 years ago

The important thing about RISC-V is that it's a completely open CPU architecture that could be competitive with ARM. It's arguably the best chance we have at performant computing hardware that doesn't spy on us or become useless after just a few years. We need this.

Blocking its development would be a big win for certain corporations, and a loss to basically everyone else. The AutoTL;DR bot didn't capture that side of the issue, but a quote in the article does allude to it:

"It would be like banning us from working on the internet," Kang said. "It would be a huge mistake in terms of technology, leadership, innovation and companies and jobs that are being created."

[-] [email protected] 57 points 2 years ago

I think a better title for your post would be, "Why do you use Steam?"

[-] [email protected] 73 points 2 years ago

I think the OP of that post would have had a better reception if they had:

  • Responsibly disclosed what they found, rather than using it to stir up drama on social media.
  • Mentioned that it's just a web forum account, not connected to game accounts or anything else of value.
  • Targeted the software vendor (https://www.ubbcentral.com/) instead of picking on one particular customer who used that software.
  • Refrained from spreading misconceptions and unfounded assumptions about how the technology works.
  • Responded to the reasonable follow-up questions, such as those that came when readers discovered that the problem was reported fixed three years ago.

People in that thread responded with skepticism and criticism to an irresponsible, misdirected, misleading, alarmist mess of a post. That's hardly surprising.

[-] [email protected] 75 points 2 years ago* (last edited 2 years ago)

More good news: There are lots of simpler hosts that are more deserving of your money than Jeff Bezos.

[-] [email protected] 71 points 2 years ago* (last edited 2 years ago)

Uh, Elon, did you just copy the X Window System logo?

[-] [email protected] 54 points 2 years ago* (last edited 2 years ago)

Key points off the top of my head:

  • Both Signal and Matrix have solid cryptography. (In fact, the Matrix Megolm protocol is built upon Signal's Olm protocol.)
  • Signal's client is open-source, but not its server. Matrix clients and servers are open-source. (Note that open server code is less important than open client code when end-to-end encryption is used.)
  • Both have had security audits, and presumably will have more in the future.
  • Both have cross-platform support. Matrix has a greater variety of clients, and last time I checked, the desktop clients were better than Signal's.
  • Signal prides itself on minimizing metadata exposure. Matrix started later, and hasn't yet moved all metadata (e.g. reactions, group membership?) to an encrypted channel. (Note that metadata protection can't ever be complete for either one of them, because an attacker that can gain access to the servers could just as well gain access to the routers, and correlate packets at the network level.)
  • Signal is a centralized service (hosted by Amazon last time I checked), meaning all traffic flows through one place and can be shut down or monitored there. Matrix is federated, much like Lemmy.
  • Signal does not offer self-hosting. Matrix does. (One might do this to be sure they always have a copy of their past messages, or to be independent of public server outages, or to be the sole keeper of data and metadata in conversations between local users.)
  • Signal requires a phone number, which makes having an anonymous account challenging for many people. Matrix doesn't require anything, but some Matrix servers require an email address for account recovery purposes.
  • Signal apparently integrates cryptocurrency payments. Matrix does not.

The most obvious security vulnerability that I can think of is that the person you are communicating with (or, conceivably, oneself, as well) is using an insecure/compromised application that may be leaking information.

Indeed, end-to-end encryption is unable to protect the endpoints. That's true of both messengers.

Since you brought it up, note that smartphones generally run system-level software that is controlled by the OS maker, meaning that Google or Apple have the ability to monitor those endpoints. Signal's approach to addressing this is to offer a Google-free build of their app, if you can find it, buried on their web site and with a scary-looking warning against using it. Matrix publishes their apps on F-Droid, so there's an easy Google-free option. Of course, most of the people using either messenger will have downloaded from the big app stores, so even if your phone and app are Google-free, it's likely that most of your contacts' phones are not. I believe Matrix has an advantage here, simply because their Google-free builds are easier to find and keep updated, and are therefore probably in use by more people.

[-] [email protected] 58 points 2 years ago

Highlights:

The crash started apparently out-of-the-blue, hitting thousands of Argentinian users on a Debian-based distro called Huayra, and specifically on version 5 which was based on Debian 10.

Everybody seemed to crash while searching for images on Google.

Google's code was allocating 20000 variables in a single frame.

view more: ‹ prev next ›

ono

0 post score
0 comment score
joined 2 years ago