My fear with pixelfed and loops is the single dev seemingly more interested in money and clout than in building something long lasting for the community. I don’t expect it to last long, but my friends really crave an app to exchange reels in and so we’re hoping loops will be sufficient until something more stable comes around.
Yeah, this one guy has been trying to jumpstart so many projects. And that’s admirable, but it’s also too much for one dude (and I know he’s tried to get some other people, but there has been drama around that - by him, I think).
But more to your point - something feels a little off even though I can’t confirm anything. It does feel like this guy might just take some money and run if given the chance.
And I don’t necessarily blame him for that - I probably would too. I don’t want to work, and if I had money I wouldn’t.
But there’s just this feeling I can’t shake about all of it. And I have a Pixelfed and a Loops account. They are both fine, so we’ll see, I guess. But I wouldn’t be surprised if I end back up with Mastodon being my sole social place for sharing photos, for example.
New to open source? Good ideas don’t really die in open source. If loops.video or Pixelfed are good ideas, open source will just do its thing because no one owns the idea once it goes open source
I see the backend and front end released. The back end is AGPL and the front end does need a license (assumed it had one, my bad). Assuming he puts the same AGPL license on the front end, I don’t see anything unsubstantial? The community gets to make squooshloops or whatever name comes up and the backend and front end belongs to them at that point to release on their hardware.
It’s all ActivityPub, so mastodon users wouldn’t miss see a thing go wrong? Start subscribing to squooshloops.social accounts from your instance’s deprecated Pixelfed software like nothing happened because the squoosh devs were smart to make it compatible with other ActivityPub apps. Once adoption hits a masse, and maybe ActivityPub specs changed, and squoosh added new things to their spec that other services expect or depend on, new versions of squoosh and other activitypub software stop trying to be backwards with the unmaintained pixelated and loops.video software. Those instances are forced to use a fork or stop federating with those other instances who no longer support the old stuff. The world keeps moving and remember that time when squoosh was originally that failed loops thing.
Kinda like how Chrome has its roots in WebKit which has its roots in KHTML which has its roots in KDE. I’m not seeing a problem honestly. Yes, KDE’s konqueror is dead (rip, I used KDE and loved that jelly K browser icon ever since I was like 12 in 2005). It lives on in chromium though, and has spread all over the world because of electron. Very weird story for that browser, but it somewhat shows my point: open source doesn’t die. It isn’t perfect — lots of valid complaints about chromium and electron, but none of the valid complaints are “that idea is gonna die if Google dies”
Well that’s great news if you’re right. It doesn’t change that the creator seems to be immature and therefore not the most reliable social media Steward, but if the SW keeps getting developed or a better system comes from the open source nature as you suggest then I’ll be happy.
Good ideas absolutely do die all the time even in open source. If the original dev doesn’t want to play nice, it’s actually pretty difficult to create a new fork that everyone will agree on. Hopefully these federated apps have enough inertia to prevent the userbase from splintering when the original devs move on.
What’s a good idea in open source that did die (and is still absolutely dead, even)? I’m sure you can find a GitHub project and be like “I like this idea and it’s dead” fine. But these projects are so used and popular… they aren’t going anywhere. That’s the context of this discussion. These apps are fine if the dev leaves because they are open source now. The right people will continue the work of this guy goes I think.
My fear with pixelfed and loops is the single dev seemingly more interested in money and clout than in building something long lasting for the community. I don’t expect it to last long, but my friends really crave an app to exchange reels in and so we’re hoping loops will be sufficient until something more stable comes around.
Yeah, this one guy has been trying to jumpstart so many projects. And that’s admirable, but it’s also too much for one dude (and I know he’s tried to get some other people, but there has been drama around that - by him, I think).
But more to your point - something feels a little off even though I can’t confirm anything. It does feel like this guy might just take some money and run if given the chance.
And I don’t necessarily blame him for that - I probably would too. I don’t want to work, and if I had money I wouldn’t.
But there’s just this feeling I can’t shake about all of it. And I have a Pixelfed and a Loops account. They are both fine, so we’ll see, I guess. But I wouldn’t be surprised if I end back up with Mastodon being my sole social place for sharing photos, for example.
New to open source? Good ideas don’t really die in open source. If loops.video or Pixelfed are good ideas, open source will just do its thing because no one owns the idea once it goes open source
Isn’t the point of this thread that the code isn’t actually open source - that the released code isn’t anything substantial?
I see the backend and front end released. The back end is AGPL and the front end does need a license (assumed it had one, my bad). Assuming he puts the same AGPL license on the front end, I don’t see anything unsubstantial? The community gets to make squooshloops or whatever name comes up and the backend and front end belongs to them at that point to release on their hardware.
It’s all ActivityPub, so mastodon users wouldn’t miss see a thing go wrong? Start subscribing to squooshloops.social accounts from your instance’s deprecated Pixelfed software like nothing happened because the squoosh devs were smart to make it compatible with other ActivityPub apps. Once adoption hits a masse, and maybe ActivityPub specs changed, and squoosh added new things to their spec that other services expect or depend on, new versions of squoosh and other activitypub software stop trying to be backwards with the unmaintained pixelated and loops.video software. Those instances are forced to use a fork or stop federating with those other instances who no longer support the old stuff. The world keeps moving and remember that time when squoosh was originally that failed loops thing.
Kinda like how Chrome has its roots in WebKit which has its roots in KHTML which has its roots in KDE. I’m not seeing a problem honestly. Yes, KDE’s konqueror is dead (rip, I used KDE and loved that jelly K browser icon ever since I was like 12 in 2005). It lives on in chromium though, and has spread all over the world because of electron. Very weird story for that browser, but it somewhat shows my point: open source doesn’t die. It isn’t perfect — lots of valid complaints about chromium and electron, but none of the valid complaints are “that idea is gonna die if Google dies”
Well that’s great news if you’re right. It doesn’t change that the creator seems to be immature and therefore not the most reliable social media Steward, but if the SW keeps getting developed or a better system comes from the open source nature as you suggest then I’ll be happy.
Good ideas absolutely do die all the time even in open source. If the original dev doesn’t want to play nice, it’s actually pretty difficult to create a new fork that everyone will agree on. Hopefully these federated apps have enough inertia to prevent the userbase from splintering when the original devs move on.
What’s a good idea in open source that did die (and is still absolutely dead, even)? I’m sure you can find a GitHub project and be like “I like this idea and it’s dead” fine. But these projects are so used and popular… they aren’t going anywhere. That’s the context of this discussion. These apps are fine if the dev leaves because they are open source now. The right people will continue the work of this guy goes I think.