Jan Vogt

I could offer the M1 Pro (in an MBP)

+1

I see. But it makes this lib unusable in contexts where data: URIs might exist. If that's intended, this can be closed.

As far as I understand RFCs, it is valid though. See the example at [RFC 2397](https://tools.ietf.org/html/rfc2397) which also contains consecutive slashes.

I'd really like to use the library, but since `data:` URIs are pretty ubiquitous in modern web, this library is unusable for manipulating websites without support for it. Maybe @mrkkrp...

Actually, I did a little more digging. Let me tell you, that I become to appreciate this library striving to follow the general URI handling rules laid out in [RFC...

One more thing: IMHO the roundtrip property ```haskell import Text.URI prop_roundtrip :: Text -> Bool prop_roundtrip uri = render mkURI uri == (pure uri) ``` should really hold for all...

Yes indeed it's just base64 encoded binary. Which is totally fine with the generic parsing algorithm, as long as there is no normalisation happening by incorrectly assuming a hierarchy. If...

Ok, I'm on it.

Hitting this as well with a unsafed scratch buffer. Closing it and reloading the window get's rid of the second hls process (the one with the cradle located at '/')