🚨 COCK.LI IS ON RED ALERT.

Service Update Log | Warrant/Liberty Canary

Thank you very much for your gracious support to cock.li over the last few weeks. The cock.li team wants you to know that your donations have allowed us to place fighting for cock.li as our top priority.

This new era for cock.li means you can rest assured that we will make efforts to keep our userbase updated on the current happenings to the maximum extent possible. Cock.li started as a hobby project, and was slowly neglected over the years as upkeep mounted while interest in the project waned. Now that engaged people are working on the site every day again, you should expect that you will have some descriptions of the work that's going on, i.e. where your money is going.

If it seems like work is currently slow, that's because most of the required work is in the background, and it would be unwise to detail it at this point. Some day, our work will be less serious, and the quality of updates should improve further.

Until then, I hope you will appreciate this list of our current priorities:

    High priority

  1. RED ⟶ ORANGE alert (top priority)
  2. Regular maintenance
  3. Restore password changes
  4. Finish DNS migration and expansion
  5. Hardware maintenance & security
  6. New website with all features

    Medium priority

  1. Updates
  2. E-mail deliverability
  3. Financial reports
  4. Reimbursement calculations (for many $100s of bills not paid by cock.li over many years)
  5. Mail storage improvements
  6. New PGP keys
  7. Status page
  8. Update feeds (TXT+RSS)
  9. Team contacts
  10. Monitor improvements

    Low priority / Future work

  1. Writing about cock.li (its history, tech, and philosophy)

Of course, these priorities will change as our work develops and our minds wander. This list should be updated as needed.

Thanks again for your support. Back to work!

—Team cock.li

What is this about? Red alert?

You missed the party. Check log.txt.

Liberty Canary

Now restored along with the warrant canary at canary.asc.txt.

Donate to cock.li

Cock.li maintains two types of funds: SERVICESAFU and TEAMSAFU, used for operating and staffing costs, respectively. There are two funds because for over 10 years, no one directly related to cock.li was allowed to be paid for their work on it. TEAMSAFU is our solution to allow us to get paid for our work on cock.li, and there's much work to be done.

SERVICESAFU

SERVICESAFU is cock.li's operating expense fund. Expenses paid from this fund include costs for hosting, legal, domain registration, and contingencies.

This fund is still spending donations made 5 years ago, and should be well-funded even for the current red alert. But if you want to know your donation will be spent in the safest manner, this is where you send it.

The donations and expenses related to the Bitcoin wallets of SERVICESAFU are disclosed in cock.li's financial reports (which haven't been updated in 3 years, but will be "some day")

Monero: 44vHmnRmhcXiqq348LPGwxSPfvrN4pAKzb1GypnQn65c824N9MsKk2Z5okYCUieYy58u2DYHT4HToK1hXuqnk7QdNfe3nLL

Bitcoin: bc1q4pxl6727zj0s37zarhu20lsg72ac3htvlsv52l

TEAMSAFU

The SERVICE can't be SAFU if the TEAM isn't. In contrast to the service fund, TEAMSAFU allows our team to be paid for their work on cock.li, or for any purpose we see fit. Donations to this fund will directly encourage us to continue our work on the service. Its donations and expenses are not included in cock.li's financial reports, but the Bitcoin wallets can be publicly analyzed on the "block chain".

Monero: 41fqXKYNEWuBDuqYczhoSiE1aUN9tCGdWYrfjynebuTM3tdE5UUHEfeZjZ3iZpgqY8LdYLk9h4As66UBC5mARL4z98PfUwB

Bitcoin: bc1qg9ehmfzusgfd6dvudll0qxkcl8c5q3sh8qnetr

Fun facts about cock.li:

User count: ~1,400,000

Established: 2013

Domains: