Loops in its current state would wreak havoc on Mastodon and other fediverse platforms that cache remote media
This is why it doesn't federate yet, and isn't fully open source.
Loops is serving TBs of video per day, and we don't even federate yet.
Which is why I'm working on a solution to minimize bandwidth, and leveraging the upcoming FediCDN initiative.
We're going to get this right, and without other fediverse servers having to pay for this expensive video federation!
Stay tuned.
Shlee fucked around and @shlee 3d models :)
@Floppy oooh nice... I wonder if you could get mastodon to add support for STL rendering.
@shlee it’s on my list, it’d be great to have that work!
@dansup Could you explain a bit more about the relationship between Loops not federating yet, and Loops being closed source? It isn't really clear, I think, how those two things are tied together. The only link between the two things that I can think of is it that you're keeping the source closed for now to prevent people from forking + updating the code themselves to enable federation support, and then deploying their own instances with the forked code. Is that it?
And even if that is the case, why not just defederate from those instances?
The Lemmy admins had a similar issue when dealing with instances that were mirroring reddit content.
Dan, wouldn't it be better if you started relying on the *community* to help you instead of clamming up in the hopes to come out with a solution to a perceived problem?
Look at the language:
> *We're* going to get this right
> *I'm working* on a solution to minimize bandwidth
Do you see the problem?
You've raised an incredible amount of money, which shows that people have confidence in you and believe you when you say you want to make this a real community effort.
It's okay if your software is open and it has flaws. But it's not okay if you keep this cycle of hyping up something for months (years, now?) and when push comes to shove you just continue doing things on your own.
Specifically about the loops situation:
1) this should not be an excuse to keep the source code closed. If other instances start pushing too much video, admins can just defederate them.
2) Please avoid reinventing yet-another wheel. Inventing is fun, but forcing others to use your inventions all the time is not. Webtorrents are already a thing. IPFS is already a thing. Just pick one solution that is content addressable and makes distribution scale with the number of consumers.
@dansup open source it and let the community work with you to make this right.
@dansup you're going to end up with a central server with millions of users and a hundreds of tiny instances that rely on the larger one for content. A bit like Mastodon.social (though worse!). Where there are a couple huge instances with good marketing and SEO and loads of tiny ones.