Planet freenode

January 21, 2021

freenode staffblog

Changes to realnames of bridged users runs a bridge (matrix-appservice-irc) from their Matrix homeserver to freenode that allow Matrix users from any homeserver that federates with to join channels on freenode and intermingle with the normal IRC userbase. These users have their Matrix User Id (username and homeserver, e.g. put in the realname field of their IRC connection.

Over time, the need to differentiate users by which homeserver they are using has arisen for multiple reasons, and we've worked with the bridge operators to better format Matrix User Ids to suit the limited space provided by IRC realnames.

Realnames pose a slight problem for this usage; the maximum length for a Matrix User Id is 255 characters, whereas the maximum length for an IRC realname is 50 characters and things longer than that get truncated, which means if people have a Matrix username of 50 characters, it will truncate off the entirety of their homeserver.

The solution we came up with for this has been to reverse the order of username and homeserver, and then reverse the order of domain name parts and truncate that at 30 characters, which means the most significant parts of a homeserver's domain name comes at the start of a realname. For example, becomes net.freenode:jess. If a homeserver is truncated to 30 characters, a > is appended prior to the : - would become net.freenode.subdomaaaaaaaaaai>:jess.

We'd like to extend deep gratitude to the operators of the bridge for handling and implementing our change request quickly to suit a contemporary need, and we'd like to remind users that they can message staff at any time if they have any questions about the above changes.

by jess at January 21, 2021 08:00 PM

November 28, 2020

freenode staffblog

Changes to ChanServ regarding cloaks

freenode offers cloaks to our users, which replace one's hostname or IP address in various places with a project affiliation or lack thereof. Many of you will be aware that cloaks on freenode are not offered as a security measure and that various means are available to third parties to see through them.

However, many users acquire cloaks for security/privacy reasons anyway, and we've taken the decision to close some of the more glaring holes in the protection they offer. Please do note that cloaks are still not recommended for hiding a user's IP address.

We have deployed the following changes to ChanServ:

  • AKICK DEL no longer removes bans against the host behind a cloak
  • WHY no longers considers host-based access
  • UNQUIET no longer unquiets nicks that aren't on the target channel

Empirically, these are corner cases that don't often come into play when managing a channel. However, if you need assistance with something that these commands used to do, feel free—as always—to contact staff at any time.

While bans against IP addresses continue to apply to cloaked users, we intend to revise this behaviour in the future due to its privacy implications.

If you have any questions, please don't hesitate to ask either #freenode or any available member of staff.

by edk at November 28, 2020 05:00 PM

October 30, 2020

Pricey's blog

Restic backups to B2 without delete

Since setting up restic to back up to b2 I had embarassingly missunderstood the following UI wording around lifecycle settings:

I had assumed that this meant that all versions of the file would be maintained, no matter what clients did. The B2 docs are much clearer, explaining that these rules are really only automation on your existing files. They're not blocks/holds/locks which can take any action before or affect api calls.

In short: Lifecycle Rules schedule cleaning up version history, they don't prevent you deleting that version history.

One of the capabilities I want from my backup system is that the system backing data up should not also be able to destroy existing backups. (I'm not bothered about it reading previous backups) I had assumed lifecycle rules gave me this, I was wrong, time for a quick fix...

The obvious solution is to restrict the capabilities of the b2 api key during creation, specifically to omit deleteFiles. Unfortunately, restic doesn't currently handle this well, for example during basic backups it requires the ability to delete files in the locks/ directory and will complain loudly. There are a few open issues and existing [PR]'s but nothing yet merged.

Enter rclone

A few years ago rclone gained support for serving storage to restic via it's api and since rclone supports using soft delete by default swapping to this backend is pretty trivial.

One of the best bits is that you can continue to use your existing config, the repository format is unchanged.

The first thing to do is to generate a new key without deleteFiles:

$ b2 authorize-account
Backblaze application key ID: <account key id>
Backblaze application key: 

$ b2 create-key --bucket bucketname keyname listBuckets,listFiles,readFiles,writeFiles
<app key id> <app key secret>

...and then take that output to set up an rclone backend. You can either go through rclone config (See their docs for an example) or just drop a file into place:

$ cat ~/.config/rclone/rclone.conf
type = b2
account = <app key id>
key = <app key secret>

Then all that's left is to update your backup script:

  1. e.g. if previously it was
    then now it'll be
    (Note that the second part (b2) now refers to the name of the rclone backend, not the type. e.g. the bit within the square brackets of rclone.conf config)
  2. Alter the options rclone is called with. Annoyingly, even though rclone uses soft delete in b2 by default, restic sets --b2-hard-delete by default... so add the following option whenever you run restic:
    -o rclone.args="serve restic --stdio"

Back to the lifecycle...

Beyond restic forget/prune to manage old snapshots, we've now got to consider cleaning up soft deleted files. Given my backups are largely additive, forget rarely frees much space so it's not my biggest priority.

rclone provides a handy cleanup command, but it's very tempting to go back to where I began and let Backblaze b2 lifecycles clean them up without any extra scheduling on your own infrastructure.

Obligatory reminder.

October 30, 2020 12:00 AM

October 26, 2020

Md's blog

RPKI validation with FORT Validator

This article documents how to install FORT Validator (an RPKI relying party software which also implements the RPKI to Router protocol in a single daemon) on Debian 10 to provide RPKI validation to routers. If you are using testing or unstable then you can just skip the part about apt pinnings.

The packages in bullseye (Debian testing) can be installed as is on Debian stable with no need to rebuild them, by configuring an appropriate pinning for apt:

cat <<END > /etc/apt/sources.list.d/bullseye.list
deb bullseye main

cat <<END > /etc/apt/preferences.d/pin-rpki
# by default do not install anything from bullseye
Package: *
Pin: release bullseye
Pin-Priority: 100

Package: fort-validator rpki-trust-anchors
Pin: release bullseye
Pin-Priority: 990

apt update

Before starting, make sure that curl (or wget) and the web PKI certificates are installed:

apt install curl ca-certificates

If you already know about the legal issues related to the ARIN TAL then you may instruct the package to automatically install it. If you skip this step then you will be asked at installation time about it, either way is fine.

echo 'rpki-trust-anchors rpki-trust-anchors/get_arin_tal boolean true' \
  | debconf-set-selections

Install the package as usual:

apt install fort-validator

You may also install rpki-client and gortr on Debian 10, or maybe cfrpki and gortr. I have also tried packaging Routinator 3000 for Debian, but this effort is currently on hold because the Rust ecosystem is broken and hostile to the good packaging practices of Linux distributions.

October 26, 2020 12:25 AM

RPKI validation with OpenBSD's rpki-client and Cloudflare's gortr

This article documents how to install rpki-client (an RPKI relying party software, the actual validator) and gortr (which implements the RPKI to Router protocol) on Debian 10 to provide RPKI validation to routers. If you are using testing or unstable then you can just skip the part about apt pinnings.

The packages in bullseye (Debian testing) can be installed as is on Debian stable with no need to rebuild them, by configuring an appropriate pinning for apt:

cat <<END > /etc/apt/sources.list.d/bullseye.list
deb bullseye main

cat <<END > /etc/apt/preferences.d/pin-rpki
# by default do not install anything from bullseye
Package: *
Pin: release bullseye
Pin-Priority: 100

Package: gortr rpki-client rpki-trust-anchors
Pin: release bullseye
Pin-Priority: 990

apt update

Before starting, make sure that curl (or wget) and the web PKI certificates are installed:

apt install curl ca-certificates

If you already know about the legal issues related to the ARIN TAL then you may instruct the package to automatically install it. If you skip this step then you will be asked at installation time about it, either way is fine.

echo 'rpki-trust-anchors rpki-trust-anchors/get_arin_tal boolean true' \
  | debconf-set-selections

Install the packages as usual:

apt install rpki-client gortr

And then configure rpki-client to generate its output in the the JSON format needed by gortr:

echo 'OPTIONS=-j' > /etc/default/rpki-client

You may manually start the service unit to immediately generate the data instead of waiting for the next timer run:

systemctl start rpki-client &

gortr too needs to be configured to use the JSON data generated by rpki-client:

echo 'GORTR_ARGS=-bind :323 -verify=false -checktime=false -cache /var/lib/rpki-client/json' > /etc/default/gortr

And then it needs to be restarted to use the new configuration:

systemctl restart gortr

You may also install FORT Validator on Debian 10, or maybe cfrpki with gortr. I have also tried packaging Routinator 3000 for Debian, but this effort is currently on hold because the Rust ecosystem is broken and hostile to the packaging practices of Linux distributions.

October 26, 2020 12:22 AM

September 26, 2020

Pricey's blog

Multi-repos KISS

I have never worked in a monorepo professionally.

September 26, 2020 12:00 AM

June 10, 2020

erry's blog

Python argparse cheat sheet

I have a confession to make: I never remember how to use argparse. Maybe it’s because I don’t use it often enough to have how it works memorized, but I certainly use it often enough that I’m annoyed every time I have to look it up. Argparse? More like ARGHparse. continue reading...

The post Python argparse cheat sheet first appeared on Errietta's blog ☕.

by errietta at June 10, 2020 01:52 PM

May 26, 2020

Pricey's blog

LXD performance observation

You might want to consider enabling tmpfs...

May 26, 2020 12:00 AM

April 30, 2020

erry's blog

Documenting a Django API with OpenAPI and Dataclasses

Django makes it easy to quickly spin up APIs and provides a great admin interface and command line management tools. It certainly speeds up the development of any CRUD system. However, as your project grows, you will want to make sure your code is well-documented, both for your backend developers continue reading...

The post Documenting a Django API with OpenAPI and Dataclasses first appeared on Errietta's blog ☕.

by errietta at April 30, 2020 07:07 PM

March 19, 2020

Pricey's blog

AppArmor hat & child profiles

My last post omitted the real reason I hadn't swapped to OnlyOffice was that I was too lazy to look further into apparmor. Allowing dash to inherit the php permissions with /bin/dash ix, is one solution but for other reasons, I wanted to write a more contained profile to spawn dash within. Searching the internet & reading my favourite apparmor docs didn't enlighten.

March 19, 2020 12:00 AM

February 26, 2020

Pricey's blog

Why I'm not using ONLYOFFICE yet.

I'm a huge fan of Nextcloud and version 18 brought great integration with ONLYOFFICE. I'm not using it though because it ships with binaries that aren't always straightforward to execute.

February 26, 2020 12:00 AM

February 22, 2020

freenode staffblog

[Scheduled Maintenance] Services database spring cleaning

During the Easter weekend (April 12th to 15th) we will be purging the freenode services database. We periodically prune the database to remove expired accounts, nicknames and channels. Just like previous database purges we will be removing any accounts and nicknames that have not been used for 120 days at the time of the purge.

We appreciate that not everyone remembers to identify to services, and we would urge you to check and, if necessary, ensure that you identify so as to not lose your account/nickname(s) during the purge if you use any that may be approaching the expiration limit (120 days) used in connection with the services purge.

Please note that nicknames and accounts expire separately and you will need to identify to all grouped nicks that you wish to keep, and don’t forget to also check any second accounts you may have for bots or similar (for the sake of your fellow community members we would recommend cycling through any nicknames with a client that is not joined to channels so as to minimise disruption).

Some channels may also be affected by the NickServ purge and topical channels may be dropped from the database should the access list become empty. Primary channels will remain registered and can be reclaimed by the affected group contact(s).

If you have a nick grouped to your account that you would like to use as your main nick, you can change your account name; see /msg NickServ HELP SET ACCOUNTNAME for additional information. Remember that you can use sendpass to recover lost passwords - see /msg NickServ HELP SENDPASS for details. Please also make sure that your account has a valid e-mail address assigned, as this is the only way to regain access to your account should you lose your password. You can check the current address with /msg NickServ INFO while logged in, and set a new one with the SET EMAIL command, see /msg NickServ HELP SET EMAIL for instructions.

If you have any questions, please do not hesitate to ask our volunteers in #freenode or listed on /stats p.

Thank you for using freenode.

by Fuchs at February 22, 2020 10:42 AM

January 05, 2020

Md's blog

Debian support for libxcrypt

glibc 2.29-7 and libxcrypt 1:4.4.10-10 today entered Debian testing: crypt(3) and the other related library functions in libcrypt from now on will be provided by libxcrypt instead of glibc.

After 18 months of packaging work, Debian finally supports modern password hashing methods like yescrypt: the details about them are documented in crypt(5).

For the time being there is still no support for libxcrypt in our release of PAM, but hopefully the Debian maintainer will update the package soon and this will allow using yescrypt by default.

If you want to test now the new algorithms then you can generate a password using my mkpasswd program and copy it to /etc/shadow:

# echo "marco:$(echo 12345 | mkpasswd --stdin)" | chpasswd --encrypted

January 05, 2020 02:18 AM

December 20, 2019

erry's blog

13 ways the Internet is broken

#9 will shock you. The web has been changing the past few years, not necessarily always for the better. There has been an emergence of anti-patterns, which are patterns that stand to try to make a profit without caring about the user experience, or often by hindering it. These patterns continue reading...

The post 13 ways the Internet is broken first appeared on Errietta's blog ☕.

by errietta at December 20, 2019 12:13 PM

December 02, 2019

erry's blog

New WP install for this site

You may have noticed the site looks different. Due to “technical difficulties” I’ve had to move the wordpress install to a new box, quite hastily. Please let me know if anything is broken; I’m still picking up the pieces.

The post New WP install for this site first appeared on Errietta's blog ☕.

by errietta at December 02, 2019 12:03 PM

Hello world!

Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

by errietta at December 02, 2019 12:35 AM

November 28, 2019

Pricey's blog

Connection reset...

After switching energy supplier, I discovered I couldn't connect to their website.

This is an explanation with notes of how I've attempted to diagnose the issue so far.1

November 28, 2019 12:00 AM

November 23, 2019

freenode staffblog

Private Internet Access and the freenode project

This week we learned the news of the proposed merger between Private Internet Access (LTMI) and Kape Technologies.

freenode is not affected by this merger. Kape has indicated that it will honour Private Internet Access' server sponsorship for the next six months as a minimum, and we hope that the company will continue to support the project also after this time.

Nevertheless, the freenode project is fortunate to be in a position where it does not rely on a single sponsor and we have a broad and diverse range of supporters; and the freenode project will continue being part of and having access to support from the Imperial Family Companies (formerly London Trust Media Holdings (LTMH)).

freenode continues to exist to support the development and use of free and open source software, and there will be no changes to the operations, values, mission or direction of the freenode project in connection with the merger of Private Internet Access and Kape Technologies.

We would like to thank Private Internet Access for the support the company has provided to freenode and numerous other projects within the FOSS space, and we hope to see continued support for FOSS projects also upon conclusion of the merger.

by christel at November 23, 2019 06:50 PM

October 26, 2019

Pricey's blog

Nextcloud, CVE's & Apparmor

Nextcloud and others recently reported on CVE-2019-11043 which looks like a particularly nasty RCE affecting only nginx+php-fpm with certain configurations.

Unfortunately, the configuration the Nextcloud documentation recommended was one of those vulnerable configurations.

October 26, 2019 12:00 AM

October 18, 2019

Pricey's blog

Switching backups to Restic - update

In a previous post I mentioned swapping my backups to restic. Since then, I've found my B2 storage costs increased substantially and wanted to figure out why.

October 18, 2019 12:00 AM

October 11, 2019

Pricey's blog

Azure DevOps permissions primer

I often join Azure DevOps projects some time after they were started and can almost guarantee I'll find... questionable... permissions have been applied.

If you search for e.g. "azure devops permissions" you'll get pages like this which only tell half the story, so here's a quick primer...

October 11, 2019 12:00 AM

September 15, 2019

erry's blog

Making Jenkins Behave 2: Electric Boogaloo

That’s right, as promised, I’m going to torture myself with Jenkins some more, this time with multi-branch pipelines! If you missed it, I recently wrote a blog post in which I explained how to integrate Jenkins and Github with freestyle jobs. In that post, I stipulated that were I able continue reading...

The post Making Jenkins Behave 2: Electric Boogaloo first appeared on Errietta's blog ☕.

by errietta at September 15, 2019 02:19 PM

September 01, 2019

Pricey's blog

Switching backups to Restic

I have used Duplicati uneasily for some time to back up my personal server which hosts Nextcloud and other bits.

September 01, 2019 12:00 AM

August 22, 2019

erry's blog

Making Jenkins and Github ACTUALLY integrate with each other

Introduction Note There’s a better way of doing this with multibranch pipelines, which I recommend over this method. You may need to build jenkins jobs when branches/PRs are made from within the repository – say, to run tests. You may also want to report on the test status when finished. continue reading...

The post Making Jenkins and Github ACTUALLY integrate with each other first appeared on Errietta's blog ☕.

by errietta at August 22, 2019 12:37 PM

August 19, 2019

Pricey's blog

First thoughts on Zola

Zola1 is a static site generator in Rust.

Wanting to blog a bit more and having a passing interest in Rust, I figured I might as well rebuild my blog rather than actually write anything...

August 19, 2019 12:00 AM

August 12, 2019

Pricey's blog

Invoke-ASCmd Caches xmla?

tldr: Invoke-ASCmd caches xmla files somewhere. Always provide the absolute path to Invoke-ASCmd -InputFile.

August 12, 2019 12:00 AM

August 11, 2019

freenode staffblog

Matrix GDPR access request data overshare

Hi all,

You may already be aware that in the process of servicing a request for personal information under the GDPR, provided a user with a data dump that mistakenly included events that user had not been a party to. We suggest reading's writeup for more details.

On the morning of 2019-08-04 UTC we were notified by the recipient of the dump that the errant data included messages from freenode users and, in a spirit of transparency, felt it was important to keep you informed of any potential security issue concerning you.

We have reached out to's team in order to understand the impact of the issue, and they have assured us that all of these messages were to public channels whose administrations chose to make their histories publicly available.

If you have any questions, feel free to either track down a staffer in PM or email

Thanks for using freenode.

by edk at August 11, 2019 06:52 PM

June 22, 2019

freenode staffblog

Moving webchat to Kiwi IRC

Hi all,

after years of providing our good old qwebirc based webchat, we are excited to announce that freenode is moving to a new Kiwi IRC based solution!

The change will occur during this weekend (June 22nd / 23rd).

Kiwi IRC is an extensible and modern webchat solution, making IRC a lot easier and more comfortable to use for both newcomers and long time users. In addition to a clean and friendly UI it supports translations into various languages, easier formatting and usage of emoji and advanced customization for power users.

Most existing links and bookmarks should continue to work, including sites embedding the freenode webchat; please do let us know if you are running into issues.

We would like to thank everybody who supported us during this migration, most of all Kiwi's developer, prawnsalad, who provided a huge amount of code, adaptations, options and testing that should ensure a smooth migration.

Along with this change, we will no longer apply gateway cloaks to users of our webchat, treating them the same as any other client. While channel operators will still be able to recognize them via the realname field, we strongly suggest that you carefully consider the impact on legitimate users and hope that you decide not to ban webchat users as a whole.

Please note that the old webchat will no longer be available after this migration.

Thank you for using freenode, via our new Kiwi webchat or any other client you prefer!

by Fuchs, ilbelkyr at June 22, 2019 08:42 PM

June 17, 2019

freenode staffblog

ircd-seven 1.1.8

Hi all,

We're preparing to release version 1.1.8 of ircd-seven and deploy it to the production network over the coming weeks.

This release incorporates a number of user-facing changes:

  • Monitor is restored to a usable state, and will be re-enabled.
  • Spam filtering can be opted-out of. Setting mode +u on yourself ( /umode +u or /mode yournick +u) will disable filtering for messages sent to you. Setting it on a channel will disable filtering for all messages sent to that channel.
  • /motd and /stats are no longer ratelimited unless directed at a specific server.

We're also introducing support for several IRCv3 features that may improve the experience on capable clients:

There's one more change that is not related to this release, but deserves mention: nearly two years ago, we developed an improvement to the +z channel mode, which sends messages that would have been blocked by +q or +m to channel operators instead. Our new version sends these messages to ops from the @-prefixed version of the channel:

:e!e@freenode/staff/spy.edk PRIVMSG @#test :I'm quieted

to make it easier for operators to distinguish between messages everyone can see and messages they can see due to +z.

This borrows the syntax from an existing feature, STATUSMSG, but is easy to tell apart from it, because only ops and voiced users can send to @channel normally.

We gated this behind a feature switch, and we've been waiting, largely passively, for client support to increase. It appears that everyone who wants to act on warnings has done so, and we'd like to commit to a date to enable it.

We'll be enabling this feature on the 31st of July 2019, UTC. If you op a channel that uses +z, please make sure your client handles it correctly. You can send test messages by using /msg @#channel test using a second opped connection for any channel where you have ops—your client should associate this message with #channel, and preferably distinguish it from normal messages in some way.

Thanks for using freenode, and I look forward to collaborating with many of you via a slightly less-antiquated medium.

by edk at June 17, 2019 10:15 AM

May 30, 2019

erry's blog

ENOUGH with the burndown charts!

I heard about a team being asked to provide burndown charts in their demos to stakeholders. My first reaction was: why!? In this blog post, I’m going to try to articulate why I believe burndown charts are often meaningless at best and harmful at worst, and why even if they continue reading...

The post ENOUGH with the burndown charts! first appeared on Errietta's blog ☕.

by errietta at May 30, 2019 08:52 PM

May 20, 2019

erry's blog

Introduction to the fastapi python framework

I have been working on a new python-based API recently, and on a colleague’s suggestion we decided to use fastapi as our framework. Fastapi is a python-based framework which encourages documentation using Pydantic and OpenAPI (formerly Swagger), fast development and deployment with Docker, and easy tests thanks to the Starlette continue reading...

The post Introduction to the fastapi python framework first appeared on Errietta's blog ☕.

by errietta at May 20, 2019 04:21 PM

May 04, 2019

freenode staffblog

freenode Next Gen Tor Hidden Service

Over the last few years, the Tor Project has developed a new Tor Hidden Services protocol. It has a few improvements over the previous version, including better cryptography using SHA3 and ed25519.

We've added a new Tor Hidden Service address to our instructions for connecting to freenode via Tor that uses the new protocol. The new address is


If you're using a recent version of Tor (0.3.5 or newer) to connect to freenode, you should be able to use the new service by changing from the old address to the new one in your client configuration. The old address will continue to work for the forseeable future, but is likely to be deprecated eventually as the Tor ecosystem changes.

by dax at May 04, 2019 12:00 AM

January 26, 2019

erry's blog

Build APIs with node, Lambda & Serverless

This is a talk I did at London Node User Group on January 23rd, 2019. You can watch the talk below or on youtube.

The post Build APIs with node, Lambda & Serverless first appeared on Errietta's blog ☕.

by errietta at January 26, 2019 05:28 PM

January 19, 2019

erry's blog

Porting to nuxt.js

My personal website is one of the places where I can easily experiment, and it has been written and rewritten a few times. Having said that, laziness meant that it was stuck on its previous PHP-laravel implementation for a while. PHP was one of the first things I learned as continue reading...

The post Porting to nuxt.js first appeared on Errietta's blog ☕.

by errietta at January 19, 2019 08:25 PM

December 21, 2018

Deedra's blog

kj7cmd: ham radio call sign etc

So i finally managed to get my ham radio license in november after several years of wanting to do it but not having the patience or ability to really study well. I was talking to an old roommate and she told me about hamtestonline. Apparrently hamtestonline is a really great way for studying for your ham radio exams as i had call to find out. You are allowed to miss 9 questions on the technission exam, I managed to only miss 5!

Next goal is to get my general license. I’ve already paid for the course just need to actually do the work. Hopefully i’d say by march at the latest i’ll have my general license.

I’m not sure if i’ll get my extra license or not. I will probably do it just to say i did it, however it’s not really a priority. Most of the ham bands can be gotten with your technission and general licenses at this point chris told me that getting that one is more to say you’ve done the work then anything else.

I wonder how in the world we can run an HF antenna in an apartment…!

by deedra at December 21, 2018 10:24 PM

tarch (the new talking arch)

I have no real idea what’s going to happen with this project at this point even if it’s going to actually move forward. Currently I’d consider this project up in the air and a giant question mark weather it’s going to move forward. I got nailed with medical things so we’ll see what happens.

by deedra at December 21, 2018 09:55 PM

November 04, 2018

freenode staffblog

freenode #live 2018 is a wrap, thank YOU!

Wow. What an incredible weekend. I want to express my heartfelt thanks to all those who joined us for freenode #live this weekend. Whether you participated in person or tuned into the livestream.

We were fortunate enough to have an exceptionally inspiring and engaging speaker line-up - thank you so much for coming to inspire the community. Thank you also to our supportive sponsors who have enabled us to put this event on again, and of course the freenode volunteer team - both those who detached for a weekend to throw themselves into an entirely different type of volunteering and those who stayed behind to keep the network running and also doubled as livestream monitors, a special thank you to you all for your willingness to adapt and get stuck in. A huge thank you also to the venue staff, and to the AV technicians!

YOU are freenode.

I hope that the several calls to action in various talks will inspire and encourage as we jump from C (communicate, collaborate and create) to E (engage, educate and empower).

I am confident that we will do a more extensive recap when we have started to recover from the weekend, but before I nod off to sleep I want to do a huge shout-out of thanks to those of the freenode #live participants that hailed from underrepresented groups. In a time where the world is oftentimes unjust and outright scary it has been an incredibly inspiring and empowering experience to meet so many of you this weekend. I am under no illusion that there isn't a fight still to be had to ensure full inclusion and equality and I am incredibly happy that you form a growing and significant part of our community.

YOU are freenode also. Thank you.

Lost property?

Towards the end of day two a pair of glasses were found in the theatre and while a few announcements were made no one came forth to claim the glasses. In the event that you lost yours but would prefer to be able to see properly again, please do get in touch with us via e-mail or IRC and we will arrange for the glasses to be returned to you!

by christel at November 04, 2018 10:59 PM

October 01, 2018

freenode staffblog

Did you hear? freenode #live is coming to town!

A little over a month from now, the second freenode #live will take place at We The Curious in Bristol. With talks from many free and open source community leaders such as Leslie Hawthorn, VM Brasseur, Chris Lamb and Bradley Kuhn, freenode #live once again brings an international free software gathering to the South West.

Other exhibitors at this year’s event will be the returning main sponsor, Private Internet Access, as well as the Free Software Foundation, OpenSuSE, Minetest, Linux Journal and the Handshake Project.

Handshake is a new decentralized alternative DNS root, and for a short time before launch freenode users and members of the free and open source community are encouraged to sign up today at and receive free Handshake coins that can be used to purchase domain names when Handshake launches in the near future.

Tickets for the full event start at £15 (approximately USD $20, 18 Euro) but there is a free tier for those wanting to catch the talks and exhibition hall only. Bristol is well connected with Bristol International Airport (BRS) serving many European destinations, and the city is a few hours by train from London and Manchester.

Please note: This guest blog entry has been written by our sponsor Handshake.

by mattl from Handshake at October 01, 2018 04:47 PM

September 24, 2018

freenode staffblog

Spam filtering


As most of you are aware, we've been experiencing significant spam over the past few weeks. As a result, we have decided to roll out a server-side spam filter. Unlike our current spam-mitigating techniques, this system applies to private messages and does not let the first matching line get through.

Various ethical concerns have been raised over the course of introducing this feature. They'll be addressed below. The short version, though, is that the system has various limitations built in designed to prevent operator abuse. Only a tiny bit of information can get out of the filters, and they do not have access to much information themselves, to the extent that we believe the obvious ways to abuse such a feature are impractical.

We've historically been reluctant to take steps like this, and we remain so, but we believe the disruption has reached such a level that this is necessary to allow the communities using freenode to collaborate effectively. The prior complement of anti-spam measures represents our preferred approach, and we intend to employ this only when they prove insufficient to minimize disruption.

For the technically inclined, you can view the changes here.

  • Could this be used to spy on users? Which filter a user matched is not reported to staff, only that one did. This limits the theoretical maximum rate of passive monitoring to one bit per message, far less than the information content of conversations.

    Recipients of private messages are not included in the line that filters match on, so staff cannot use spam filters to see who is talking to whom.

  • Could this be used to shadowban users? No. If a filter blocks a message, its sender is either disconnected from the network or sent an error message.

    Currently, the filter system is configured not to use the nick, username, or hostname for filter matching, so it can't discriminate against particular users at all.

The exact information filters "see" is as follows:

  • The type of message (PRIVMSG/NOTICE)
  • The target of the message, if that target is a channel. For private messages, filters can see that they are PMs but not who their target is.
  • Whether or not the sender is identified (but not their account name)
  • The full contents of the message

The code can be configured to filter on the nick!user@host of the sender. We haven't enabled this, and have no current plans to, but this is subject to change should the nature of the spam demand it.

Filtering is always performed on the server originating a message, and inside the ircd process. This system will never cause a message to be distributed more widely than before.

Staff can, as always, answer your questions about this change, and we welcome constructive feedback. Private messages to staff are not subject to filtering.

by edk at September 24, 2018 05:47 PM

September 03, 2018

Deedra's blog

the new talking arch (tarch)

for many reasons that have come up in the last couple days mike and i decided to just fork talking arch. I’d rather not drag frustration and politics into a project I want to help start and we decided that since we want to add quite a few new features to talking arch as well as try and  keep a generic talking arch livecd for those who just want straight talking arch.


And so we’re forking it. we’ve decided to do several things i’ll mention below all of which we think will help those who need a standard talking arch livecd that talks but we want to create a special livecd with several things.


*we want to create 2 sets of livecds 1 which uses fenrir the new screenreader and 1 which uses speakup.

*in the long run we will probably have to move to fenrir but that’s quite a ways off i suspect.

*we want to create a livecd with many admin and rescue tools that  will assist those blind folks who  are system admins who need those features.

*We also want to add support to that same livecd to include other installers  so that say a user who needs a talking livecd but debian isn’t talking,  the user can use that admin type livecd to install debian voidlinux arch you get the idea.


We are greatly looking forward  to getting this project moving and hope that those who may use it will enjoy it. I’ll announce further things as we get things rolling. I suspect however the first step is to bring the generic livecd current so people dont have a livecd that’s a year old or more.


Stay tuned!



by deedra at September 03, 2018 04:12 AM

September 02, 2018

Deedra's blog

thoughts on server hosting and vpss

So last year when i origionally bought I wanted to relearn some of my admin skills part of which was buying and getting a vps to play with. We had seen something of scaleway’s offers they had at one time of  $3/month for a nice little arm server with a decent amount of disk and ram. I was also looking at as well as that’s where chris’s domain has been hosted for many years.


Itried scaleway for a while and hated it too many accessibility problems on their site for 1 thing and many other things i hated about them.  I ended up going with and sticking with prgmr for many reasons the setup  was nice getting  voidlinux set up on it was easy for chris to do. having an out-of-band console via ssh is absolutely wonderful and the support and staff is incredibley wonderful to deal with. So, there is my recommendation so to speak. I have nothing but wonderful things to say about prgmr and well scaleway….the accessibility nightmare of the centurey and other bad things.



by deedra at September 02, 2018 08:24 AM

September 01, 2018

Deedra's blog

my views on marijuana recreational and medical

I’ve used marijunaa for several years now for medical reasons. I have a lot of issues that i’ll write about later but for now let’s say that i have severe chronic pain and vomiting and psych issues i dont think they’ve fully diagnosed. For me marijuana is a needed medication.

Doctors here dont deal with pain meds much any more and dont like giving them out for chronic pain. For me i refuse opiates for many reasons. The biggest of which is i dont like what they do to me plus they make me puke.

So medical marijuana for me it is. It controls the pain and nausia but it’s got the side effect that i’m psychologically adicted to it. What this means is that my body seems to essentially require that the levels be stable. when they’re not it causes my psych issues to spiral which makes me puke… get the idea.

As for recreational marijuana it’s now a thing i could take or leave. it’s a medicine and so essentially it’s no longer fun.

by deedra at September 01, 2018 08:07 AM

fenrir screenreader

I’ve not discussed this screenreader yet as it’s been a while since i’ve had a blog i’ve been happy with.

Fenrir is a user-space screenreader for linux. I love it as i think it’s a good replacement for speak considering speakup has some issues.

In reality all screenreaders have their issues but i prefer fenrir for many reasons. Mainly it’s not built into the kernel and i can use it with an x terminal and get around orca’s terminal bugs..

I think the biggest bug i’ve found in fenrir so far is one that i hope will be fixed before the next release.


by deedra at September 01, 2018 07:59 AM

kittyrats: part2

we have 2 kittyrats and definitly dont want more. JIngles and bastet are like our children for lack of better wording. Jingles is starting to have i guess what i’d call old age issues she gets really bad hairballs that cause her to spew a lot. so off to the vet on the 10th, and maybe we can find out what’s wrong with the jingle kitty.

Bastet on the other hand is a healthy girl but she’s got this weird fear of mike’s guide dog. She kind of freaks out a litle but she’s also getting curious and brave so we’l see what she does.

The kittyrats will have their own wordpress blog soon like me. They’ve got a older blog but it’s time to hear what they have to to say!

by deedra at September 01, 2018 07:56 AM

what’s a kittyrat?

everyone probably wonders by now what’s a kittyrat? chris and i started calling our cats kittyrats when we got jingles. Reason why is because she’s got a super long tail and long body and legs. The term kittyrat stuck because well it’s stupidly cute and fun.:P

We got a roommate a bit ago and now mike calls them kittyrats to!

by deedra at September 01, 2018 07:52 AM

talking arch thoughts and decisions

talking arch was a project created by chris several years ago it provides a way for users to have an easily accessible talking live cd for linux so they can install arch linux and possibley other things. I also know of many who use it as a rescue cd.

When chris stopped using archlinux the project was handed over to someone who took it on and has been maintaining it up till their x8664 machine went boom. Mike and i have decided to take over the project and either a, take it over or b fork it if we can’t take over the project. Decision soon either way because if i dont hear anything by monday i’ll fork.

by deedra at September 01, 2018 07:48 AM


i’ve been freenode staff off and on over the years as things have gone. I’ve been back for a bit over a year give or take and it’s been an interesting experience. Over all it’s been extremely enjoyable however and despite the spam the strange ones and the bad ones so to speak it’s been well worth coming back.

I’ve changed my schedule recently to cover US nights and early sleeping EU hours so hopefully we’ve got a bit more hands to help out when users need to get the help.

by deedra at September 01, 2018 07:44 AM

updates or something

i’ve had multiple blogs in the past and i’ve never really kept up witht hem for multiple reasons. This is one of those blogs where anything goes. I may discuss personal things open sources stuff and such and there will always be kittyrats!

by deedra at September 01, 2018 07:40 AM

August 06, 2018

freenode staffblog

Continued and persistent spambot attack and clarification

As you may be aware there has been a prolonged spambot attack directed at freenode (and other IRC networks) in recent weeks, targeting a number of individuals involved with freenode and the wider IRC communities. The freenode team, and people involved with the wider IRC communities, are working hard to mitigate and reduce the spam that hits your community channels.

The spam content has changed in the last few days and while I am extremely glad that the attacks appear to no longer focus on members of the volunteer team and no longer involve libellous and false statements relating to these volunteers, we feel we should provide some clarification on some of the claims that are being made in the current spamwave relating to freenode and its involvement in Handshake.

The current spambot attacks state that freenode is involved with an 'ICO scam' relating to the Handshake project. Most freenode volunteers have involvement with one or several FOSS projects, often projects that use the freenode network as part of their communications toolbox. Handshake is no different in this regard, as it is a project that I have been involved with. I am deeply sorry to those affected by the spam, to freenode and to Handshake that spammers have chosen to use my involvement as a further platform to attack the freenode communities, and now also Handshake.

Prior to announcement, the Handshake project raised USD 10.2 million in funding from project supporters and the project made the decision to not only give a substantial amount of its coin supply to people and projects within the FOSS sphere but to also donate the USD 10.2 million (FIAT) to projects whose work the initial project contributors admire and/or rely upon. Like many projects within the FOSS world, Handshake has extensively used other free and open source software to build its codebase, and FOSS also lies at the foundations of the internet architecture that we rely upon day to day.

One of the projects Handshake identified as useful is indeed also freenode, which is on the pledgee list to receive a FIAT donation from the project. This donation will, among other things, contribute towards making the freenode #live conference bigger and better, and also to focus on some development work that has otherwise been on the back-burner. freenode is happy to be included as a list of recipients and honoured to be appreciated in this way.

  • Handshake is a FOSS project, and like many FOSS projects it has a channel on the freenode network.
  • Handshake is an experimental peer-to-peer DNS for which one aim is to be more resistant to censorhip than existing systems.
  • Handshake is doing a faucet distribution to a number of FOSS contributors and projects, many of which are freenode users.
  • Handshake is making a fairly hefty (USD 10.2 million) overall financial contribution to projects within the FOSS sphere in addition to its faucet allocation of HNS coins and freenode is one of many projects within the FOSS sphere that is receiving a contribution.

As such, any link between freenode and Handshake is tenuous at best and the current wave of spam would appear to be designed to do little bar discredit freenode and the Handshake project both.

I am sure you will appreciate that the freenode volunteer team is not in a position to answer questions relating to the Handshake project any more than they are in a position to answer questions relating to any other new FOSS project that starts to use the freenode network.

But I also understand that some of you may have additional questions relating to Handshake, I am sure you will appreciate that the freenode website is not the platform for such a discussion, and would suggest that you visit the Handshake website, Handshake Github Repository and Handshake Documentation if you are interested in learning more about the project and that you direct any questions to the Handshake project via the appropriate communication channels for the project.

by christel at August 06, 2018 06:30 AM

July 28, 2018

erry's blog

Installing and getting started with Python

I like experimenting with and learning new things. I’d never looked at Python before, because its syntax put me off, coming from a background of languages with C-like syntax. However, I eventually convinced myself to at least have a play with it and I’ve started working on a simple application continue reading...

by errietta at July 28, 2018 12:05 PM

July 27, 2018

freenode staffblog

Current spambot attack on freenode (and elsewhere)

Many of you will have noticed that over the last few days there has been an extensive spambot wave on freenode, and on other networks.

The fairly aggressive spambot attacks link to websites that we believe to have been set up to impersonate freenode volunteers, and that we believe to contain offensive and incorrect information intended to defame and libel members of the freenode volunteer team.

Naturally, the matter has been escalated to law enforcement and both the project and the individual volunteers concerned have sought legal advice in connection with the current attack.

Due to the nature of the attack, this is of course causing serious emotional distress on the part of the affected volunteers and their immediate family and social circles, as well as the rest of the volunteer team.

On behalf of the entire team, I would like to express thanks to those of you who have reached out with words of encouragement and support, and especially those of you from other IRC networks who have invested your time and efforts in trying to help mitigate and support.

I would also like to apologise to those users and channels (on and off freenode) who are affected by the spam.

by christel at July 27, 2018 01:20 PM

July 13, 2018

freenode staffblog

freenode #live 2018: Welcoming (some of) this year's keynote speakers

It is with a great deal of excitement that I can announce some of this year's keynote speakers for freenode #live. The entire freenode team is excited to be welcoming the following FOSS rockstars to Bristol this November; Bradley Kuhn, Chris Lamb, Kyle Rankin, Leslie Hawthorn and VM Brasseur.

We have a few more exciting announcements to make in the lead-up to the conference! You don't want to miss out, and we encourage you to head over to to get your tickets for this year's event! And if you want to join this year's speaker line-up then you still have some time, the CFP is open and we're looking forward to hearing from you.

Bradley M. Kuhn

Bradley M. Kuhn is the Distinguished Technologist at Software Freedom Conservancy, and editor-in-chief of Kuhn began his work in the software freedom movement as a volunteer in 1992, as an early adopter of GNU/Linux, and contributor to various Free Software projects. Kuhn's non-profit career began in 2000 at FSF. As FSF's Executive Director from 2001-2005, Kuhn led FSF's GPL enforcement, launched its Associate Member program, and invented the Affero GPL. Kuhn was appointed President of Conservancy in April 2006, was Conservancy's primary volunteer from 2006-2010, and has been a full-time staffer since early 2011. Kuhn holds a summa cum laude B.S. in Computer Science from Loyola University in Maryland, and an M.S. in Computer Science from the University of Cincinnati. Kuhn received an O'Reilly Open Source Award, in recognition for his lifelong policy work on copyleft licensing. You can follow him on Twitter @bkuhn_ebb_org

Chris Lamb

Currently Project Leader of the Debian GNU/Linux project and a member of Board of Directors for the Open Source Initiative, Chris is a freelance computer programmer, author of dozens of free-software projects and contributor to 100s of others. He has been official Debian Developer since 2008 and is currently highly active in the Reproducible Builds sub-project for which he has been awarded a grant from the Linux Foundation's Core Infrastructure Initiative. In his spare time he is an avid classical musician and Ironman triathlete. Chris has spoken at numerous conferences including LinuxCon China, HKOSCon,, DjangoCon Europe, LibrePlanet, OSCAL, All Things Open, SCALE, Software Freedom Kosovo, #freenode Live, FOSS'ASIA, and many more. You can follow him on Twitter @lolamby

Kyle Rankin

Kyle Rankin is the Chief Security Officer at Purism, SPC and a Tech Editor and columnist at Linux Journal. He is the author of Linux Hardening in Hostile Networks, DevOps Troubleshooting, The Official Ubuntu Server Book, Knoppix Hacks, Knoppix Pocket Reference, Linux Multimedia Hacks and Ubuntu Hacks, and also a contributor to a number of other O’Reilly books. Rankin speaks frequently on security and free and open source software including at BsidesLV, O’Reilly Security Conference, OSCON, SCALE, CactusCon, OpenWest, Linux World Expo and Penguicon. You can follow him on Twitter @kylerankin.

Leslie Hawthorn

An internationally known developer relations strategist and community management expert, Leslie Hawthorn has spent the past decade creating, cultivating, and enabling open source communities. She’s best known for creating the world’s first initiative to involve pre-university students in open source software development, launching Google’s #2 developer blog, and receiving an O’Reilly Open Source Award in 2010. Her career has provided her with the opportunity to develop, hone, and share open source expertise spanning enterprise to NGOs, including senior roles at Red Hat, Google, the Open Source Initiative, and Elastic.

If you cheer during movies when you hear the words “I fight for the users” or “Get your head out of your cockpit,” the two of you will likely get along famously. Follow her on Twitter @lhawthorn or read her blog at

VM Brasseur

VM (aka Vicky) spent most of her 20 years in the tech industry leading software development departments and teams, and providing technical management and leadership consulting for small and medium businesses. Now she leverages nearly 30 years of free and open source software experience and a strong business background to advise companies about free/open source, technology, community, business, and the intersections between them.

She is the author of Forge Your Future with Open Source, the first book to detail how to contribute to free and open source software projects. Think of it as the missing manual of open source contributions and community participation. The book is published by The Pragmatic Programmers and is now available in an early release beta version. It's available at

Vicky is the Vice President of the Open Source Initiative, a moderator and author for, an author for Linux Journal, and a frequent and popular speaker at free/open source conferences and events. She's the proud winner of the Perl White Camel Award (2014) and the O’Reilly Open Source Award (2016). She blogs about free/open source, business, and technical management at {anonymous => 'hash'};. You can follow her on Twitter @VMBrasseur

by christel at July 13, 2018 01:49 PM

June 29, 2018

freenode staffblog

freenode Security Update: Reused Password Attack

In the very early hours of today (Friday 29 June 2018), we became aware of unauthorised attempts to access a substantial number of freenode accounts. This appears to be the result of an attacker using lists of usernames and passwords from other online services that have previously been compromised, and trying these combinations on freenode accounts.

Our investigations commenced immediately and we found that the attacker had been able to log in to a number of freenode accounts.

freenode has not been hacked or compromised.

Affected information

For the affected accounts, usernames (nicknames) and passwords are affected. Additionally, for some accounts, other information including channel access and channel lists may be affected.

What we are doing

We are committed to protecting your data and, as a precaution, we have frozen the affected accounts and are in the process of sending individual notifications to affected users.

What you can do

If your account was affected, we are in the process of contacting you directly with information to reset your password and restore access to your account.

We encourage all users to practice good password hygiene, even if your account has not been affected at this time.

Attacks such as these have a tendency to escalate and cause a domino effect and we will continue to investigate and monitor for new attack vectors.

Password reuse means that once one account is compromised, all of the accounts that share that password become compromised.

by christel at June 29, 2018 08:08 AM

June 22, 2018

freenode staffblog

freenode and

In light of the two ongoing threads on Hacker News and Reddit concerning LTMH and, we have had a fair few freenode users contact us with questions as to whether will replace and/or absorb freenode, and what impact it would have on freenode communities.

I wanted to make sure that I addressed these concerns, and I can assure you that there are no plans on the part of freenode or LTM that involve any changes to freenode, freenode is not on the brink of shutdown — if anything, we are excited to be celebrating our 20th anniversary at this year's freenode #live event, and we hope to see at least another 20 after that.

The freenode project exists to support the development and use of Free and Open Source Software, and to that end it serves a very different purpose to the one that the visionaries behind have in mind. I fully believe that freenode and can co-exist, just as we co-exist with the numerous other IRC networks out there, and I would like to hope that may encourage those of their users who would be a good fit for freenode to come check us out, just as I hope that we may be able to send someone their way should we come across users who have great potential for running a series of training sessions or similar.

And while LTM has provided freenode with some much needed resources following last year's announcement, any potential partnership between the two will be limited to the possibility of freenode being represented in the foundation. It is my understanding that the foundation will operate on a nonprofit basis and will seek to bring together network operators and ircd/services developers to identify irc-related projects that are in need of funding and support, the team hopes to establish positive working relationships with operators, developers, ircv3 and end users alike, and the foundation, which will be governed by community consensus, will seek to ensure that and its efforts benefit all, not only those organisations that LTM supports today.

With regard to itself, I am curious and excited to see what's in store in terms of utilising IRC as a platform for delivering training sessions and the idea of a virtual incubator using an IRC backend. There has been some incredible developments on the client-side in recent times, with both IRCCloud and KiwiIRC continuing to work on features that will soon introduce video and voice calls, file-sharing and a host of other productivity tools that provide the team with good foundations for success.

For the sake of full disclosure: I am an Executive Vice President at LTM, and I work closely with all subsidiaries within the Group, included.

by christel at June 22, 2018 09:20 PM

June 16, 2018

erry's blog

Typescript and the Beanstalk

Typescript and the Beanstalk Deploying typescript apps to Beanstalk with CircleCI Before we get started, note that this post assumes that you have your CircleCI/Beanstalk integration working already. The reason for this is that setting that up itself is a very long-winded process. I may make a video about it continue reading...

by errietta at June 16, 2018 03:01 PM

June 06, 2018

freenode staffblog

Announcement: - New Service

Over the last two decades, we have found that a variety of freenode community members have reached out to us when they have been involved in the hiring process at their places of work. We have always been keen to support and promote relevant topics within the wider freenode communities, and we are excited to be launching the new website. Whether you are hiring for a permanent full-time role, looking to fill a temporary contract or looking to attract volunteer contributors for your FOSS project, we very much welcome and encourage you to use the site.

We hope that the new site will provide a useful addition to the existing freenode projects, such as the IRC network and the #live conference.


Head over to and add your job openings! The service is free to use, although we would be grateful for a contribution towards the operating costs of freenode services and the #live conference in the event that you successfully match via the website. In the event that you successfully match and wish to make a contribution, please contact us on

FOSS or other peer-directed project on the hunt for volunteers?

Why not add a post on the site to see if you may be able to attract some contributors from the wider freenode and FOSS communities?

Looking for a new job or a volunteer role?

Keep an eye on to see if something of interest is added. We will utilise wallops on the freenode IRC network to provide a brief summary of available roles periodically, for those wishing to receive these, please set yourself +w (/umode +w or /mode yournick +w).

Feature requests, suggestions and feedback?

The github repository can be found here, you can also drop us an e-mail to or find us in #freenode-jobs on the freenode network.

by christel at June 06, 2018 09:24 AM

May 26, 2018

freenode staffblog

Services maintenance and password security

We recently took our services (NickServ and friends) offline for maintenance to ensure encrypted storage of the services database.

During this process, we accidentally started services with an empty database. While we quickly realized the mistake, a large number of users were already logged out before we stopped the process, receiving a message like "Account youruser dropped, forcing logout". Services were quickly restored to normal afterwards and people were able to log in to their accounts as before. We would like to apologize for the disruption and confusion this may have caused.

Unfortunately, some people have used this opportunity to spread some misinformation, claiming that "all passwords have been released". This is not the case; there has been no threat to account security due to this incident. Additionally, we do not store passwords in a recoverable form at all.

In any case, we do recommend using a unique and secure password not shared with other online services. If you wish to change your password, you may do so using the command /msg NickServ SET PASSWORD <newpassword> while logged in (replacing <newpassword> with the password you wish to set). You might wish to consider using a password manager as well, such as KeePassXC.

We do take security and privacy very seriously. Notifications about any actual security breaches would appear on this site, as well as in global notices sent out by members of staff (identified by a freenode/staff/ cloak).

Apologies for the confusion and thank you for using freenode!

by ilbelkyr at May 26, 2018 05:12 PM

May 24, 2018

freenode staffblog

Updated Privacy Policy

With GDPR coming into effect tomorrow, 25 May 2018, freenode has made some amendments to its privacy policy to provide clarification relating to GDPR compliance.

In the event that you do not consent to our continued processing of your personal data in order to provide you with access to the service, you may drop your nickserv registration using the drop command (please see '/msg nickserv help drop' for further instructions). The latest version of our policies can always be found here.

by christel at May 24, 2018 11:58 PM

May 14, 2018

freenode staffblog

Channel moderation and channel topics

On freenode, we have always tried to minimise the amount of policies we apply across the network to allow projects to run their project channels in ways that complement their wider procedures and code of conducts for the projects both on and outside of IRC.

As such, a number of project channels opt to run their channels in a way that allows any user of the channel to modify the topic, and for most this is an approach that works most of the time, and ensures that updates can be announced and communicated effectively without all community members needing to be on the access list for the channel in question.

Naturally, the trade-off is that also those outside of the community are able to join and modify topics at will, and we are currently finding that a number of a project channels are having their topics changed to a message encouraging the users of the channel to move to a different channel.

In light of the above, we would like to ask that you check the modes and topics of your channel(s), and if appropriate reinstate your previous topic and decide whether or not you may wish to +t, even temporarily, to reduce disruption within your community.

Please do not hesitate to message a member of freenode staff for assistance!

by christel at May 14, 2018 07:26 AM

May 13, 2018

erry's blog

How to fix your node dependencies’ es6 causing browser errors

How to fix your node dependencies’ es6 causing browser errors If you’re doing anything with modern JavaScript this day and age you’re probably using es6 and using babel to transpile it back to es5, which works with most browsers. This works fine for the code you write, but what about ...continue reading

by errietta at May 13, 2018 10:30 PM