mox

joined 1 year ago
[–] mox@lemmy.sdf.org 2 points 1 day ago* (last edited 1 day ago)

Good luck. You'll find that your farmed accounts can't do much of anything, and will be quickly and automatically deleted.

[–] mox@lemmy.sdf.org 1 points 1 day ago (1 children)

I have been happy with the Sony controllers. They're comfortable, have relatively small dead zones, and are still working well after more than a few years of use. Both the DualShock 4 v2 and the DualSense are supported by Steam Input, can be used on Windows, and have native support (from Sony!) in the Linux kernel.

[–] mox@lemmy.sdf.org 19 points 1 day ago* (last edited 1 day ago) (3 children)

What will be effective depends on the nature of the site and that of the bots causing trouble. For example, a forum can limit posting privileges until an account builds a reputation, a paid goods/services site can restrict access until a purchase is made, a web service can use revocable credentials, and a data download site can use rate limits. (That last one is actually useful in a variety of situations, and can be done at the network level instead of or in addition to the application level.)

There is no silver bullet, but there are lots of small measures that can be very effective when applied thoughtfully, without turning a site into a frustrating-to-use surveillance tool for Google at the expense of the humans who want to or have to use it.

Even a small, locally hosted, activate-only-once, simple image or text-based CAPTCHA would be preferable to the ones operated by third parties.

[–] mox@lemmy.sdf.org 9 points 1 day ago* (last edited 1 day ago)

There's no point in arguing what once was. Things have changed. CAPTCHAs are now less effective, far more invasive, and for many people, far more troublesome.

Cling to them if you like. I no longer use them on any of my sites, because I care about my users.

[–] mox@lemmy.sdf.org -5 points 1 day ago* (last edited 1 day ago) (7 children)

CAPTCHAs make web sites awful to use, and waste the limited lifespans of billions of people.

There are other ways to manage bots.

 

Not just tracking cookies, but browser fingerprinting.

Not just Google, but now Cloudflare.

[–] mox@lemmy.sdf.org 3 points 1 day ago

I must say I e never played Skyrim, and I didn’t know how beautiful it could be.

Modern texture packs, replacement models, and lighting mods make it even more so.

On top of that, Skyrim's soundtrack is outstanding, and conspires with the scenery to make it a game world not easily forgotten. I'm sure I'll be going back.

[–] mox@lemmy.sdf.org 51 points 2 days ago (1 children)

Farm income has dropped 23% from 2022 in one of the biggest declines in history, according to the USDA, and the American Farm Bureau says the agricultural economy is in a recession.

Even while grocery prices have risen to painful heights. It's almost as though there's something between the people who supply the food and those who pay for it, taking more than their fair share.

[–] mox@lemmy.sdf.org -3 points 2 days ago* (last edited 2 days ago)

Indeed. Tucked away in a corner of their web site, where it isn't easy to find unless someone else guides you to it, below a large bold warning that discourages people from actually using it:

Danger zone

Advanced users with special needs can download the Signal APK directly. Most users should not do this under normal circumstances.

This ensures that nearly nobody uses that build. Consequently, almost all chats on Signal will have an app store build running on at least one endpoint.

[–] mox@lemmy.sdf.org -2 points 2 days ago* (last edited 2 days ago)

It's not false.

Signal's default, well-supported installations use Google services, so unless you're an extremely atypical user, those services are present on most of your contacts' devices. You might have the knowledge, skill, and motivation to remove those services from your own device, but since they're still present at the other end of most chats, you haven't escaped them.

Let's also remember that E2EE doesn't protect the endpionts, and that Google Play Services run with system-level privileges.

[–] mox@lemmy.sdf.org 2 points 2 days ago* (last edited 2 days ago) (7 children)

It’s been recently added to FDroid.

No, it has not. A third party published it in an f-droid compatible repository. That might be convenient for someone who happens to trust that third party and manually add it to their F-Droid client, but it is not at all like it being added it to F-Droid.

You can use NTFY with Molly (which has been on FDroid for some time).

This does not refute what I wrote. Unless you only communicate with people who get their Signal app from some non-Google source and they all rig up alternative push notification channels, or every one of them uses Signal exclusively on iOS, your conversations are still tied to Google. Perhaps you have so few contacts that you could achieve that, but most people are not in that position.

network-level metadata monitoring by anyone with sufficient access/influence at Signal or their data center provider (such as a government who doesn’t like encrypted messaging).

