Did you give it to it?

It can be a pretty nice feature for using map-based apps in the browser.

I haven’t used such websites for a while and I don’t see Firefox in the recent users of the location API, even though I use Firefox Android all the time. (Info available in Android under Settings/Location.)

And did mentioning these things just make the message disappear on US-based lemmy-instances?

I don’t believe it did.

Perhaps many, but I have over 500 accounts in my password manager, yet none of have been leaked per the password exposure report (which I assume is based on the https://haveibeenpwned.com/ database).

So perhaps the problem is overblown in practice, assuming you don’t use the same password in many sites.

Realistically, how often does this happen?

Maybe find a solution when it happens.

Well, except perhaps for the fact that Discord has a Linux version, while the Facebook App doesn’t.

And—clearly!—it seems rather popular as well.

Right on! People should only share news articles that pertain to my interests.

Where should they be “taking” funding instead?

Alas my game PC is going to stick with Windows due to bad state of VR in Linux :/. And therefore one day it might need to update to Windows 11.

In particular if you have a headset that is not Valve Index, though apparently with Meta Quest one can use ALVR, as long as you get the actual games running.

Maybe consider static ip assignment in your DHCP server (e.g. internet router) if at all possible… Then you can add a name to it to /etc/hosts.

Alternatively you could use Avahi to provide mdns names to your local network

Do you have that file? If not, then unset SSH_AUTH_SOCK will work just as well.

If it does exist, then I suppose it has good chances of working correctly :). ssh-add -l will try to use that socket and list your keys in the service (or list nothing if there are no keys, but it would still work without error).

At the end of the log you find:

822413 connect(4, {sa_family=AF_UNIX, sun_path="/run/user/1000/gcr/ssh"}, 110) = 0
...
822413 read(4, 

meaning it’s trying to interact with the ssh-agent, but it (finally) doesn’t give a response.

Use the lsof command to figure out which program is providing the agent service and try to resolve issue that way. If it’s not the OpenSSH ssh-agent, then maybe you can disable its ssh-agent functionality and use real ssh-agent in its place…

My wild guess is that the program might be trying to interactively verify the use of the key from you, but it is not succeeding in doing that for some reason.

I guess it’s worth checking if those names point to the expected binaries, but I also think it would be highly unlikely they would be anything else than just /usr/bin/ssh and /usr/bin/ssh-agent.

As mentioned, -v (or -vv) helps to analyze the situation.

My theory is that you already have something providing ssh agent service, but that process is somehow stuck, and when ssh tries to connect it, it doesn’t respond to the connect, or it accepts the connection but doesn’t actually interact with ssh. Quite possibly ssh doesn’t have a timeout for interacting with ssh-agent.

Using eval $(ssh-agent -s) starts a new ssh agent and replaces the environment variables in question with the new ones, therefore avoiding the use of the stuck process.

If this is the actual problem here, then before running the eval, echo $SSH_AUTH_SOCK would show the path of the existing ssh agent socket. If this is the case, then you can use lsof $SSH_AUTH_SOCK to see what that process is. Quite possibly it’s provided by gnome-keyring-daemon if you’re running Gnome. As to why that process would not be working I don’t have ideas.

Another way to analyze the problem is strace -o logfile -f ssh .. and then check out what is at the end of the logfile. If the theory applies, then it would likely be a connect call for the ssh-agent.

I think the main problem is that Chromium still contributes towards the browser engine monoculture, as it is bug-for-bug compatible with Chrome. Therefore if you switch to Chromium, it’s still enough for the web sites to test for Chrome compatibility, which they will, because it has the largest market share. Users of competing browsers suffer, further driving the lure of Chrome (or Chromium).

On the other hand, if people switched to some other engine, one that does not share the same core engine or even the same history, this will no longer hold: web sites would need to be developed against the spec, or at least against all the browsers they might realistically expect their customers to use.

I highly doubt businesses would have been this fast in making the switch.

Well that’s exactly the worry. Why shouldn’t it be? It is their business and livehood.

Moving away from Discord can mean you need to stop interacting with the community using it. My personal examples are: Tilt5, Makera, Turbo Sliders. In the these cases Discord is also the way to access support for something you’ve paid for.

Getting thise communities to move into something open (e.g. Matrix) can be a tall order.

Boox Tab Ultra

Looks pretty nice device! Even the camera makes a bit sense in the demo they give (though apparently in practice the scanning rarely works). And cheaper to boot as well. I might consider getting this one.

But is the display really better quality? Atleast the DPI is slightly higher at 219 on the Boox Tab Ultra vs 190 on the Daylight. And Boox weighs 70 grams less, and that’s the device some reviews call heavy (and some lightweight…).

These reviews mention the slow display speed:

• https://www.xda-developers.com/boox-tab-ultra-review/
• https://www.techradar.com/reviews/onyx-boox-tab-ultra-review-an-e-ink-peg-in-an-ipad-hole even goes to describe it “distracting” and “Performance can’t keep up with fast typing”
• https://www.trustedreviews.com/reviews/onyx-boox-tab-ultra “Tab Ultra does let you choose between several refresh modes” and https://www.makeuseof.com/onyx-boox-tab-ultra-review/ "The HD preset works fine for casual reading, whereas the balanced mode works better when thumbing through documents or typing. Meanwhile, the fast mode is suggested for general website browsing, and ultrafast is more useful for video playback. "—surely if the display was always fast and working, this fidgeting would be pointless?

So perhaps there is some room for improvement? That being said, some other reviews don’t mention it and one says it’s faster than typical e-ink display, though that doesn’t sound immediately purely praising.

In the end it probably comes to the software: how fast it is, it well it works, how nice it is to use. It seems both have customized the standard Android, so I suppose the difference is in which one has done it better and which one has better custom apps. Per the reviews Boox doesn’t fare too well in this aspect. Maybe someone will make a comparative review of the devices.

As opposed to buing a separate display for the computer?

I like to think this thing would be nice reading the news while having a breakfast or reading an e-book outside or at the bed, not near my computer. So it makes a lot of sense to build a tablet with this display technology.

Zooming and panning a pdf is arguably more comfortable with higher frame rate.