+bonifartius 𒂼𒄄 @bonifartius@qoto.org

Never expected that in less than a year after giving birth I'd feel this good. Virtues of the peasant diet and walking every day, I guess.

Feels like my husband and I have both upgraded through this experience - we're both thinner, fitter, healthier looking and happier than when we met and got married. It's an exciting idea that marriage and kids isn't the beginning of a decline into obesity and middle aged depression, but that you can change and grow together to become the best versions of yourselves so that you can serve and support your community and your faith.

Slacktivist!

Me and the boys after shipping malware to millions of computers

@allison@hidamari.apartments it's coming soon™ (like a year at minimum because i've never done something like this and have no clue what i'm doing ​:nkowoozy:​)

the plan is for it to be properly cross-platform, written entirely in go using a GUI toolkit that runs on Linux, macOS, Windows, Android, iOS, FreeBSD, and OpenBSD. i'm going to try to copy as much of telegram as i can because i think telegram hands-down has the best IM UX. i also want stickers and good voice/video calls.

properly using all the system APIs for voice/video calls will be a massive headache but i'm absolutely determined to make them work. i'm also going to look into supporting UnifiedPush but i'm fairly certain that requires support at both the server and client levels but we'll see.

it's a beeg undertaking but i'm tired of people hating on XMPP just because they don't like the clients

i also want people to be able to say "just install $APPNAME" instead of "well if you're on android, use conversations, on linux, use dino or gajim, on windows, use gajim or whatever the other thing was, on mac use siskin or snikket…". i'd also like a kind of welcome screen that gently introduces users to xmpp as a platform, goes over its capabilities, and gives the user a choice as to how they pick their server. the maintainers of this repo [0] extensively vet providers before adding them to specific categories. as the README says, category A is suitable for automatic selection. if the user wants a simple decision just based on domain, i'll surface those in category A and not show any of the "extra" information. if they want to know a bit more about the list, they can hit a toggle to expand provider details, showing things like backup policies and bus factor. that would also expand the list to include providers from category B. providers in category C will be auto-complete suggestions if they want to enter their own server at registration

[0]: https://invent.kde.org/melvo/xmpp-providers

after they register, maybe give them the option to interact with a fake user to get a feel for how OMEMO works, and after they're done with that, provide a toggle for blind trust or manual verification

it sounds like a lot but i want to keep the welcome crap down to like 4-6 screens at most with a button to skip the rest present throughout

@admcod "Our" democracy
This is Extremely Dangerous to Our Democracy.mp4

I make too much soup all the damn time and I want to give it to my friends 😤

Epic right side of history moment bruh xdddd

Zum Tagesausklang nun die japanische Nationalhymne.

https://www.youtube.com/watch?v=0K-5RkFEagc

@Data
😆
https://nitter.unixfox.eu/spriter99880/status/1504093415616696322#m

Hilarious system propaganda

"...calling for peace, and a No Fly Zone."

@Hibou
AND WHAT HAVE I BECOME
MY SWEETEST FRIEND
EVERY THREAD I MAKE
TURNS TO HELL IN THE END

@Sophistifunk you can remove "like"

And also the first comma.

I'm on side "none of my fing business"