Does he already not have the opportunity, robot or not?

Yeah, with mpv you can even hold the jump 10/60 sec forward/backward button pressed and the frames just fly in the screen. Vlc seeking is really slow in comparison.

They presumably assume they’d be selling so little that it wouldn’t be worth the trouble.

They’ll probably wait out this situation for a while and see what the competition does…

If you just do it on your own computer, the packet will be already dropped by your own gateway. You can fake whichever address in your local subnet, but those are very likely remapped anyway in your gw to the one given by your ISP.

If you would have access to the switch port used by your ISP in the Internet exchange point (IX), you would have more liberties in choosing the IP.

That’s a bit surprising, given DDG uses Bing, Bing is Microsoft and Microsoft owns Github.

Did you try the same search with Bing, or have an example to share?

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.

That’s pretty low bar for calling something a “quirk”. The whole ML family, so OCaml, SML, Haskell, F# and perhaps a the new distant relative Rust call it also it None.

And it’s not even the same thing: null means pointer to nothing, while None means no value.

How is None a quirk?

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?

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 highly doubt businesses would have been this fast in making the switch.