Ticket created by ~edwardloveall on ~edwardloveall/Scribe
Visiting articles like this one will work but the user gets a certificate error. This is because only the main scribe.rip site has a valid certificate. Although recently-ish Let's Encrypt started offering wildcard certificates. I can use these to make all scribe subdomains HTTPS enabled.
Comment by ~edwardloveall on ~edwardloveall/Scribe
I shipped a new version today that explains how Scribe only supports article pages. You can check it out by trying to visit the page for a user, a tag, or search results.
REPORTED RESOLVED FIXED
Comment by ~edwardloveall on ~edwardloveall/Scribe
Hi royi, thanks for the report. I recently switched from showing gist embeds to rendering them inline, partially to fix some bugs but also partially for privacy. It's possible I could also try to render jupyter notebook images, but I think given the time I personally have to work on this project it's unlikely.
It is possible that in the future I'll add some way to display the normal embedded iframes again which would show these images just like they're shown on medium, but that won't be for a while. I'll leave this open for now.
Comment by ~edwardloveall on ~edwardloveall/Scribe
Hi sircmpwn 👋🏻
Right now I am struggling a little bit to keep up with Scribe alone, so I it wouldn't be sustainable for me to add and maintain Substack support. Maybe one day. Also, there's probably enough in Substack (paid subscriptions, each account is a subdomain, newsletter discovery, how good or bad is their API) to warrant it's own code base.
I'll mark this WONT_FIX for now. If someone feels inspired and wants to use Scribe as a starting point to make their own, please do! And thank you for the suggestion 🙂
REPORTED RESOLVED WONT_FIX
Comment by ~edwardloveall on ~edwardloveall/Scribe
This is now fixed and deployed as of commit 7d0bc37 version 2022-01-30
The bug actually had nothing to do with the URL but everything to do with how Medium calculates offsets for where to mark up text like bold or a link. Medium uses UTF-16 character offsets (likely to make it easier to parse in JavaScript) but Crystal uses UTF-8. Converting strings to UTF-16 to do offset calculation then back to UTF-8 fixes this.
The reason this author had the problem is they put a block of text near the end of their post describing (I think) how to support them. It included two 💸 emoji, and the very end of their text had a different style than the rest. When crystal went to grab that piece of the string, the emoji pushed the indexes out beyond the end of where it thought the text was and then it crashed.
More info in the commit log here.
Thanks for the report!
REPORTED RESOLVED FIXED
Comment by ~edwardloveall on ~edwardloveall/Scribe
Hi amolith. Yeah, that's not a great user experience. While displaying user pages doesn't like up with Scribe's goals, I do like your idea of informing the user that it's not supported, and why. I'll put it on my list.
Comment by ~edwardloveall on ~edwardloveall/Scribe
Hello! This is now fixed and Scribe is proxying gists. I'm going to mark this as fixed but comment here or open a new issue if you find that it's not working. Thanks for the initial report!
REPORTED RESOLVED FIXED
Comment by ~edwardloveall on ~edwardloveall/Scribe
Whoops! That's what I get for trying to triage when I get up in the morning. Good eye, Timo.
Comment by ~edwardloveall on ~edwardloveall/Scribe
Comment by ~edwardloveall on ~edwardloveall/Scribe
Thanks Timo, great find! I'll see what I can do to fix this. I'm doing this in my free time so I'm not sure when it will be fixed.