whatisgithub

What is dear_fcc?

efforg/dear_fcc — explained in plain English

Analysis updated 2026-08-05 · repo last pushed 2018-08-17

1RubyAudience · pm founderComplexity · 3/5DormantSetup · moderate

In one sentence

A tool from the Electronic Frontier Foundation that lets advocacy groups run letter-writing campaigns to submit public comments to the FCC. Supporters personalize pre-written messages through a custom web form, and the system handles submitting them.

Mindmap

mindmap
  root((repo))
    What it does
      Runs letter-writing campaigns
      Submits comments to FCC
      Custom web form for supporters
    How it works
      Config files for proceedings
      Comment templates with options
      Queue-based submission system
    Use cases
      Net neutrality campaigns
      Media ownership rule comments
      FCC public input campaigns
    Tech stack
      Ruby
      Docker deployment
      CSV bulk export
    Audience
      Advocacy organizations
      Campaign organizers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Run a public comment campaign for an FCC proceeding with a custom web form

USE CASE 2

Collect personalized supporter messages using pre-written templates with multiple choice options

USE CASE 3

Export thousands of comments to CSV for bulk upload when FCC submission rates are limited

What is it built with?

RubyDockerCSV

How does it compare?

efforg/dear_fcc521xueweihan/homebrew-coreamitsuryavanshi/graphiti-activegraph
Stars111
LanguageRubyRubyRuby
Last pushed2018-08-172022-05-112022-12-09
MaintenanceDormantDormantDormant
Setup difficultymoderateeasyhard
Complexity3/51/53/5
Audiencepm founderdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires Docker installed and configuration of two files defining the FCC proceeding and comment template before the app can start.

The license terms are not specified in the repository documentation.

So what is it?

Dear FCC is a tool built by the Electronic Frontier Foundation that lets organizations run their own letter-writing campaigns to submit public comments to the Federal Communications Commission. Instead of sending people to the FCC's own comment system directly, an advocacy group can set up a custom web form where supporters choose from pre-written language, personalize their message, and then the system handles submitting all those comments to the FCC on the backend. The way it works is straightforward. An organizer configures two files: one describing the specific FCC proceeding they are commenting on, and another defining the comment template shown to users. The template can include multiple choice options where people pick from suggested language, options that let people either pick a suggestion or write their own, and randomized selections that vary the wording from person to person so the comments don't all read identically. When someone submits a comment through the form, it goes into a queue and gets sent to the FCC's filing system. This is clearly built for advocacy organizations running campaigns around FCC rulemakings, net neutrality debates, media ownership rules, or any proceeding where public input matters. The README references the "Restoring Internet Freedom" proceeding specifically, which was the FCC's 2017 net neutrality repeal, so this tool was used during that fight. One practical detail worth noting: the FCC's electronic filing system limits how fast comments can be submitted, so if a campaign generates a huge volume, the system can export everything to a CSV file for bulk upload through a separate FCC form. That export clears the queue, so you need to save the output. The CSV is capped at five megabytes to match the FCC's own file size limit, and if you have more comments than that, you run the export again. The project uses Docker for deployment, which means it packages everything needed to run into a self-contained setup. Configuration is minimal, copy the example files, fill in your campaign details, and start it up.

Copy-paste prompts

Prompt 1
Help me set up a Docker deployment for a Ruby app that collects public comments and submits them to a government filing system. I need to configure campaign details and comment templates.
Prompt 2
I want to build a letter-writing campaign web form where supporters choose from pre-written language options or write their own message. Help me design the comment template configuration with multiple choice, free-text, and randomized options.
Prompt 3
Help me implement a CSV export feature for a comment queue system. The CSV needs to be capped at 5 megabytes, and if there are more comments than that limit, the export should run again for the remaining items.

Frequently asked questions

What is dear_fcc?

A tool from the Electronic Frontier Foundation that lets advocacy groups run letter-writing campaigns to submit public comments to the FCC. Supporters personalize pre-written messages through a custom web form, and the system handles submitting them.

What language is dear_fcc written in?

Mainly Ruby. The stack also includes Ruby, Docker, CSV.

Is dear_fcc actively maintained?

Dormant — no commits in 2+ years (last push 2018-08-17).

What license does dear_fcc use?

The license terms are not specified in the repository documentation.

How hard is dear_fcc to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is dear_fcc for?

Mainly pm founder.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.