Don Kimberlin

1 it's sharing the web page url, which Kodi and other video players don't know how to deal with directly. 2 after switching to the a link to the mp4...

VLC is straightforward to get working, Looks like Kodi doesn't register any intent handlers. It could theoretically work by enabling http control in Kodi and then setting up JSON communication...

Podcast2 plugin should be able to function as a work around until this is addressed. It checks the required boxes and is passing all the validators I can find.

Have you looked at administration-overview-comments? Filtering by local comments & comments on local videos is the best way I've found to weed out bad actors.

I to have noticed this behavior on a few of the 2 and 3 vcpu instances I help with. Very noticeable with larger channel imports. It maxes out the CPU...

I just verified and attempting to use an existing user name as a channel name fails with the error:This name already exists on this instance

One of the design goals of the podcast2 plugin is to resolve this registration issue. currently passes the validator. https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fmusic.freediverse.com%2Fplugins%2Fpodcast2%2Frouter%2Fpodcast2%3Fchannel%3Dtomlehrer

This sounds good, but would increase the priority of a "max size" setting in redundancy configuration. 8k livestreams will quickly blow out an instance's local cache.

This seems a natural feature to leverage the tag https://github.com/Podcastindex-org/podcast-namespace/discussions/502