Technology
Which posts fit here?
Anything that is at least tangentially connected to the technology, social media platforms, informational technologies and tech policy.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
!globalnews@lemmy.zip
!interestingshare@lemmy.zip
Icon attribution | Banner attribution
If someone is interested in moderating this community, message @brikox@lemmy.zip.
view the rest of the comments
Your average person is not capable of setting up, hosting, backing up and maintaining a proper Peertube instance. A large part of my dayjob is in hosting and infra, and I have set up a PT instance before. Honestly, even as far as average hosting goes, their setup is kind of needy. Most dockers are like start, port, go these days. As soon as you mandate that they have DNS and a working 443 upfront, you're kicking most people out before they start.
There is no challenge there that cannot be overcome by application architecture. I don't see anything that is a deal braker, and there is definitely a need out there, but it's a damn big project and the makers of PT aren't just doing straight up charity.
Indexer loses heartbeat, content shows up as unavailable. Configurable by admin to disappear from searches after x time. Current watchers: If enough people were watching the stream currently/recently, they'd keep going from each other's cache as peertube will actually peer. (I've tested the peer part, it does what's on the tin) If no one has future segments, they'd get kicked out same as if the server went offline. Most content creators would be pretty careful not to do this. It would also be an interesting thing to explore the mirroring functionality and have small creators team up and mirror each others data, doing a kind of remote replica between friends thing.
That's actually kind of my point. It's mostly Peertube, but without users trying to deal with nginx/apache, redis/postgres, port 80/443 ips issues, SMTP, DNS and SSL. Someone who is capable of dealing with those parts just stitches them on as remote content. The servers don't pay for storage or most of the networking and they help the clients with visibility and getting around ISP limits.
If we try to setup end users with the whole shebang, they're going to run into issues when the Redis goes RO from running out of space/memory, or when they have disk issues and the postgres goes tits up. (or god forbid PT needs a DB upgrade or something) They don't know about services and recovery, they're not capable of setting up backups or running restores.
Hell maybe the app is also the consumption part as well. You watch peertube by running the PT desktop app. Then we can deal with self signed certs. run people on sqlite and local shared host memory instead of redis. We'd still need remote trackers to help orchestrate the DHT.
I duuno, it's big, it's pain. I think if it were available, big tech (and honestly big brother) would be shitting themselves.