If you need to include a + in a query parameter, you may need to use %2B instead, due to a W3 recommendation that causes a + to be interpreted as a space.
I found it be refreshingly pedantic and accurate to refer to it as just a "recommendation" rather than a "requirement" or something... though I'm not actually sure why we call such standard things in the web APIs merely a "recommendation". Can't we just call it a standard at this point?
for - SRG Corporation2CO-OPeration program - worker-owned cooperatives - Apis & Heritage - inequality reduction - via worker-owned cooperatives
summary - Apis & Heritage is a unique US private equity firm that has established an investment fund called "The Legacy Fund" which is used to facilitate Employee-Led BuyOut (ELBO). Studies show the enormous potential for reducing inequality and it is an issue that receives rare bipartisan political support in the US. The "Silver Tsunami" describes 3 million small business owners likely to retire in 2035. Together, their businesses account for $10 trillion in assets. Apis & Heritage helps faciliate a smooth transition for owners to sell to their employees, increasing their net worth by as much as 10x by the time they retire.
We need to be sure employee ownership becomes a movement
for - Apis & Heritage - champions of worker-owned cooperative movement
process
for - Apis & Heritage Legacy Fund employee buyout process - Apis & Heritage values the enterprise and offers seller fair price for their life work - Once purchased, they transfer the company's assets to a trust - Using private debt capital, they finance a portion of that transaction. - The trust administers the ESOP - The seller has full liquidity upfront and can retire immediately, The Legacy Fund saves seller from having to manage the complex process of selling to employees. - ESOP is a retirement account for the new employee-owhers. - After 5 years, each employee become vested, with new share allocations made each year.based on wages as a percentage of total payroll - If value of business grows, so do employee share value. - When employee-owner is ready to retire, they sell back the shares based on current valuation - new employee-owners receive training from Democracy at Work Institute (DAWI) - The trust repays debt from initial transaction on behalf of the business to Apis & Heritage and its investors who make an attractive return -
Plugins are ways of adding new languages or formatting rules to Prettier. Prettier’s own implementations of all languages are expressed using the plugin API.
I'm curious if anyone has ever experimented with making an online Luhmann-esque Zettelkasten using WikiMedia as their platform?
What were the pros/cons you found for doing so?
Have you tried other methods (index cards, Obsidian, other(s)?), and if so what affordances did MediaWiki provide or were lacking for what you were attempting to accomplish?
Did you use transclusion functionality?
Did you attempt to build or implement backlink functionality? Use the API or plugins for this?
Did you build some sort of custom index (manually, programatically, other)?
If you used it for writing, what methods did you attempt with respect to taking the smaller pieces/ideas and building them up into longer written pieces?
Links to specific public examples are welcome here. I'll also accept links to public versions of commonplace books or similar forms which also use MediaWiki as their infrastructure.
syndication link: https://www.reddit.com/r/Zettelkasten/comments/144hzn9/zettelkasten_with_mediawiki/
Problem details for HTTP APIs HTTP status codes are sometimes not sufficient to convey enough information about an error to be helpful. The RFC 7807 defines simple JSON and XML document formats to inform the client about a problem in a HTTP API. It's a great start point for reporting errors in your API. It also defines the application/problem+json and application/problem+xml media types.
Mailgun is primarily a developer’s tool so the best way use Mailgun is through our APIs.
developers first API first
API TypeMailgun API NamePostmark API NameSending EmailsMessagesEmailManaging SuppressionsSuppressionsSuppressionsManaging TemplatesTemplatesTemplatesManaging Sending SettingsServerManaging ServersServersManaging Sent EmailsEventsMessagesManaging Inbound EmailsMessages, EventsMessagesManage Inbound Processing SettingsRoutesManage email domains you can send fromDomainsDomains
The web API is now the most common meaning of the term API
"detail": [ { "loc": [ "body", "name" ], "message": "Field required" }, { "loc": [ "body", "email" ], "message": "'not-email' is not an 'email'" } ]
not complient with Problem Details, which requires details to be a string
For example, let’s consider the type property. For most of the projects I am working on, it isn’t practical to have a webpage dedicated to each type of possible error.
That's not required. The standard doesn't require this to be a URL locator — merely a URI! So you can just make up a URI and use it even if it's not resolvable. ... like you did for the URN below.
For the instance property, the most practical way I’ve found of implementing this is to define a URN that encapsulates additional information regarding the error. Here is an example URN for reference. urn:companyname:api:error:protocol:badRequest:f29f57d7-e1f8-4643-b226-fa18f15e9b71
"type": "https://example.com/problems/request-parameters-missing"
ErrorResponse: description: Container object for one or more errors returned by the API. type: object required: - errors properties: errors: type: array items: $ref: '#/definitions/Error'
FetchErrorResponse: type: object properties: meta: $ref: '#/definitions/FetchMetaResponse' errors: $ref: '#/definitions/Error' example: { "meta": { "req_id": "d07c8b12-c95e-4a06-8424-92aac94bb445" }, "errors": [{ "code": "Unauthorized", "detail": "A valid bearer token is required", "status":"401" } ] }
asdfasdfasdfasdf
Fukuyama's work, which draws on both competition analysis and an assessment of threats to democracy, joins a growing body of proposals that also includes Mike Masnick's "protocols not platforms," Cory Doctorow's "adversarial interoperability," my own "Magic APIs," and Twitter CEO Jack Dorsey's "algorithmic choice."
Nice overview of work in the space for fixing monopoly in social media space the at the moment. I hadn't heard about Fukuyama or Daphne Keller's versions before.
I'm not sure I think Dorsey's is actually a thing. I suspect it is actually vaporware from the word go.
IndieWeb has been working slowly at the problem as well.
The valueAsNumber IDL attribute represents the value of the element, interpreted as a number. On getting, if the valueAsNumber attribute does not apply, as defined for the input element's type attribute's current state, then return a Not-a-Number (NaN) value.
Capacitor's origins lie in Ionic's mission to provide a holistic framework for developing hybrid apps—apps that run on mobile devices, on desktops, and in the browser. It does not only replace Apache Cordova as a “bridge” to native platform access in new Ionic projects but also “provides a consistent, web-focused set of APIs”.
Capacitor is a framework that provides developers a coherent API set to access various features on different platforms. By doing so, it also simplifies using those features. Especially for web APIs that are hard to use or require multiple steps to set them up, Capacitor provides an easy-to-use interface.
Another problem I ran into was knowing when an element is removed. I had to add a MutationObserver on the current tooltip target so if it gets removed by Svelte while the tooltip is visible (e.g. if a click moves to another route) the tooltip isn't left hanging around on the screen. No mouseleave/mouseout events are dispatched on elements that are removed.
First sighting: MutationObserver
Audrey Watters, hackeducation.com Education APIs: The Good, The Bad, and The Ugly
Looking forward to reading/hearing Audrey Water's thoughts on education APIs.