#go#compression#decompression#deflate#go#golang#gzip#snappy#zip#zstandard#zstd
The "github.com/klauspost/compress" package offers many fast and efficient compression tools in pure Go, including zstandard, S2 (a faster Snappy replacement), optimized deflate for gzip/zip/zlib, and snappy with better compression and concurrency. It also provides entropy encoders (huff0, FSE), HTTP gzip handlers, and a parallel gzip implementation (pgzip). These tools are drop-in replacements for Go's standard libraries but run about twice as fast, saving time and resources. You can easily add it to your project with `go get`. It supports current and recent Go versions and offers options to disable unsafe code or assembly for compatibility. This package benefits you by improving compression speed and efficiency while maintaining compatibility with standard Go compression APIs, making your applications faster and more resource-friendly.
https://github.com/klauspost/compress
https://pypi.python.org/pypi/oauthlib
A generic, spec-compliant, thorough implementation of the #OAuth request-signing logic for python
OAuth often seems complicated and difficult-to-implement. There are several prominent libraries for handling OAuth requests, but they all suffer from one or both of the following:
They predate the OAuth 1.0 spec, AKA RFC 5849.
They predate the OAuth 2.0 spec, AKA RFC 6749.
They assume the usage of a specific HTTP request library.
OAuthLib is a generic utility which implements the logic of OAuth without assuming a specific HTTP request object or web framework. Use it to graft OAuth client support onto your favorite HTTP library, or provide support onto your favourite web framework. If you’re a maintainer of such a library, write a thin veneer on top of OAuthLib and get OAuth support for very little effort.
https://aaronparecki.com/2012/07/29/2/oauth2-simplified#others
OAuth 2 Simplified
Sun, Jul 29, 2012 9:30am -07:00
Many services such as #Facebook, #Github, and #Google have already deployed OAuth 2 servers, and deployed implementations win.
The #OAuth 2 spec itself leaves many decisions up to the implementor. Instead of describing all possible decisions that need to be made to successfully implement OAuth 2, this post makes decisions that are appropriate for most implementations.
This post is an attempt to describe OAuth 2 in a simplified format to help developers and service providers implement the protocol.