Cautionary tale about why FOSS is important. Also about why Kbin lacking an official API is a problem.
this post was submitted on 09 Dec 2023
84 points (100.0% liked)
Technology
37708 readers
348 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
I would say it’s more a cautionary tale about how people’s health is often far more important than anything we do in daily life. This focus on deliveries over life is quite worrying
True... It amazes me when people become so entitled online, especially in the FOSS community. It looks like they think devs owe them something.
They got free testing for the promise of releasing the source, then failed to fulfill that promise, so... yeah, they do owe those people something.
Case and point? If they're not being compensated, they have no obligations to anyone. "Free testing" isn't compensation unless they plan to monetize it later using improvements from that testing.
Oh, legally they have no obligations unless written so in a binding contract. Ever seen a failed Kickstarter or a cancelled Patreon? No obligations, even if they get compensated in USD. Plenty of those out there.
Morally, the people giving that free testing and community building are still owed what they were promised, no less no more.
Why was there even pressure to deliver if the official API wasn't even out yet? I thought they were just working on UI and basic functionality until they can plug in the API, so if anything they had more time and leisure than if everyone were screaming "i need it now". It seems more likely they just bit more than they could chew and decided to give up the app development since it ended up being harder than they thought (and that's completely fine to do). You don't really make an app like this overnight, especially if you have no prior experience doing it.
Case in point, Ernest had to take a month off kbin development to handle things in his personal life. I, too, have abandoned open source projects due to lack of interest. I think people incorrectly assume that the internet offers a level of permanence unmatched by real life, when in fact it only highlights the ethereal nature of anything people build.
From a business perspective, that would be the case, also a cautionary tale about running a solo business.
However, the article says they planned to release the source, and had already managed to get a community of over 1000 people interested in the project, so I think the community perspective is more applicable.
At the time, Kbin’s API was largely unfinished, meaning that technically, no Kbin instances supported apps of any kind.
Lack of a formal API to work with was tricky. There were discussions in Kbin’s development tracker about formally merging in support for apps, but it wasn’t ready for prime-time. Typically, adding a client API that’s well-rounded enough for mobile apps necessitates a lengthy checklist for requirements. Long story short, it’s a time-consuming process.
Some of the work she did -- having to drive the thing off scraping the UI, without using a kbin API -- is probably effectively being obsoleted, since kbin's API stuff is coming out now:
https://kbin.social/m/ArtemisApp/t/639282/API-to-be-unlocked-in-the-next-kbin-update
So it may be that what will happen is that existing lemmy apps will just add support for the kbin API.
Shocked.