William Krick

I'm seeing the same thing. I'm not sure how to debug this. I don't know if the error is in the MPD service itself or if the issue is with...

I've managed to update the app so that it works correctly with the latest version of Vue. I've created a pull request... https://github.com/florianheinemann/MPD.FM/pull/8 ...from my modified fork... https://github.com/wkrick/MPD.FM

@r0b- @pieroxy I propose two new methods... - `compressToURISafe()` or `compressToURISafeEncoding()` - `decompressFromURISafe()` or `decompressFromURISafeEncoding()` With "URI Safe" being the "Unreserved" characters defined in [RFC 3986](https://www.ietf.org/rfc/rfc3986.txt) as discussed here... https://joshbuchea.com/uri-safe-characters/...

@r0b- @Rycochet I just came across something called Base64URL which is described in Section 5 of RFC 4648 back in 2006... https://www.rfc-editor.org/rfc/rfc4648#section-10 ...and explained in more detail on this website......

@HelloLudger - I think the reason is because an empty string isn't a valid Base64 encoded string. There's no inputs into the Base64 encoding algorithm that generate an empty string...

@HelloLudger Interesting. The test cases proposed in the RFC clearly indicate that encoding an empty string results in an empty string... `BASE64("") = ""` I stand corrected.

If you're adding a corrected endpoint for base64, how do you feel about a new corrected endpoint for compressToEncodedURIComponent? https://github.com/pieroxy/lz-string/pull/127

@Rycochet Regarding the 'Add "corrected" encodedURI endpoint' item, there's already an RFC for a Base64URL encoding scheme that I referenced in a comment on a different PR. I think we...

I think that the stats on the right side are literally just the values you get from your gear broken out into different categories. - System Corruption - Armor on...

> Beeloo0011 what? @karnthis I think this is a bot. Their GitHub history is really bizarre. Like they're probing for insecure repos or something.