canceledpeopleorg/canceledpeople.org

Cataloguing public episodes of cancel culture

canceledpeople.org

https://canceledpeople.org is a public resource designed to highlight the chilling effects of cancel culture wherever it exists, in an easily-sharable foramat for all to see. As a public resource, anyone can submit instances of cancellations for us to consider including in the database, via https://canceledpeople.org/submissions.

History

A similar version of this site was first published on https://canceledpeople.com and quickly gained notoriety online. Shortly after, the site mysteriously disappeared, with public requests to revive it. The site in this repository is a recreation of the old one, by entirely different site admins in an attempt to keep the public utility alive and useful for everyone.

Building the site

To build the site locally, run:

$ npm install
$ node run build

And then navigate to http://localhost:8080.

Contributing

Contributions are welcome! Please read CONTRIBUTING.md first.

canceledpeople.org's Issues

Add GitHub workflow/actions to build the site

This will let us stop storing the generated HTML in the master branch.

Make the header navigation links actually work

Right now they do nothing.

Add database search functionality

Separate the pages into separate directories

That way you can navigate to them without typing .html at the end.

Fix the header/body scroll problem

I think I have an extra div somewhere around <main>, which screws up scrolling. This is simply because I don't know much about material design lite. If you load the DB page and scroll down without clicking in the body, you'll bypass all of the table contents (will be hidden under the footer) and scroll down exposing the footer as if the scroll height of the page has been exhausted. This should be an easy fix.

Separate home page and cancellations page

Initially, it probably won't be as elaborate as the original site's home page with the fancy auto-typing animation, but we should at least separate it from the database so that old links to the old site still work (with the exception of .com -> .org).

In addition, /cancelations and /cancellations should probably end up at the same place, with one redirecting to the other.

Figure out why the mdl-js-buttons don't work on mobile!

They work now, specifically because I added some serious hacks:

• https://github.com/CanceledPeopleOrg/canceledpeople.org/blob/master/header.ejs#L43-L44
• https://github.com/CanceledPeopleOrg/canceledpeople.org/blob/master/js/generate-table.mjs#L37-L38

But absent these hacks, these buttons don't seem to work right. Clicking perfectly on the far outer edge of the button reliably triggers the expected behavior, but clicking like a normal person inside the button usually doesn't i.e., navigate, click the link, etc., but I don't know why. Someone with MDL experience might.

Add CONTRIBUTING.md

And explain that we'll only accept new submissions to the database via the submissions form, and that the only PRs that will be accepted for the database will be corrections or adjustments.

Store country codes in the database, instead of raw SVG code

With this in place, we can manually create each image that points to https://cdn.jsdelivr.net/gh/hampusborgos/country-flags@main/svg/<country-code>.svg, which we'll populate on the fly. This keeps the DB lean.

Make the header navigation bar sticky at the top

Maybe http://jsfiddle.net/will_stone/gk7u32b6/ can shed some light?

EJS templating build flow

Right now the site is a little hackily created, since it copies a bunch of HTML between all of the pages. We need to separate out the header and footer from each page dynamically, and using something like https://ejs.co/ and GitHub actions to build the live version of the site seems like perhaps the easiest, most lightweight solution. It makes the build more complicated, but much easier to maintain.

Make the database use an exported JS array instead of JSON

This is for browser compatibility. It seems that Firefox does not support JS module import assertions, but we should be able to achieve the same behavior (without the assertion) with plain ole JS module exports.

Make each row in the database linkable