npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

base69

v0.1.0

Published

Base69 encoding. Nice!

Downloads

8

Readme

Base69

Base69 is a binary-to-text encoding scheme inspired by Base64 encoding.

Why Base69 when Base64 is adequate? Because it's NICE!

Technique

Base69 is similar to Base64 - it uses a set of 69 characters (not 64) to represent the data and uses the character = to indicate padding.

Base64 works with blocks of 3 bytes which can be broken into four 6-bit chunks. (6 bits can represent 64 values).

Base69 works with block of 7 bytes instead which can be broken into eight 7-bit chunks. (Need at least 7 bytes to represent 69 values; and since 7 is prime, need at least 7 bytes to break the data into 8 chunks of 7 bits).

The 69 characters in the set are:

ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/-*<>|

Algorithm

  • Divide the input byte stream to 7 byte chunks.
  • Divide the 56 bits in a chunk to 8 groups of 7 bits.
  • Take the numeric value (n) of each 7 bit group and turn them into a 2 character string: Divide n by 69 and get the quotient and remainder. The string's first character is the character corresponding to the remainder and the second character corresponds to the quotient from the 69-character dataset.
  • If the trailing data is less than 7 bytes, then extra bytes of value 0 are added at the end to make a 7-byte chunk.
  • The last two characters of the encoded padded data are replaced by p= whre p is the number of bytes padded at the end. e.g. if the data at the end is 4 bytes long, 3 bytes are added. So the last 2 characters in the encoded string will be 3=

Implementations

A basic Javascript implementation is added to this project. Implementations in other languages are welcome from contributors.

View demo that turns text to Base69 strings and vice versa.

Javascript API

export declare function encode(bytes: Uint8Array): string;
export declare function decode(value: string): Uint8Array;

FAQ

Why implement Base69?

Because it's noice!

Is it better than Base64?

Not really

License

MIT License (c) Preet Shihn