Skip to main content


Are there any software projects that people would be willing to pay a small weekly or monthly contribution to support me while I develop it? I need a way to feed my family, and I don't like asking for handouts.

Please respond with ideas of things you'd like to see exist, that you'd maybe be willing to contribute an ongoing nonzero amount towards, and boost for reach. If you don't have idea of your own, that's fine. Boosting will still help!

#FediHired
#OpenSource
#Python
#MachineLearning
#Data
#Reporting
#BackendDeveloper

This entry was edited (4 days ago)
in reply to Aaron

My primary flossy software fantasy is a mail server RFC (and index implementation) which integrates e2ee as a requirement. And a mail client which implements it transparently.
in reply to Amgine

@Amgine I've worked with email protocols, etc., but it has been many many years! I bet I'd have to learn it over again
in reply to Aaron

@Amgine Well. You'd need to be a bit more precise.

There exist RFCs for protocols that work Email-like and are e2ee, but they're not implemented in Email clients.

They're also a bit more generic. You can use them for mail, but also other stuff.

in reply to Jens Finkhäuser

@jens
I am likely lacking the knowledgebase to explain my goals properly, but here's what I would like:

Email server RFC clarification:
Email messages where subject, contact, & attachments are not in standard encrypted blobs are rejected as malformed. In other respects it should conform to existing email server standards.

Requiring encryption forces clients to use it by default, and should cause evolution in the market toward transparency for UX.

in reply to Amgine

@jens
We do not require users to understand ASCII/Unicode representation, used to encode their emails / im / text now. In the same manner we can make encryption invisible to people sending emails.
in reply to Amgine

@Amgine Well, if you encrypt the recipient, nothing with Email will continue to work.

So then, why remain attached to compatibility?

in reply to Jens Finkhäuser

@jens
Heh, that was likely an error on my part.

Compatibility is useful for adoption. Email predates internet. It has steadily evolved, but relatively slowly and is resistant to change, yet it now uses 8-bit bytes (among many other changes I have witnessed.)