Commit Graph

23 Commits

Author SHA1 Message Date
Edward Loveall 6a38a1cebc
Update CHANGELOG 2023-05-06 13:18:13 -04:00
Edward Loveall 815f5c19f0
Update to nodejs 16.18.0
It was pretty old, but also it wasn't installing correctly on an Apple
Silicon machine.
2022-11-06 17:33:20 -05:00
Edward Loveall bf31305617
Version 2022-10-30 2022-11-04 18:25:14 -04:00
Edward Loveall d7ea1174ff
Updates to pre/code config
This ensures that code blocks look good at all screen sizes.
2022-10-11 20:33:18 -04:00
Edward Loveall 48204b039b
Remove downloadable Redirector config 2022-09-24 15:59:37 -04:00
Edward Loveall 7e927469dc
Replace Redirector extension with LibRedirect
Since Scribe launched, the Redirector extension config has needed
occasional attention. Using regular expressions to cover all edge cases
is difficult. After finding out that Scribe's current config can hang
websites, I decided that [LibRedirect] is likely a more robust
solution. It can rely on more than regular expressions, and is less
work to set up.

[LibRedirect]: https://libredirect.github.io/
2022-09-24 15:50:38 -04:00
Edward Loveall 4097aa20df
Fix Redirector config escaped strings
When printing out the configuration JSON, the Redirector extension
expects regex escapes to be escaped, themselves. So `\` becomes `\\`.
However, Crystal treats these as escaped character also, and each `\`
must additionally be escaped, so a single slash becomes `\\\\`
2022-07-19 16:28:23 -04:00
Edward Loveall 449ece843a
Provide a configuration file for the Redirector extension
Instead of providing long detailed instructions for how to configure
the Redirector extension, this provides a single json file that users
can import. I started by making a single file stored in the
`public/assets` directory, but then realized this was a regression since
the instructions were customized to each domain. Instead I can use
Lucky's [data] response to dynamically build the JSON config.

[data]:
https://luckyframework.org/guides/http-and-routing/request-and-response#
handling-responses
2022-07-17 15:00:03 -04:00
Edward Loveall 269ccc1bef
Scroll long code blocks
This sets the width of code blocks to be the width of the page, and
adds a scrollbar for long blocks. Article `c146e768bb41` has some
examples.

I could have also wrapped the codeblocks, but as pointed out by
[~kaki87] this often reduces readability. Hence: scrollbars.

[~kaki87]: https://todo.sr.ht/~edwardloveall/Scribe/6#event-188395
2022-07-17 13:23:03 -04:00
Edward Loveall 5b20d3f6d1
Upgrade to Crystal 1.5.0 2022-07-17 12:39:48 -04:00
Edward Loveall 35b72ada37
Upgrade to Lucky 0.30.1
Upgrading to 0.31.0 should be very easy. It's just running `shards
update` in the root of the project. That should be all.
2022-07-17 11:55:51 -04:00
Edward Loveall 740230d451
Fix source code link
Capitalize the `S` in `Scribe`. I don't have record of this ever
needing to be capitalized before, but it clearly does not work.
2022-07-17 11:30:03 -04:00
Edward Loveall f05a12a880
Add support for missing posts
Posts, like 8661f4724aa9, can go missing if the account or post was
removed. In this case, the API returns data like this:

```json
{
  "data": {
    "post": null
  }
}
```

When this happens, we can detect it because the parsed response now has
a nil value: `response.data.post == nil` and construct an `EmptyPage`
instead of a `Page`. The `Articles::Show` action can then render
conditionally based on if the response from `PageConverter` is a `Page`
or an `EmptyPage`.
2022-06-17 16:00:01 -04:00
Edward Loveall 1dcded9153
Update changelog to mention no DATABASE_URL 2022-05-21 15:02:06 -04:00
Edward Loveall 93f5cb2d9e
Update CHANGELOG 2022-04-04 20:41:00 -04:00
Edward Loveall 80b6b51804
Fix redirection pattern
Commit 6ea0586423 improved redirection
instructions, but regressed in one way. The "Redirect to" pattern
specified a slash which was accounted for in the main pattern, which
resulted in a double slash:

https://medium.com/@user/post-123456abcdef

would redirect to

https://scribe.rip//@user/post-123456abcdef

This removes the extra slash
2022-03-12 12:03:23 -05:00
Edward Loveall fb51270f87
Fix article ID parsing bug
Since the article ID regular expression wasn't anchored to the end of
the URL, it would grab characters after a / or - that were hex
characters. For example /@user/bacon-123abc would just grab `bac`. Not
great.

This anchors the ID at the end of the string so that it will be more
likely to catch IDs.
2022-02-13 21:07:50 -05:00
Edward Loveall 1f517f9031
Link to full Medium URL on error page
Previously the link on the error page was only linking to the path
component of the url, e.g. `/search` but ignoring any query params e.g.
`/search?q=hello`. This uses the HTTP::Request `resource` method which
appears to capture both.
2022-02-13 10:13:24 -05:00
Edward Loveall 24d3ab9ab3
Better article ID parsing
A new ArticleIdParser class takes in an HTTP::Request object and parses
the article ID from it. It intentinoally fails on tag, user, and search
pages and attempts to only catch articles.
2022-02-13 10:10:46 -05:00
Edward Loveall f056a0b68a
Better error pages
Instead of showing the default Lucky error page, the styles now match
Scribe. In addition, if a URL can't be parsed, Scribe gives some
information as to why this might be (that Scribe can only deal with an
article pages)
2022-02-12 17:56:36 -05:00
Edward Loveall 7d0bc37efd
Fix markup errors caused by UTF-16/8 differences
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 UFT-8 fixes some markup bugs.

---

Medium calculates markup offsets using UTF-16 encoding. Some characters
like Emoji are count as multiple bytes which affects those offsets. For
example in UTF-16 💸 is worth two bytes, but Crystal strings only count
it as one. This is a problem for markup generation because it can
offset the markup and even cause out-of-range errors.

Take the following example:

💸💸!

Imagine that `!` was bold but the emoji isn't. For Crystal, this starts
at char index 2, end at char index 3. Medium's markup will say markup
goes from character 4 to 5. In a 3 character string like this, trying
to access character range 4...5 is an error because 5 is already out of
bounds.

My theory is that this is meant to be compatible with JavaScript's
string length calculations, as Medium is primarily a platform built for
the web:

```js
"a".length // 1
"💸".length // 2
"👩‍❤️‍💋‍👩".length // 11
```

To get these same numbers in Crystal strings must be converted to
UTF-16:

```crystal
"a".to_utf16.size # 1
"💸".to_utf16.size # 2
"👩‍❤️‍💋‍👩".to_utf16.size # 11
```

The MarkupConverter now converts text into UFT-16 byte arrays on
initialization. Once it's figured out the range of bytes needed for
each piece of markup, it converts it back into UTF-8 strings.
2022-01-30 11:53:22 -05:00
Edward Loveall 648a933b24
Provide a list of instances as JSON
This is for extensions or other tools that wish to have a list of
instances. It can be accessed by visiting the raw file on sourcehut:

https://git.sr.ht/~edwardloveall/scribe/blob/main/docs/instances.json
2022-01-29 12:58:08 -05:00
Edward Loveall 3a8ad82252
Add CHANGELOG 2022-01-23 15:06:01 -05:00