movq

www.uninformativ.de

No description provided.

Recent twts from movq
movq
www.uninformativ.de
 (5d ago)
↳ In-reply-to » For the record, the third thing is to activate agent forwarding. In ~/.ssh/config:

@lyse@lyse.isobeef.org Hm, I’m not sure I would want to do that:

ForwardAgent
    ...

    Agent forwarding should be enabled  with  caution.   Users
    with  the ability to bypass file permissions on the remote
    host (for the agent's Unix-domain socket) can  access  the
    local agent through the forwarded connection.  An attacker
    cannot  obtain  key  material from the agent, however they
    can perform operations on the keys that enable them to au‐
    thenticate using the identities loaded into the agent.

⤋ Read More
movq
www.uninformativ.de
 (5d ago)
↳ In-reply-to » Anyone else having trouble pulling from git.mills.io? 🤔

@lyse@lyse.isobeef.org Changing the user name helped, it now says Authenticated to git.mills.io ([199.247.16.95]:2222) using "publickey". ssh-add ... had no effect (even after ssh-add -D).

Here’s a debug log, @prologic@twtxt.net, perhaps you could take a look at this 🙏: https://movq.de/v/116c5f514b/clone2.txt

(Might be a silly mistake on my part. Wrong remote path or something?)

⤋ Read More
movq
www.uninformativ.de
 (6d ago)

Anyone else having trouble pulling from git.mills.io? 🤔

$ g clone ssh://git@git.mills.io:2222/yarnsocial/twtxt.dev.git
Cloning into 'twtxt.dev'...
git@git.mills.io: Permission denied (publickey).
fatal: Could not read from remote repository.

The key verification function on https://git.mills.io/user/settings/keys says I’m using the correct key.

This also looks good:

$ GIT_SSH_COMMAND="ssh -v" g clone ssh://git@git.mills.io:2222/yarnsocial/twtxt.dev.git
...
debug1: Authentications that can continue: publickey
debug1: Offering public key: /home/user/.ssh/keys/key-millsio ED25519 SHA256:nVNT... explicit
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
git@git.mills.io: Permission denied (publickey).
fatal: Could not read from remote repository.

Does it work for you, @lyse@lyse.isobeef.org @prologic@twtxt.net?

⤋ Read More
movq
www.uninformativ.de
 (1w ago)

Now that Winter has come to an end, I’m realizing that the default amber color scheme of my widget toolkit might be problemaic.

Image

Readability isn’t great when the sun is blasting through the windows. 🥴

I should probably make this full themeable by the user …

(Haven’t worked on this code in a month, sadly.)

⤋ Read More
movq
www.uninformativ.de
 (1w ago)
↳ In-reply-to » Last year, I made a huge mistake. I repeated on here, what multiple sourcea at Google told me, and what is to this day, written on their blog about Android. I failed to take into consideration, that people who work at Google, often just lie, or present things intentionally vaguely, so they do not have to follow through with their promises. I would like to apologize to everyone, who took my previous posts here, as assurance software not explicitly approved by Google, will continue working on Android, past this year (or even just a couple months from now) and that everything has been resolved, as things are now in fact even worse, than they were before. To follow the current state of "Open Android", please check: https://keepandroidopen.org/

@thecanine@twtxt.net

as things are now in fact even worse

You mean this, right?

Contrary to a vague mention of a possible “advanced flow” that may eventually allow “experienced users to accept the risks of installing software that isn’t verified”, Google’s description of the program continues to state plainly that:

Starting in September 2026, Android will require all apps to be registered by verified developers in order to be installed on certified Android devices

Until such time that they have shown evidence that it will be possible to bypass the verification process without undue friction, we must believe what is stated on their official page: that all apps from non-registered developers will be blocked once their lock-down goes into effect.

⤋ Read More
movq
www.uninformativ.de
 (1w ago)
↳ In-reply-to » RIP Vim 😢 https://hachyderm.io/@AndrewRadev/116175986749599825 https://github.com/vim/vim/pull/19413#issuecomment-4000394026

@prologic@twtxt.net So many people calling this thing “he” and saying things like “I had a discussion with him” or “he explained his reasoning”, it’s mind boggling. Nobody even questions it anymore.

⤋ Read More