But, why won't everyone join Mastadon instead?!?
Thank goodness they go to BS.
fmstrat
joined 1 year ago
Yup, it does. I think I still have my server hard coded from when it first launched.
To me, an alternative model would be deep-linking/embedding 3rd party videos that you own.
For instance, sign up at @server, then:
- Connect your YouTube account
- Post Video 1 to YouTube
- You now have a Video 1 in your federated feed with a YouTube embed
- Connect your Vimeo account
- Post Video 1 to Vimeo (same hash and/or title)
- Your feed entry of Video 1 is updated to support both back end videos
This way your "feed" is federated, but the efficiency of centralized video content is used. If a provider goes down, or you choose to leave, you can re-up to another provider and with the connected account/title matching, your feed could be auto-updated.
I'm not sure I agree with the other OP, I haven't used Kdenlive, but I thought it lacked OpenGL and Decklink support compared to Shotcut. Personally been very happy with Shotcut after using Premier and After Effects previously.
I know people who have, so I would disagree.
The problem with Peertube, IMO, is you can't just "join".
Pick an instance, it's locked down. I get it, hosting others video content is costly and dangerous, but it's also a huge barrier.
Will this happen with AI models? And what safeguards do we have against AI that goes rogue like this?
Yes. And none that are good enough, apparently.
If it begins to enshitify, someone will quickly take up the helm. It's become so core now that someone like Cloudflare would just be like "We do this now."
Let me know if it works out for you, if not I can try to help.
Or man 😉
Yea, it works for me, but there were no great guides. If nothing is in the DB, try checking HTTP error codes, or setting the RUST_LOG to trace (which gives you a log line for every item synced).
A problem I had that seemed like nothing was saving was the nginx proxy wasn't doing things right, and I couldn't tell. Using the local IP worked, and after making some nginx config tweaks I got it working.
I ended up making suggestions here based on my experience: https://github.com/porelli/firefox-sync
I didn't exactly use that repo, but started with it and use their images. Their nginx config works, though.
To make this simple:
Lemmy: One user follows a community from another server, content federates from all users commenting and posting. It takes one follow to start that flow.
Mastadon: One user follows another, content federates for that one user. It takes a lot of follows to get significant content movement.
In addotion, it is much more likely that out of 10 servers, the same communities are followed vs the same people.