Libraries tagged by bencoding

PHP package for Byte Pair Encoding (BPE) used by GPT-3.

Go to Download

Encoding function for bittorrent

Go to Download

Deze bundle bevat de benodigde logica (schema's, mappings en code) voor het omzeten van Sim Form belastingen xml naar ZGW berichten. Ten behoeve van het inrichten van belasting aangiften en bezwaren.

Go to Download

A Laravel 5 wrapper around opencoconut video encoding library

Go to Download

Just encoding

Go to Download

A PHP package for encoding, decoding and cracking the Caesar shift cipher

Go to Download

An project that implements Slim Framework becoming a resource server in a microservice ecosystem with OAuth2

Go to Download

Minify is a PHP app that helps you follow several rules for client-side performance. It combines multiple CSS or Javascript files, removes unnecessary whitespace and comments, and serves them with gzip encoding and optimal client-side cache headers

Go to Download

An implementation of the Radix-64 encoding as described by OpenPGP (RFC 4880).

Go to Download

Recursive Length Prefix Encoding in PHP.

Go to Download

This is a fork of the original repository. Collection of binary-to-text encoding utilities for PHP. Includes Base32 support and much more.

Go to Download

Services taking care of encoding and decoding XML bodies

Go to Download

Middleware taking care of encoding and decoding XML bodies

Go to Download

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download

Tools to transcoding/encoding audio or video, inspect and convert media formats.

Go to Download