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.
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.