101 lines
6.5 KiB
XML
101 lines
6.5 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
|
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
|
<channel>
|
|
<title>Aravinth Manivannan on </title>
|
|
<link>/contributors/aravinth-manivannan/</link>
|
|
<description>Recent content in Aravinth Manivannan on </description>
|
|
<generator>Hugo -- gohugo.io</generator>
|
|
<language>en-US</language>
|
|
<lastBuildDate>Wed, 26 May 2021 00:00:00 +0000</lastBuildDate><atom:link href="/contributors/aravinth-manivannan/index.xml" rel="self" type="application/rss+xml" />
|
|
<item>
|
|
<title>February, 2023: Monthly Report</title>
|
|
<link>/blog/february-2023-monthly-report/</link>
|
|
<pubDate>Wed, 08 Mar 2023 00:00:00 +0000</pubDate>
|
|
|
|
<guid>/blog/february-2023-monthly-report/</guid>
|
|
<description>Hello and welcome to the (August 2022 to) February, 2023 monthly report!
|
|
TL;DR Gusted and I secured funding from NLnet to work on mCaptcha in 2023, we suffered an outage from 15 January to February 6, polyfill benchmarking support in mCaptcha
|
|
We have funding! Gusted and I applied and secured funding through 2023 development is funded through the NGI0 Entrust Fund, via NLnet.
|
|
The full list of tasks that we&rsquo;ll be working on in the period is is available here.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>July, 2022: Monthly Report</title>
|
|
<link>/blog/july-2022-monthly-report/</link>
|
|
<pubDate>Thu, 04 Aug 2022 00:00:00 +0000</pubDate>
|
|
|
|
<guid>/blog/july-2022-monthly-report/</guid>
|
|
<description>Hello and welcome to the July, 2022 monthly report!
|
|
TL;DR Codeberg is trying out mCaptcha, Gitea is getting mCaptcha support, mCaptcha supports MariaDB, I&rsquo;ve applied for NLnet and Open Tech Fund, documentation is updated: tutorials and glossary is added and glue libraries have new releases.
|
|
Codeberg is deploying mCaptcha Codeberg is committed to trying out mCaptcha to make their platform more accessible: they currently use a text-based CAPTCHA, which will be replaced by mCaptcha.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>June, 2022: Monthly Report</title>
|
|
<link>/blog/june-2022-monthly-report/</link>
|
|
<pubDate>Thu, 07 Jul 2022 00:00:00 +0000</pubDate>
|
|
|
|
<guid>/blog/june-2022-monthly-report/</guid>
|
|
<description>Hello and welcome to the June 2022 edition of the monthly report!
|
|
mCaptcha is incorporated! I spent June doing non-technical tasks but I made significant progress: I had been trying to do it since summer 2021, but I faced various setbacks along the way. A family friend, who is also an auditor helped me finally get mCaptcha incorporated!
|
|
And we&rsquo;ve already filed successfully filed the first tax return too!
|
|
GSTIN 33DGKPA2253J1ZN Ideas for Commercial Operations Commercial operations will take a while longer(end of 2022, most probably).</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>May, 2022: Monthly Report</title>
|
|
<link>/blog/may-2022-monthly-report/</link>
|
|
<pubDate>Fri, 10 Jun 2022 00:00:00 +0000</pubDate>
|
|
|
|
<guid>/blog/may-2022-monthly-report/</guid>
|
|
<description>Hello and welcome to the May 2022 edition of the monthly report!
|
|
mCaptcha, for a while was showing all the signs of a dead project: no commits on the repositories and no monthly updates. But the project is far from dead!
|
|
Python bindings to mCaptcha PoW pow_py contains bindings to pow_sha256, the proof-of-work library that mCaptcha uses. For the uninitiated, the bindings allow for python programs to automatically solve mCaptcha.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>December, 2021: Monthly Report</title>
|
|
<link>/blog/december-2021-monthly-report/</link>
|
|
<pubDate>Thu, 23 Dec 2021 00:00:00 +0000</pubDate>
|
|
|
|
<guid>/blog/december-2021-monthly-report/</guid>
|
|
<description>Hello and welcome to the first edition of the monthly report!
|
|
I believe free software like mCaptcha is critical to a healthy internet but being a one-person show, there&rsquo;s hardly any accountability in the way software is built. I hope, through monthly reports, I can explain the logic and intentions behind decisions taken in the development process.
|
|
This month, the following things were accomplished:
|
|
1. Full LibreJS Compliance The CAPTCHA widget and the admin dashboard are 100% LibreJS compliant!</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Survey</title>
|
|
<link>/blog/survey/</link>
|
|
<pubDate>Thu, 28 Oct 2021 00:00:00 +0000</pubDate>
|
|
|
|
<guid>/blog/survey/</guid>
|
|
<description>Survey link: https://survey.mcaptcha.org/survey/campaigns/b717e51e-24d4-4ab6-912f-de2dfe3ce1fe/about
|
|
NOTE: The survey(at least, the lucky draw is temporarily suspended due to some logistical reasons. Apologies for any inconvenience caused.
|
|
mCaptcha relies on a proof-of-work(PoW) mechanism to guard against bots. In order for this to be effective, the difficulty factor should be configured properly. If the difficulty factor is too high all the time, it will inconvenience the users and if it&rsquo;s too low during attack, the defence will be weak.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>PoW performance</title>
|
|
<link>/blog/pow-performance/</link>
|
|
<pubDate>Wed, 01 Sep 2021 00:00:00 +0000</pubDate>
|
|
|
|
<guid>/blog/pow-performance/</guid>
|
|
<description>mCaptcha uses a proof-of-work(PoW) mechanism to rate limit users or potential bots. In order for this to be effective, the PoW should be configured properly. The difficulty requirement can&rsquo;t be too high, as it could cause accessibility issues on the client-side while at the same time, it shouldn&rsquo;t be too low, as it wouldn&rsquo;t offer proper protection against bots.
|
|
Malicious bots(the ones that wreak havoc), run native code which is capable of running in a multi-threaded context.</description>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Say hello to mCaptcha</title>
|
|
<link>/blog/say-hello-to-mcaptcha/</link>
|
|
<pubDate>Wed, 26 May 2021 00:00:00 +0000</pubDate>
|
|
|
|
<guid>/blog/say-hello-to-mcaptcha/</guid>
|
|
<description>At mCaptcha, we believe in digital freedom and privacy and so we built a proof-of-work based CAPTCHA system that doesn&rsquo;t track. Seriously, no tracking. But that isn&rsquo;t the killer feature, our system doesn&rsquo;t require the user to pick cars or ID sidewalks &mdash; our system does it&rsquo;s thing(usually at the click of a button) and gets out of the way.
|
|
How does it work? mCaptcha uses SHA256 based proof-of-work(PoW) to rate limit users.</description>
|
|
</item>
|
|
|
|
</channel>
|
|
</rss>
|