Update

<?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> <generator uri="http://jekyllrb.com" version="3.1.6">Jekyll</generator> <link href="/feed.xml" rel="self" type="application/atom+xml" /> <link href="/" rel="alternate" type="text/html" /> <updated>2024-11-08T00:03:27+00:00</updated> <id>/</id> <entry> <title>Update</title> <link href="/2024/11/01/update/" rel="alternate" type="text/html" title="Update" /> <published>2024-11-01T00:00:00+00:00</published> <updated>2024-11-01T00:00:00+00:00</updated> <id>/2024/11/01/update</id> <content type="html" xml:base="/2024/11/01/update/"><ul> <li><a href="/ElectionResults/2024">2024 staff election results</a> - thanks to Steve McIntyre (Sledge) and Pierre-Elliott B茅cue (peb) for running the elections as counters this year.</li> </ul> </content> <summary> 2024 staff election results - thanks toSteve McIntyre (Sledge) and Pierre-Elliott B茅cue (peb) for runningthe elections as counters this year.</summary> </entry> <entry> <title>Update</title> <link href="/2024/03/23/update/" rel="alternate" type="text/html" title="Update" /> <published>2024-03-23T00:00:00+00:00</published> <updated>2024-03-23T00:00:00+00:00</updated> <id>/2024/03/23/update</id> <content type="html" xml:base="/2024/03/23/update/"><ul> <li><a href="/ElectionResults/2023">2023 staff election results</a> - thanks to Steve McIntyre (Sledge), Alexander F忙r酶y (ahf), and Pierre-Elliott B茅cue (peb) for running the elections as counters this year.</li> </ul> </content> <summary> 2023 staff election results - thanks toSteve McIntyre (Sledge), Alexander F忙r酶y (ahf), and Pierre-ElliottB茅cue (peb) for running the elections as counters this year.</summary> </entry> <entry> <title>Update</title> <link href="/2023/10/10/update/" rel="alternate" type="text/html" title="Update" /> <published>2023-10-10T00:00:00+00:00</published> <updated>2023-10-10T00:00:00+00:00</updated> <id>/2023/10/10/update</id> <content type="html" xml:base="/2023/10/10/update/"><ul> <li><a href="/ElectionResults/2022">2022 staff election results</a> - They鈥檙e a year late, but 2022 election results have been posted. Thanks to Steve McIntyre (Sledge), Alexander F忙r酶y (ahf), and Pierre-Elliott B茅cue (peb) for running the elections as counters this year.</li> </ul> </content> <summary> 2022 staff election results - They鈥檙e a year late,but 2022 election results have been posted. Thanks to Steve McIntyre(Sledge), Alexander F忙r酶y (ahf), and Pierre-Elliott B茅cue (peb) for runningthe elections as counters this year.</summary> </entry> <entry> <title>Update</title> <link href="/2022/10/24/update/" rel="alternate" type="text/html" title="Update" /> <published>2022-10-24T00:00:00+00:00</published> <updated>2022-10-24T00:00:00+00:00</updated> <id>/2022/10/24/update</id> <content type="html" xml:base="/2022/10/24/update/"><ul> <li> OFTC wants to upgrade the services in use to the Atheme variant. One user visible change will be the uniqueness of SSL cert fingerprints for accounts. If you are using SSL CertFP to identify to your accounts, please review the fingerprints associated with your account(s) and ensure that they are not duplicated between your accounts. This only applies if you have multiple separate accounts using the same fingerprint. Linked/grouped nicks are only a single account. We intend to remove any remaining duplicate fingerprint entries on 2022-11-22. The removal algorithm will delete duplicates from all but the most recently used account. </li> </ul> </content> <summary> OFTC wants to upgrade the services in use to the Atheme variant. One uservisible change will be the uniqueness of SSL cert fingerprints for accounts.If you are using SSL CertFP to identify to your accounts, please review thefingerprints associated with your account(s) and ensure that they are notduplicated between your accounts. This only applies if you have multipleseparate accounts using the same fingerprint. Linked/grouped nicks are only asingle account.</summary> </entry> <entry> <title>Update</title> <link href="/2022/01/17/update/" rel="alternate" type="text/html" title="Update" /> <published>2022-01-17T00:00:00+00:00</published> <updated>2022-01-17T00:00:00+00:00</updated> <id>/2022/01/17/update</id> <content type="html" xml:base="/2022/01/17/update/"><ul> <li>We now offer a <a href="/Tor">Tor</a> hidden service: <a href="ircs://oftcnet6xg6roj6d7id4y4cu6dchysacqj2ldgea73qzdagufflqxrid.onion:6697">ircs://oftcnet6xg6roj6d7id4y4cu6dchysacqj2ldgea73qzdagufflqxrid.onion</a>.</li> </ul> </content> <summary> We now offer a Tor hidden service:ircs://oftcnet6xg6roj6d7id4y4cu6dchysacqj2ldgea73qzdagufflqxrid.onion.</summary> </entry> <entry> <title>Update</title> <link href="/2021/11/05/update/" rel="alternate" type="text/html" title="Update" /> <published>2021-11-05T00:00:00+00:00</published> <updated>2021-11-05T00:00:00+00:00</updated> <id>/2021/11/05/update</id> <content type="html" xml:base="/2021/11/05/update/"><ul> <li><a href="/ElectionResults/2021">2021 staff election results</a> - thanks to Steve McIntyre (Sledge) and Alexander F忙r酶y (ahf) for running the elections as counters this year.</li> </ul> </content> <summary> 2021 staff election results - thanks toSteve McIntyre (Sledge) and Alexander F忙r酶y (ahf) for running theelections as counters this year.</summary> </entry> <entry> <title>Update</title> <link href="/2021/10/07/update/" rel="alternate" type="text/html" title="Update" /> <published>2021-10-07T00:00:00+00:00</published> <updated>2021-10-07T00:00:00+00:00</updated> <id>/2021/10/07/update</id> <content type="html" xml:base="/2021/10/07/update/"><ul> <li>We鈥檝e reconfigured our <a href="https://letsencrypt.org/2021/10/01/cert-chaining-help.html">Let鈥檚 Encrypt TLS certificates to not use the expired DST Root CA X3</a>, which should resolve issues with some clients and older TLS implementations. Note that if you鈥檙e using Android older than 7.1.1, you will no longer be able to connect without manually trusting the Let鈥檚 Encrypt CA.</li> </ul> </content> <summary> We鈥檝e reconfigured ourLet鈥檚 Encrypt TLS certificates to not use the expired DST Root CA X3,which should resolve issues with some clients and older TLSimplementations. Note that if you鈥檙e using Android older than 7.1.1, youwill no longer be able to connect without manually trusting the Let鈥檚Encrypt CA.</summary> </entry> <entry> <title>Update</title> <link href="/2021/09/15/update/" rel="alternate" type="text/html" title="Update" /> <published>2021-09-15T00:00:00+00:00</published> <updated>2021-09-15T00:00:00+00:00</updated> <id>/2021/09/15/update</id> <content type="html" xml:base="/2021/09/15/update/"><ul> <li> We have now deployed the <a href="https://github.com/oftc/oftc-webverify">new verification flow</a> that utilizes hCaptcha instead of Google ReCaptcha. Upon registration, the user receives a link which they can visit in their browser and solve a captcha. Upon successful completion, they will be marked as verified. Together with this, we have also made the system automatically mark the user as verified on the IRC side, making the old <code class="highlighter-rouge">checkverify</code> NickServ command no longer necessary. Should the user need a new link, as they expire after one hour, the new <code class="highlighter-rouge">reverify</code> NickServ command can come in handy. </li> <li> The primary purpose of the old ServicesWeb web application was to facilitate verification. With today鈥檚 changes, we have decided to discontinue it. </li> </ul> </content> <summary> We have now deployed the new verification flowthat utilizes hCaptcha instead of Google ReCaptcha. Upon registration, the user receivesa link which they can visit in their browser and solve a captcha. Upon successful completion,they will be marked as verified. Together with this, we have also made the system automatically mark the user as verified on theIRC side, making the old checkverify NickServ command no longer necessary. Should the user need a new link, as they expire after one hour, the new reverify NickServ commandcan come in handy. The primary purpose of the old ServicesWeb web application was to facilitate verification.With today鈥檚 changes, we have decided to discontinue it. </summary> </entry> <entry> <title>Update</title> <link href="/2021/06/18/update/" rel="alternate" type="text/html" title="Update" /> <published>2021-06-18T00:00:00+00:00</published> <updated>2021-06-18T00:00:00+00:00</updated> <id>/2021/06/18/update</id> <content type="html" xml:base="/2021/06/18/update/"><ul> <li><a href="/AntiSpamBot">New Anti-Spam Bot</a> - We have deployed a new anti-spam bot. With your channel op鈥檚 permission, it joins your channel, blocks spam messages before the channel sees them, and K-lines the spamming host. Read <a href="/AntiSpamBot">this page</a> to see if our bot is a good fit for your channel.</li> </ul> </content> <summary> New Anti-Spam Bot - We have deployed a new anti-spam bot.With your channel op鈥檚 permission, it joins your channel, blocks spammessages before the channel sees them, and K-lines the spamming host. Readthis page to see if our bot is a good fit for your channel.</summary> </entry> <entry> <title>Update</title> <link href="/2021/05/23/update/" rel="alternate" type="text/html" title="Update" /> <published>2021-05-23T00:00:00+00:00</published> <updated>2021-05-23T00:00:00+00:00</updated> <id>/2021/05/23/update</id> <content type="html" xml:base="/2021/05/23/update/"><ul> <li> <a href="/Privacy_Policy">Privacy Policy updates</a> - New accounts now have the flag PRIVATE turned on by default, all old accounts have this flag turned on forcefully ONCE as of now. This means that the mail address used for registration is no longer visible by default to other users, only <a href="/staff">IRCOps</a>. We have also updated our privacy policy to include more details on which data is visible to who (including other users). </li> </ul> </content> <summary> Privacy Policy updates - New accounts now havethe flag PRIVATE turned on by default, all old accounts havethis flag turned on forcefully ONCE as of now. This means thatthe mail address used for registration is no longer visible bydefault to other users, only IRCOps.</summary> </entry> </feed>

CINXE.COM

Update