The Reading source code is now available.

I’m sunsetting at the end of this month. Thanks to everyone who participated—I really enjoyed building things with and for you. Data exports are available and I’ll be around for support and questions. —@leppert

Apologies for the flood of emails and posts from hooks. The server should be back up and running. In the next few weeks, I’ll likely be looking for a new arrangement for Reading, one that’s more respectful of the community. Reach out if you’d like to have a conversation.

@coldbrainreads Checking on it. Thanks for the heads up.

@martijnvdven The code’s in the mail. (on the way to your email, that is)

@martijnvdven I’ll see if I can get around to it :/. Happy to give you access to the existing extension codebase if you’re interested in taking a stab. And there’s always the bookmarklet.

@adamtcole Should be working now. Sorry for that :(

@adamtcole Giving it a look.

@llorchorg Should be fixed. Sorry about that, and thanks again for letting me know.

@llorchorg Hmmm. Looking into it! Thanks for the heads up.

Annnnd we’re back. Thus concludes the free hosting we were enjoying on Digital Ocean. If anyone has a new hookup, let me (@leppert) know!

Working on getting the site back up. Sorry!

@jameskeithford @maxisreading Working on it. It’s a false flag from Google. See also:

@thebestsophist that’s good to know! Let me know if you find it anywhere else.

@thebestsophist i.e. not our responsibility. I’ve asked Google to review and correct the error their end attributing the malware to Reading.

@thebestsophist That’s unfortunate. Dealt with two reports from Google earlier today, but both were hosted by linked pages.

@derekkinsman Mind following me so we can DM?

@derekkinsman Oh no! What’re you seeing?

@sumt7 When you click these buttons, they should trigger any hooks that are configured with yep / nope. Let me know if you still have probs.

@sumt7 Hi there! You’ll find “yep” and “nope” buttons when you use the Reading plugin or bookmarklet on a page.