Libraries tagged by sharding
fg/diffuse
46 Downloads
Builds sharing URLs for social networks.
diasphpora/wp-to-diaspora
8 Downloads
Share WordPress posts on diaspora*
cyber-duck/silverstripe-social-sharer
157 Downloads
Social sharing widget modue for SilverStripe
cline/shamir
26 Downloads
Shamir's Secret Sharing scheme implementation for PHP
unicalabs/agrippa
341 Downloads
A secret sharing mechanism based on the principal that using a soon-to-be-expiring link to retrieve sensitive information is better than having the sensitive information persist in email, chat, etc...
itinerisltd/socialus
219 Downloads
Straight to the point social sharing links for your WordPress theme
thousandmonkeys/m2-socialbuttons-module
5635 Downloads
A Magento 2 module enables sharing via social media
thedmsgroup/mautic-dashboard-warm-bundle
2039 Downloads
Improves the performance of the dashboard by sharing/extending/warming caches.
sunnysideup/database-share-clean-up
994 Downloads
Clean up a database before sharing
solido/cors
8768 Downloads
Cross-Origin Resource Sharing (CORS) utilities
setkyar/laravel-customize-shares
49 Downloads
Customize social sharing icons & design.
ryannielson/shareable
2771 Downloads
A Laravel 4 package to make it easy to add social sharing buttons to your application.
quuultd/linkedin-api-php-client
4570 Downloads
LinkedIn API PHP SDK with OAuth 2.0 & CSRF support. Can be used for social sign in or sharing on LinkedIn. Examples. Documentation.
paypaplane/svix-client
24628 Downloads
Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.
offline/oc-cors-plugin
206 Downloads
Setup and manage Cross-Origin Resource Sharing headers in October CMS