@unixorn@hachyderm.io2025-12-26 23:09:04
Last month I switched from Google Workspace to proton.me for hosting email for my domains.
It went smoothly, but if you're considering it, here's some things I wish I'd known when I was starting to move my old email.
#protonmail #google_apps #google_workspace
@hanno@mastodon.social2026-02-18 06:26:20
If you manage your code on Github, you might expect that you get an email notification if someone opens an issue for your code. But it appears that's no longer true for new repos.
The "Watch" settings are now, by default, "Participating and Mentions". That means unless someone tags your Github username in the issue report, you won't know about it. Yeah, even if it's your own repo in your own namespace. No, I don't know what they were thinking at Githu…
@ErikJonker@mastodon.social2026-02-08 19:06:40
“4% of GitHub public commits are being authored by Claude Code right now. At the current trajectory, we believe that Claude Code will be 20% of all daily commits by the end of 2026. While you blinked, AI consumed all of software development.”
Must-read article, even if you can disagree with the analysis
@joe@toot.works2025-12-04 20:02:17
I just got an email from a GitHub issue saying ...
So... our backlog of brand requests has reached a point where even we can't pretend we're keeping up. Some of these issues were opened before I had gray hair. And I've had gray hair for a LONG time. On top of that, treating requests as issues has always made it way too hard to see the forest for the trees.
To fix this, we are now managing all brand requests in GitHub Discussions.
... Fair enough, I guess.
@gla@mastodon.social2025-12-30 09:50:19
Bitbucket recently announced shutting down inactive workspaces.
I logged there, and my Ph.D stuff (mostly papers, some Python) were all there.
To preserve them, I asked #Copilot to write a script to move them to GitHub.
If you want to admire the slop, there’s now a post about it
@domm@social.linux.pizza2026-01-03 14:34:39
Today I tried to get our new Hetzner mailbox to work with gitlab issues, but failed. I blame Hetzner, because a) they don't seem to support subaddressing (foo 123@example.com) and b) they don't set the proper mail header (Envelope-To and Delivered-To) when doing a mail forward. Both of which work for example with mailbox.org, and both are needed to allow issue creation via email in gitlab (what they call Service Desk). Grrr...
@teledyn@mstdn.ca2025-12-01 18:11:21
so
very
frustrating
#Gnome #Evolution how is this even possible? Fresh #Debian13 install, launched, added my google workspace, read and answered email, browsed calendar, really nice, but the VERY NEXT MORNING suddenly tossed into OAuth2-is-missing, step through the 'wizard' and it always ends with the same heartache, are you trying sign in? and then…
Mail authentication (shown) gives a URL to a page, Make sure you trust Gnome (4 perms already granted, Google console agrees) but in Firefox that URL asks to confirm and then reverts to google.com. In the minibrowser, it gets to "Requesting access token, please wait"
And wait you do.
How is this even POSSIBLE? What could cause it to (a) drop an OAuth2 overnight that had been in use for a day and (b) subsequently give a URL that does not result in an access token. I removed permissions on the Google side, but same results. Reinstalled Evolution, no change
yes, I checked gitlab.gnome.org
@luana@wetdry.world2026-02-19 13:43:05
This is what I used to run icloudpd, if anyone needs it. If using --xmp-sidecar you’ll also need to use a patched version of the program: https://github.com/icloud-photos-downloader/icloud_photos_downloader/pull/1290
Run with --list-libraries so you can see all your libraries other than PrimarySync, you’ll have a second one if you have a shared iCloud library. Run that command one (or as many times as needed to completely succeed) time for each library.