This one is just a straight-up lie. Everything on the server is encrypted and no one has the keys except the participants.

Encryption doesn't hide network traffic. Signal's centralised design means there is a single point where that traffic can be monitored and traced to reveal which endpoints are talking to each other, and where, and when.

What I wrote is not a lie, which you would know if you actually understood these issues. Please stop making baseless accusations. You are wrong, and you are being very rude.

If you're interested in correcting your ignorance, I suggest starting with this paper, which touches on some of the issues:

https://www.ndss-symposium.org/ndss-paper/improving-signals-sealed-sender/

If the paper is too much for you, the linked video does a pretty good job of explaining.

 

What's new in this release:

  • A wide range of changes that were deferred during code freeze.
  • Root certificates fixes for Battle.net.
  • Print Provider improvements.
  • More progress on the Bluetooth driver.
  • Various bug fixes.
[–] mox@lemmy.sdf.org 4 points 3 days ago* (last edited 3 days ago)

Thankfully, it's not that simple.

A centralised service is an easy target for a government. (This is where Signal stands.) A decentralised one is significantly harder, because the government would have to be constantly discovering and processing every node in the network as new ones appear. (This is where Matrix stands, although it doesn't have many public servers yet.) Fully peer-to-peer decentralisation makes it harder still, because there are as many nodes as there are users, with network addresses that often change. (Some of these exist today, but are mostly experimental with few users. Matrix has done some proof-of-concept work in this area as well.)

On top of decentralisation, tunnels like VPN and Tor can be helpful in avoiding ISP-imposed blocks.

 

I haven't used this yet, but the design described in the readme makes it look very convenient compared to the usual array of tools required.

 

I haven't used this yet, but the design described in the readme makes it look very convenient compared to the usual array of tools required.

 

Error description: "Something went wrong with a file."
Error code: BLZBNTAGT00000840

A workaround that succeeded at least once for me: Use GE-Proton9-23, or kron4ek-wine-10.0-staging-tkg-amd64 from the Bottles project.

Details:

  • GE-Proton can be either the one obtained from GloriousEggroll (which is made for use within Steam), or the one obtained from the Bottles project (for use without Steam). The Bottles kron4ek-wine-10.0-staging-tkg-amd64 download location is posted here. Bottles runners are described here.
  • The next update after I switched to GE-Proton9-23 brought a new error: BLZBNTAGT00000846, which (according to Blizzard's web page) means, "We tried to make a file writable but failed. Please log in as an administrator and try again." I would usually say that doesn't make much sense in Wine, but Wine 10.0 apparently includes some administrator access support, so perhaps that could help. I got around this by switching to wine-10.0-staging-tkg-amd64 from the Bottles project, and using Battle.net's Scan and Repair option on the game. I'm not sure if the fix was the Scan and Repair, or the newer Wine build, or something in the Wine prefix getting reset when a new Wine version was detected, or some time passing between the error message and trying to launch it again (which could hint at a certificate timestamp problem), or some combination thereof. In any case, the next Blizzard update after that worked fine.
  • I briefly thought that setting the Wine prefix's Windows version to Windows 11 helped, but I have been unable to confirm it. For the record, this can be done on the winecfg Applications tab, or by running winetricks win11. Note that it requires a fairly recent version of Wine (and winetricks if using that method) so it might require temporarily upgrading Wine/Proton in order to choose that option. Battle.net might lose your saved password if you do this, in which case you would have to log in again.
  • Once the games are updated, returning to the previous Wine version should be safe, at least until a better solution is found.

Alternative approach:

Mert Eren on the Codeweavers forum relayed another workaround. Summary: The problem apparently lies in the latest version of the Battle.net "Agent" program. If your installation is old enough to still have the previous Agent version installed, it is possible to remove the new one and block it from being reinstalled, relying instead on the old version to update your games and make them playable.

CodeWeavers are investigating for the sake of their customers, but have not yet announced a fix.

Ongoing discussions:

https://us.forums.blizzard.com/en/blizzard/t/cant-updateinstall-due-to-blzbntagt00000840/53551

https://us.forums.blizzard.com/en/wow/t/couldnt-update-after-111-now-cant-install/2044960

https://old.reddit.com/r/linux_gaming/comments/1i1on1i/unable_to_update_world_of_warcraft_retail_error/

view more: next ›