Dave

There’s no exposure, you’re the one suggesting that is the payment but no one is offering exposure, they are asking for volunteer help to contribute to a volunteer run ecosystem.

Many instances ask people to give their labour for free without waiting for someone to offer. Lemmy.world ran a full interview process to appoint volunteer admins.

Something to remember is that the Threadiverse runs on unpaid labour. Someone donating their time to create art is no different to someone donating their time to run the server or develop Piefed ot whatever.

There’s unlikely to be any exposure from the art anyway, so any artist should only do it because they want to contribute to the ecosystem not because they think they will receive exposure in lieu of payment.

What’s up? Not Grafana. I did docker compose pull on the stack (without version pinning) then recreated the containers, and now it’s fucked. Or maybe it’s not because the logs are fine but it only serves the web app but 404s on any connection to the Grafana backend.

Now I need to do some investigation into any recent changes to try to work out what’s going wrong.

I think I tried this when troubleshooting and didn’t notice a difference. Nevermind, I pretty easily taught her how to bring up the menu and switch audio streams so she can solve it herself now.

Thanks, I didn’t manage to find many options in swiftfin, you don’t know if I can enforce it for a user from the server side?

I set up Jellyfin on my mother-in-law’s TV, it’s just push play.

My mum has an Apple TV (the device, not the subscription) and on there she uses swiftfin. The only issue has been sound not working on certain audio tracks on certain movies, but in general it is easy for anyone.

Both are very familiar interfaces for anyone used to playing something from a streaming service.

Isn’t it a bit weird since they already have the technology to see which parts you care about most.

Why do they need to use Gemini instead of just basic data analysis to see where viewership drops at the end of a peak part and insert the ad there?

I guess my position is that I am not worried about someone confirming content exists on my server. But I don’t live in the US, if I did I might be more worried. I also geofence to my country to limit exposure.

Cheers for that. Many of these issues allow a user to do admin actions if they do the right things, so it seems you should never allow a user that you don’t fully trust to have an account.

But outside of this, there isn’t anything in there that on its own worries me given the nature of the platform (that is, that if it all burnt down I could retrieve all data from other sources). I’m no expert but a cursory look shows a bunch of potential issues that may be layered with other issues but no clear attack path except with prior knowledge.

These should obviously be fixed but there’s nothing that makes me want to rip my server off the open internet in a hurry.

What kids of things?

I’ve never worried that much because it’s not critical data and it’s containerised in Docker, but I am curious about specifics because large numbers of people expose it to the internet (through reverse proxies).

Isn’t there an assumption it would be behind a reverse proxy… At least I hope that’s the assumption.