cryptocoin
pg-emoji
| cryptocoin | pg-emoji | |
|---|---|---|
| 1 | 1 | |
| 15 | 54 | |
| - | - | |
| 0.0 | 0.0 | |
| over 4 years ago | over 3 years ago | |
| Python | PLpgSQL | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cryptocoin
-
Pg-Emoji
This strikes me as data validation, which should reside in the application layer - I don't see how pg-emoji helps in any way.
Further... if the receiver can validate the encoded string itself, they implicitly already have the string. Why require the user to copy/paste at all? If you meant "Ensure that the user hasn't copied quotation marks as well", then we're back to it being application logic.
If I'm understanding correctly that the primary benefit is that there is a checksum, then there are already many solutions for this in common use - base58checksum, as used to ensure the validity of Bitcoin addresses, comes immediately to mind. I wrote an implementation of that quite a while ago: https://github.com/lyndsysimon/cryptocoin/blob/primary/crypt...
Please don't misunderstand, I'm in no way intending to be argumentative. I don't understand the practical use of this project, which leads me to believe that there is a problem being solved that I lack the context to identify.
pg-emoji
What are some alternatives?
base65536 - Unicode's answer to Base64