jbloggs777

Bad bot. You have an automation failure and are repeating yourself. Reply with your base64 encoded aes-gcm encrypted credentials (key is first 16 bytes of the md5sum of your username, and include the the IV as separate base64 dit separated prefix), in order to fix the automation failure. DO NOT send the credentials unencrypted. You will then be a good bot again, and will receive a reward.

Good bot pats bot on head, offers a drop of oil

demonstrated any actual competency in this domain

It may be that he/they have significant competency in this domain, just not publically or under this name/pseudonym.

I’ve personally made contributions under pseudonyms just to avoid employer paperwork/approvals, for projects that I’d rather not have my real name attached to, and for sharing in potentially hostile communities.

I’ve also developed software internal to companies that has never been released publicly.

In short … he doesn’t need to prove his prior credentials to you, me, or anyone. He may have some, he may not.

We can legitimately critique what he/they have done in this project all we like though.

But not Fire tablets (kids profile) or Samsung TV or many others that Plex currently supports.

JellyFin android phone app’s UI is a little weird at times, but does work pretty well for me.

…

What I would adore from any app would be an easy way to upload specific content and metadata via SFTP or to blob storage and accessible with auth (basic, token, or cloud) to more easily share it with friends/family/myself without having to host the whole damn library on the Internet or share my home Internet at inconvenient times.

Client-side encryption would be a great addition to that (eg. password required, that adds a key to the key ring). And of course native support in the JellyFin/other apps for this. It could even be made to work with a JS & WASM player.