Incoming links: Gmail
Ciro Santilli is very happy to meet people with related interests, he really loves his like-minded online friends. Even if you don't have something a specific goal in mind for the contact, please just say hi.
To contact Ciro publicly about any general subject that is not covered in a more specific GitHub repository, including saying hi or suggestions about his website either:
- create a GitHub issue at: github.com/cirosantilli/cirosantilli.github.io/issues/new or Giscus thread
- at mention Ciro's main Twitter account
For comments about China, first read:
and then create a GitHub issue at: github.com/cirosantilli/china-dictatorship/issues/new
Publicly viewable contact is preferred if possible to more effectively share Ciro's wisdom with the world.
But if you feel more comfortable with private contact, no problem, either:
- email:
cirosantilliwith provider ProtonMail which has domain nameproton.me. All lowercase and removing the placeholder characters<and>. Note that Ciro also controls the Gmail address with that same username, and keep in mind that dots are ignored in Gmail addresses. But ProtonMail preferred because why should we give our private minds to the CIA by default? Push notifications disabled. - Signal: username
cirosantilli.89signal.me/#eu/BuJjV0enXYTOnFFc1FZV5LFcWodL1a2Oy9VZ5uyQU7xrYxqw+npIcaHBqghWudrI. 89 is a reference to Ciro Santilli's birth year 1989. Push notifications enabled, but treat like email unless we are actively chatting back and forth.
For other less good methods that will also work, use direct messages of the following profiles from under Section "Accounts controlled by Ciro Santilli":
- LinkedIn: www.linkedin.com/in/cirosantilli
- Reddit: www.reddit.com/user/cirosantilli
- Facebook: www.facebook.com/cirosantilli
- Telegram: telegram.me/cirosantilli. Note that end-to-end encryption is present on secret chats only, which don't have device sync. Ridiculous.
If you are a privacy freak or are going to tell Ciro state secrets Ciro has this GNU Privacy Guard public key: pubkey.gpg.
Disqus comments were removed from his website in 2019-05-04, a manual dump is available here, removal rationale at: why Ciro Santilli removed Disqus comments from his website in 2019-05-04.
It boggles Ciro Santilli's mind that people use mailing list to collaborate on projects!
The only explanation is that the dinosaurs who created the projects are unable to adapt to new superior technologies.
Yes, Ciro is talking to you, big fundamental projects from last century: Linux kernel, GNU Compiler Collection (gcc.gnu.org/lists.html), Binutils (sourceware.org/binutils/), etc.
Some of you are already using Bugzilla for the bugs, so kudos. But if you've seen their benefit, why you still use the mailing list for patches?
Advantages of mailing lists:
- threaded replies, which almost no issue tracker has. GitHub feature request: github.com/isaacs/github/issues/837
Disadvantages: everything else:
- cannot subscribed to a single thread. Which forces you to create an email filter for each one of them you subscribe to.
- no metadata, notably the notion of closing / merging, but also upvotesYou have to read thirty messages before you can know if the bug was solved or not.
- it is insanely hard to reply to messages from before you were subscribed: webapps.stackexchange.com/questions/23197/reply-to-mailman-archived-message/115088#115088This forces everyone to subscribe to all lists, and then set up email filters to not be flooded with emails.
- hard to apply patches locally to test them out: stackoverflow.com/questions/5062389/how-to-use-git-am-to-apply-patches-from-email-messages/49082916#49082916Unless they use Patchwork, which adds one more website on top of the mess.And then Gmail corrupts your patches, and you are forced to use
git send-email, which does not work on some network configurations: stackoverflow.com/questions/28038662/how-to-solve-unable-to-initialize-smtp-properly-when-using-using-git-send-ema or setup ThunderBird. - often have to subscribe to post at all, thus cluttering your inbox further
- you can edit posts to make them clearer.Yes, people could vandalize their answers when they get mad, and threads might stop making sense after edits. But this can be solved with an undeletable post history like Stack Overflow has (but not any other tracker does).Or archive.org :-)In any case, what do you think will happen more often and have greater impact:
- people vandalize their posts
- people fix their silly typos and improve content
- searchable by author, keyword, etc. without Google. Yes, mailing list trackers could have decent implementations to overcome that. But no, GNU Mailman which everyone uses does not have it. Google barely indexes it.And I don't think Google properly indexes many of the mailing list archives for some reason: I never get hits for my own posts a week later, while I often do on GitHub issues.
- people have to learn about top posting vs inline posting, and this requires infinite education of new users
- Line comments in code reviews like GitHub and GitLab.On mailing lists: either put a comment in the middle of a huge patch and let other people find it, or (more likely) copy paste the part of the patch that you are talking about.
- most mail web UIs suck.OK, this is not an unsolvable or intrinsic problem, but still a problem.E.g.:
ezmlmit is not possible to see the entire content in a single page: gcc.gnu.org/ml/gcc/2015-07/threads.html.Unless you like reading threads backwards and with 4 levels of>quotations.The alternative: do like LLVM and send attachments. Yes, I we all love opening up attachments on our browsers.The real solution: everyone can create branches and pull requests. Also has the benefit of running CI on the pull requests.
Not sure:
- you can have infinitely many trackers to replicate data in case apocalypse happens in some part of the world.Although I'm not sure this is an advantage, as you don't know anymore which one is the canonical trackers an advantage, as you don't know anymore which one is the canonical tracker.And all web interfaces already have an API to export messages, and someone has already scripted it to import from any web UI to any web UI for you.And GitHub offers infinite precise history transparently on its API.
The first one Ciro Santilli managed to get working in 2022, and which has a free plan.
You can either verify your sending domain by adding 3 DNS records.
Saw the email on Gmail, but Microsoft Outlook did put it into junk though. Yahoo mail also worked fine.
100 emails a day is not insane, but it is forever and appropriate for a test, I'm happy with that.