@kirby My guess is you'd have to catch them growling when they're playing as a puppy and just encourage it then eventually start playing with their snoot like that
@susie@lain@sun oof now I'm wondering if there was a rumor that holding it to your face increased your chance of getting COVID and that could be a reason why this behavior seemed to explode too
@sun@lain can someone please explain what the point is of holding your phone up to your face and shouting at it in public? Doesn't matter if they're indoors, in a hallway, the baby wing of the hospital, someone's funeral -- they don't give a fuck, they're just gonna shout at their phone having conversations that should really be private in front of the whole world.
Completely bizarre, and these people wonder how they become target of attacks and theft.
@joel@sun@soatok@david_chisnall@sophieschmieg Confirmed, the key in config.json is now encrypted by a password in the keychain so it's significantly harder to decrypt the messages database.
The attachments are still unencrypted. :sad:
Also I had this update installed when I deleted Signal in May and I didn't realize it. It was using a surprisingly weak password in the keychain, but a clean install produces pretty good passwords like this: qkfaZuxqKC2mDl8QCkzEzw==
So I'd say significant progress has been made here.
@anemone@mischievoustomato@sun technically Secretive can use a Yubikey like a SmartCard so you wouldn't even need gpg-agent but they added this functionality after I came up with my current solution and I have not investigated if it's good or compatible with the way my Yubikey is configured
@sun@anemone@mischievoustomato I use both Yubikey and Secretive, an app that uses the Secure Enclave to store your SSH key and then you can use your fingerprint to login. I have scripts to flip between which ones are active based on shell aliases, and autodetection of which it should activate based on whether or not the lid of the laptop is closed (docked mode for me) or if the Yubikey is inserted. Always prefer the Yubikey first, but without it and the lid closed I can still use my user account password to auth instead of my fingerprint.
# ~/.gnupg/gpg-agent.conf
default-cache-ttl 600
max-cache-ttl 7200
enable-ssh-support
pinentry-program /opt/homebrew/bin/pinentry-mac
# ~/.zshrc
alias gpgfix=". ~/bin/gpgfix"
alias secretive=". ~/bin/secretive"
# Lid open? Just use Secretive (TouchID is convenient enough)
# Closed? Use Yubikey if it's there,
# otherwise Secretive via password
(ioreg -p IOUSB | grep -q YubiKey)
YUBIKEY=$?
(ioreg -r -k AppleClamshellState -d 4 | awk '/AppleClamshellState/ {print $NF}' | grep -q Yes)
LID_CLOSED=$?
if [ "${LID_CLOSED}" -eq 1 ]; then
. ~/bin/secretive
elif [ "${YUBIKEY}" -eq 0 ]; then
. ~/bin/gpgfix
else
. ~/bin/secretive
fi
# ~/bin/secretive
#!/bin/sh
export SSH_AUTH_SOCK=/Users/feld/Library/Containers/com.maxgoedjen.Secretive.SecretAgent/Data/socket.ssh
# ~/bin/gpgfix
#!/bin/sh
killall ssh-agent
export GPG_TTY=$(tty)
gpg-connect-agent updatestartuptty /bye
unset SSH_AGENT_PID
export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket)
Pleroma made it possible to opt out of it with a user setting (not actually configurable in PleromaFE, lol???)
Around this time PleromaFE stopped showing the client. Twitter even went through this too after people were getting dunked on for their client choice, possibly hacked, harassed if a Google person posted a tweet with "Twitter for iPhone" or something showing up on the post.
Well, we opted out hard because due to a bug everyone has been opted out ever since the setting was implemented.
I'm guessing nobody really cares about the application/client data anymore. But it's supposed to be there, so I fixed it.
@taoeffect there exist people who only have meaningful friendships with people they've never seen or met and they only used text-based communications. So sadly, I think it can be your friend.