Yesterday I read through 161 comments on a feature request of another project to find out what design considerations went into their implementation. Took me almost an hour. About a third of the comments didn't add any value and could have been skipped 😞
I wrote a short blog post on why as an open source maintainer I sometimes hide GitHub issue comments.
"A Warm Welcome to ASN.1 and DER" is a really nice introduction to the topic. It also gives a good idea of why writing a DER parser is so error-prone.
I just published an update to my library SafeContentResolver. After 4 years of nobody complaining about the API I went from version 0.9.0 to 1.0.0 🐌
I wrote a blog post about bugs in an Android class that you probably don't know and probably don't need to know: android.net.MailTo.
We've been asked if we could quickly implement new features in #Liberapay so that it could replace #Bountysource, which has been doing shady things. We can't and we don't want to. Encouraging people to pay for a specific issue to be solved is problematic, it creates bad incentives instead of providing stable funding for the proper maintenance and development of a project. If you still think bounties are a good idea, then you can try to revive https://freedomsponsors.org/
I am so happy that I chose #Namecheap as my domain host.
The POP3 support in @k9mail is bad 😢 I'm putting on some band-aids now. But I'm pretty sure we'll remove support for it in the future.
If you're using a POP3 account with K-9 Mail, now is a good time to switch to IMAP or to start looking for a different email app.
#bountysource changed their ToS such that bounties that have been posted more than 2 years ago will be seized by them (probably to fund the blockchain company that bought bountysource a while back). The change will become active July 1. If you have any bounties on bountysource posted before June 30, 2018 you can ask to redeploy your bounty on a new issue once.
@microg will no longer advertise the use of bountysource for issue bounties. Please refrain from posting new bounties there.
Blog post: What's up with K-9 Mail?
This is your periodic reminder that you shouldn't write new code in a memory unsafe language. And please try to migrate old code to a memory safe language. ❤️
…and the first user reported a bug caused by this. Should be easy to fix, though.
I usually like receiving bug reports from developers. They often know which technical information is important. When the app crashes, a stack trace is a very good starting point.
But please, PLEASE post it as text. Don't post a screenshot of the log window in your IDE. The issue tracker can deal with a couple of lines of text. It's not a social media site with a character limit 🤬
"Why not add an option for that?"
Open source developer, @k9mail maintainer. Berlin, Germany.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.