The definitive screen capture utility for macOS, designed with simplicity and efficiency in mind.
Always stay on the cutting edge with built-in automatic updates.
By default, ishare supports and opens .iscu
files for configuration. They are text files containing JSON data according to the iscu
spec:
Note: Version 2.0.0 introduces breaking changes. Follow the migration guide for updates and consider reinstallation if you encounter issues post-update.
The custom uploader specification since version 2.0.0+ has the following structure:
{
"name": "Custom Uploader Name",
"requestURL": "https://uploader.com/upload",
"headers": { // optional
"Authorization": "Bearer YOUR_AUTH_TOKEN"
},
"formData": { // optional
"additionalData": "value"
},
"fileFormName": "file", // optional
"requestBodyType": "multipartFormData", // optional, can be "multipartFormData" or "binary"
"responseURL": "https://uploader.com/",
"deletionURL": "https://uploader.com/", // optional
"deleteRequestType": "DELETE" // optional, can be "DELETE" or "GET"
}
All properties are case insensitive.
This new specification allows for more dynamic URL construction and handles deletion URLs.
For responseURL
and deletionURL
, JSON properties that are derived from the response payload can be defined as ``. There is support for nesting (upload.url
) and arrays (files[0].url
).
responseURL
replaces responseProp
.deletionURL
.responseProp
with responseURL
, ensuring the URL includes placeholders for dynamic values.deletionURL
field.For example,
"responseProp": "fileId"
Turns into:
"responseURL": ""
Before:
{
"name": "uploader",
"requestURL": "https://uploader.com/upload",
"responseProp": "fileUrl"
}
After:
{
"name": "uploader",
"requestURL": "https://uploader.com/upload",
"responseURL": "" // also supported: "https://uploader.com/"
}
ishare is confirmed to be compatible with the following uploader services:
Released under GPL-3.0 by @castdrian