nielsvanvelzen

Jellyfin API Authorization

To start using the Jellyfin API, authorization is probably the first thing you'll need to do. Jellyfin's authorization options can be a bit confusing because there are a lot of deprecated options.

Generally there are three ways to authenticate: no authorization, user authorization with an access token or authorization with an API key. The first way is easy, just do nothing. But most often you'll need to use either the access token or API key.

Sending authorization values

There are multiple methods for transmitting authorization values, however, some are outdated and scheduled to be removed. It's recommend to use the Authorization header. If header auth isn't an option, the token may be sent through the ApiKey query parameter. Sending secure data in a query parameter is unsafe as the changes of it leaking (via logs, copy-paste actions or by other means) are high. Only use this method as a last resort.

indaco

[Named] Colors and Palettes

A named colors approach for color palettes from Color And Fonts by Michael Andreuzza to be used with TailwindCSS

Warm Palettes

Palette 001 (Warm #1)

// tailwind.config.js

zaus

var FormRepo = function (namespace) {
	/// <summary>Persistent form values, saves to localStorage</summary>
	/// <param name="namespace" type="String">the namespace to store values in localStorage</param>

	// should also protect per page, since we could have the same forms in various places
	this.N = namespace + '.' + window.location.pathname;
};
$.extend(FormRepo.prototype, {
	namespace: function (key) {
		return this.N + '.' + key;