Today we've crossed the line of 500 users registered on read.cash. It's not a big, but it's definitely a nice number. 🎉

Of course, there are relatively unknown people on Twitter that have more followers, but the number growing, which is nice, and all these people get to experience the magic of Bitcoin Cash as cash, which is even nicer!

That bump at the end - it's the article about read.cash by Jamie Redman on bitcoin.com. Thanks, Jamie!

Thank you everyone who registered and a huge thank you to everyone who upvotes the authors!

A few updates that we've rolled out today.

Language selection

You'll have to choose the language for the article now.

Previously, we've had it set by default to English, but many people publishing in foreign languages didn't even notice the selector, so we've had to set a bunch of articles to the proper language.

Now, you'll have to explicitly set the language.

Don't worry, it takes about a second.

Lead images

Many people were confused by the lead image and expected it to appear in the article somehow.

We are at fault here, we didn't have time previously to write the code that would do that. These images were only used for the thumbnails.

As of today, you can finally set the lead image either as a heading background or as a first image in the article or explicitly use it for the thumbnail only.

...or just use it as a thumbnail (it won't show up in the article).

Profile Links

Our "Written by" block was getting a bit crowded, so we've replaced text links with icons and the "edit" link with a pencil icon. It was confusing, because there were two "Edit" links - one for the profile links, another one for the article itself.

bchd migration

Yesterday we've started a migration to bhcd, because some people occasionally experienced problems with rest.bitcoin.com (including all of the Tor Browser users).

Almost all of the client-side (in browser) code of read.cash has been migrated to bchd.fountainhead.cash.

In the meantime, our bchd node finishes syncing up - we'll see if it's better to keep Fountainhead or switch it to our node.

Anyway, this hopefully fixings these CORS problems that some of the users were having. (See the previous article for explanations)

Draft links

Occasionally, it's needed to get an opinion of somebody about your article before you publish it. To check for any errors, for example, or to proofread it.

Now, it's possible. Just click the "Preview article" link and you'll get a link you can share.

Back to editor

There was also a minor nuisance: occasionally, if you edited an article, then opened a link, then clicked "Back" - the editor would load the article from Chrome's cache, which would be the previous version of the article, not the latest. That was pretty bad, we're now forcing Chrome not to do that anymore.

That's it. Have fun!