this post was submitted on 15 Jun 2023
660 points (100.0% liked)

/kbin meta

200 readers
2 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 2 years ago
 

I think you should see something.

Like I mentioned many time before, this isn't my first attempt at creating an aggregator. Years ago, I built something similar, and back then I drew a lot of inspiration from Postmill. This time, to avoid starting from scratch, I get some elements from my old snippets. Originally, kbin was meant to be a project just for me and a few friends, so I didn't attribute the origin authors. That's not an excuse, though — I should have done it right away when the project became public on git. I have a point in my roadmap called "Preparing a repository for contributors," where I allocated a significant amount of time to educate myself about licenses, attributions, and so on. Unfortunately, everything unfolded in the wrong order.

https://codeberg.org/Kbin/kbin-core/issues/196

I think Emma is right. Since I share my small successes with you, I also want to be transparent about my failures and mistakes. I will push the proper attributions to the repository today along with some critical fixes.

To avoid reinventing the wheel, I took some code used in federation from Pixelfed as well. Essentially, there are two projects two projects will be marked. However, I have never concealed this fact:

https://kbin.social/m/random/p/254858/The-real-reason-why-I-haven-t-published-the-pixelfed-app#post-comment-438684

I mean that I'm not a guy who wants to steal your code. It's obvious that someone will take a look at the code of a project that is very similar to theirs. Sometimes, I just become terribly messy when I have to do many things at once. This lesson will definitely teach me to prioritize tasks better.

In the end, I can only promise that once everything settles down and I manage to extract a library for ActivityPub, I will revisit the Postmill repository, this time with a pull request proposal.

You should definitely check it out.

https://postmill.xyz/ - Project page
https://raddle.me/ - Postmill instance
https://pixelfed.org/ - Of course, everyone here is familiar with this one ;)

PS. the website should be running a bit faster. I will talk about it next time.

top 50 comments
sorted by: hot top controversial new old
[–] Adderalldependent@kbin.social 205 points 1 year ago (1 children)

This is the kind of transparent communication that buys so much goodwill and trust from the community. I've been enjoying my first experience in the Fediverse with Kbin, and the response here only makes me love it that much more. Nicely handled.

[–] PtitSerpent@kbin.social 51 points 1 year ago (1 children)

I think we did a good choice

[–] JonEFive@kbin.social 24 points 1 year ago (2 children)

Agreed. I had already created an account on a Lemmy instance (Lemmy.one since I wanted to avoid the two main .ml instances). I had just about settled but decided to give Kbin a try. While it doesn't seem quite as far along in it's development, it struck me as a better user experience. Combined with reservations I have about the Lemmy developers... Well, here we are. And seeing this level of involvement and dedication to doing the right thing from the developer confirms that choice. Kudos @ernest

[–] Rhaedas@kbin.social 10 points 1 year ago

I've been using both sides to figure things out, and I always end up using kbin more.

load more comments (1 replies)
[–] 0xtero@kbin.social 136 points 1 year ago (1 children)

Seems just like another day with open source software.
You gotta be careful about licensing and attribution and it can get really messy, but no big deal really.
Seems like you're correcting this and acting in good faith.

It shouldn't happen, but it happens. Thanks for the transparency

[–] Figaro@readit.buzz 20 points 1 year ago

Agreed, that's the key - act in good faith.

If you make a mistake, try to fix it in good faith. Seems like that's what is happening. 👍

[–] j3j5@hachyderm.io 109 points 1 year ago (2 children)

@ernest Hey man, if it's of any help, I have a PHP (laravel) project which mostly federates fine, license is AGPLv3 as well, so feel free to reuse what you see fit.

[–] ernest@kbin.social 52 points 1 year ago (1 children)

I will definitely check it out! Thanks

[–] j3j5@hachyderm.io 20 points 1 year ago

@ernest It's still wip so not all AP activities are supported yet, but it's powering some of my bots ( @BigBo_Energy @MeteoUY @LaDiaria )

[–] ernest@kbin.social 28 points 1 year ago

It makes a strong impression at first glance.

[–] lixus98@kbin.social 54 points 1 year ago

We appreciate the transparency and hope everything can be solved without much friction. Keep it up!

[–] developerjustin@mastodon.social 41 points 1 year ago

@ernest I thought you killed someone, based on the title 😂

I agree with the other commenter. Seems like you’re making it right. This is a new and sometimes messy frontier for a lot of people and processes. If someone is worried about protecting their IP, this isn’t the hill to die on.

[–] LollerCorleone@kbin.social 34 points 1 year ago (1 children)

I like you even more now for admitting your mistake without any hesitation and taking the steps to rectify your error. Keep up the good work!

load more comments (1 replies)
[–] knoland@kbin.social 31 points 1 year ago (1 children)

Cross-posting my comment:

This is one of my largest frustrations with the open source community. Everything is immediately assumed as malicious. There is no escalation, it's "you screwed me over" from the jump.

I suppose it's bred from decades of large corporations pilfering open source for profit. However, this post could easily have been, "I noticed there's some code I wrote that wasn't attributed, would you mind adding that?". Escalate from there if the appropriate actions aren't taken.

[–] neonfire@kbin.social 15 points 1 year ago (3 children)

For real, the person's name is LitigousEmma. This is one step away from a copyright troll, which imo seems to the the mortal enemy of the idea of FOSS. Did this Emma recognize all the developers of the programming languages they used, or the people who made the computer they worked on, or the pioneers of electronics in general? It's not like Emma took quarks and atoms and turned it into an web aggregator.

[–] knoland@kbin.social 21 points 1 year ago (6 children)

In LitigousEmma's defense, kbin did not comply with the license terms of the open source software, so there is a valid concern here. Unlike most programming languages which are often licensed under licenses which do not requite attribution.

However, mistakes happen. The open source community is better off if we could all just start from 0 and escalate based on response.

[–] gus@kbin.social 15 points 1 year ago (3 children)

Honestly that's my only issue with this. Ernest was totally rightfully called out for this, as he should have been. But Emma's knee jerk reaction is just a real bad look. Don't make any attempt to reach out and figure out why it's in there. Immediately make a public post accusing him of stealing code, trying to hide that he stole it, and claim it as his own...on a FOSS project no less...

Surely there's a step or 2 before that point..

[–] knoland@kbin.social 7 points 1 year ago (1 children)

I don't have any issue with opening an issue in the repo, that part seems reasonable. It, by definition, is an issue with the codebase.

[–] gus@kbin.social 14 points 1 year ago* (last edited 1 year ago) (2 children)

Right, I wasn't saying it shouldn't have been a public post. Just that the public post shouldn't have immediately jumped to accusations. FOSS or not, accusing someone of stealing code and intentionally trying to obfuscate its origin to pass it off as their own is a big deal for a developer. One that can destroy your reputation

A simple "I've noticed snippets in here of my work that falls under a license which is not attributed at all. Could you add the proper attributions or remove it from your project?" says the same thing and doesn't jump to any accusations that you have no idea if are true or not

[–] Rhaedas@kbin.social 6 points 1 year ago (1 children)

Not knowing either parties at all, I'd say the best solution is to assume both meant the best and some mistakes were made. One for forgetting to give credit for code, the other for wording in their asking to fix the mistake. At the end of the day, credit is given and the code grows, both benefit. Don't dwell on the small stuff that got there, problem is solved.

[–] gus@kbin.social 7 points 1 year ago

Agreed! Totally think this is a learning experience for both sides

An...earnest mistake?

I'm sorry

load more comments (1 replies)
load more comments (2 replies)
load more comments (5 replies)
load more comments (2 replies)
[–] KbinItTogether@kbin.social 28 points 1 year ago

Frankly, it's very refreshing to see someone running the show that has this combination of work ethic, passion without hunger for power, and honesty. Thank you for the transparency!

You've obviously got a million things going on a minute here. Like someone juggling flaming swords, I don't think anyone is going to blame you for dropping one accidentally while more fire-soaked swords keep being tossed at you. Seems like you know what to do and that there are a lot of talented folks here willing to provide help anyway they can. We're with you (me in the sentimental sense, I'm not so talented when it comes to coding)!

[–] Otome-chan@kbin.social 28 points 1 year ago

The title here scared me so much haha. It just seems like there's a credit issue? I don't think you've done anything wrong. Small projects naturally are like that, and kbin kinda exploded in size quite fast, so it's understandable. Transparency is good. There's no rush I think. Honestly this post just makes me realize even more how awesome kbin is and how great of a dev and admin you are. It's rare to see. Massive kudos.

[–] azura@kbin.social 25 points 1 year ago (1 children)

It's alright. I do think the actual issue was worded perhaps a bit harshly and combative, and I think you responded correctly. Very much appreciate the accountability here. To be honest if anything, this probably gives me more faith in you in the long run. There are many ways you could have dealt with it, but as far as I can see you've dealt with the issue as honorably as you could have.
Proper attribution can be tricky. We all learn. We all make mistakes. A lot of us will never release a project that makes it as far as yours has so even our issues don't become even nearly as visible.
Keep your head up and stay calm. You're doing great. We got you.

[–] JonEFive@kbin.social 7 points 1 year ago (1 children)

There are many ways you could have dealt with it, but as far as I can see you've dealt with the issue as honorably as you could have

It's certainly a far cry away from "We will remain profit driven until profits arrive" that a certain someone said in response to a legitimate question over on the other site. A breath of fresh air really.

load more comments (1 replies)
[–] Zak8022@kbin.social 23 points 1 year ago (1 children)

Seems that so long as the attribution is in place the Postmill people aren't going to push it further. I (and I hope the community) appreciate your transparency and honesty. That's the sort of thing that makes me want to stick around here and support this project.

And for fun, I will check out those other sites, since I hadn't heard about Postmill/Raddle before.

load more comments (1 replies)
[–] ReCursing@kbin.social 22 points 1 year ago

Everyone makes mistakes. Your response was not to deny or try to redirect blame, but to own up to it and fix the problem - and there is no lasting harm. Honestly if anyone asks for more than that they're being an arse! Keep doing what you're doing, I'm one of the trillions of Reddit refugees, and I like what I see here

As a thought, this project is clearly suddenly getting much bigger than you intended. Maybe see if you can take inspiration from Linux Torvalds about how to manage a project on this scale while retaining control of it - he is basically the benevolent dictator of the Linux kernel, what he says goes (and he has had some very famous arguments!), but he does delegate and take help where he needs it.

[–] RaleighEnt@kbin.social 21 points 1 year ago (3 children)

Damn emma really tore into you in that issue lol. A lot of assumptions about malicious intentions when a simple mistake seems much more likely. I mean I know they're in the right defending their work but damn idk if they needed to make such a big public stink about it lol

[–] ernest@kbin.social 18 points 1 year ago

It seems to me that she did it very gently ;)

[–] 0xtero@kbin.social 10 points 1 year ago* (last edited 1 year ago) (2 children)

Contacting the project "officially" through the the public tracker was the right thing to do.
As for the tone of the message - I don't think it was out of line considering the circumstances.

Mistakes do happen (licensing is actually hard) - and I'm happy to see it got fixed fast.

[–] 0x1C3B00DA@kbin.social 6 points 1 year ago

Mistakes do happen (licensing is actually hard)

Which is why the tone is striking people here as over the top. Ernest is clearly not a large business trying to profit off their work so some benefit of the doubt was warranted.

Ernest corrected it and the story is over so none of this matters, but open source devs going at other devs who make a mistake with attribution just makes the ecosystem a less nice place to be. Save that hostility for the ones trying to take advantage of others

load more comments (1 replies)
[–] mooklepticon@mstdn.social 6 points 1 year ago

@RaleighEnt @ernest Yeah, this part - "I have never given you permission to take my work uncredited and slap your licence on it--I wonder what your sponsors would have to say about that." - Seems unnecessarily harsh. It's not wrong, it's just a bit overboard. "Never attribute to malice that which can be attributed to ignorance." or however that quote goes. It's a simple oversight.

[–] LegendofDragoon@kbin.social 19 points 1 year ago

If there's anything I've learned from programmer humor reaching all it's that 95% of code is creatively liberated.

That being said I'm happy to hear you being transparent and giving the credit where it's due!

Keep up the good work man and try not to burn yourself out, I know this just be a stressful time!

[–] miroppb@kbin.social 18 points 1 year ago

Website is definitely running faster. Thank you @ernest

[–] DaisyLee@kbin.social 18 points 1 year ago

Licenses are hard. The fact that you are being transparent means this was not malice. Keep improving, and it all will work out in the end.

[–] anthoniix@kbin.social 18 points 1 year ago* (last edited 1 year ago) (1 children)

I honestly don't see this as a big deal, but I'm glad that you're being honest and open. Attribution is cool and all, but Emma makes it sound like you committed some sort of cardinal sin. I can never understand why someone who uses a permissive license gets so upset when their work is not attributed, you gain almost nothing from it.

Again though, attribution is still a net good. I think it's the polite thing to do, and I'm glad you're doing it.

[–] sab@kbin.social 6 points 1 year ago (2 children)

When you ask for very little (credit for your hard work), it's even more infuriating when you're deprived of it. You could compare it to stealing ideas in academia - the omission of one tiny reference makes a huge difference.

That said, there is such a thing as a honest mistake, and Ernest is handling it in the best way possible. But there are enough instances of permissive licences being abused that I don't blame the original author for initially taking it badly.

load more comments (2 replies)
[–] lh@kbin.social 17 points 1 year ago

Seems to me you're handling it the best way possible - yes, re-using open source code without proper attribution is an unfortunate mistake, but you've also clearly explained the reasons it happened. I also understand why the original code author reacted very strongly; when code is stolen maliciously and with intent, it's a huge "fuck you" to the original authors, who have freely released their code on the basis that they receive attribution of their use.

Good to see you've subsequently made up, and the code can stay. Thanks for being transparent, @ernest!

[–] strepto@kbin.social 13 points 1 year ago

Don't stress ernest. Mistakes happen

[–] FrostBolt@kbin.social 12 points 1 year ago

Thank you for the transparency

[–] InduperatorRex@kbin.social 12 points 1 year ago

This is exactly what we like to see, people actually taking responsibility for their mistakes and rectifying them in an open and transparent manner

[–] Saturdaycat@kbin.social 11 points 1 year ago

@ernest thank you for being transparent with us, it's what we can hope for when on platforms like this. I am happy to be here on kbin!

[–] VulcanSphere@kbin.social 10 points 1 year ago

We appreciate your honesty and transparency, keep up the good work!

[–] Timwi@kbin.social 10 points 1 year ago

You, sir, are an honorable person. I think I can speak for all open-source hobby programmers when I say: you make us proud.

[–] effingjoe@kbin.social 10 points 1 year ago* (last edited 1 year ago) (4 children)

Is 'LitigiousEmma' an inside joke, or an extremely relevant username? haha

Edit: For some reason this keeps bouncing around in my head and the more I think about the more I believe that Emma should have contacted you privately (at first, anyway) instead of jumping right into attempting to publicly shame you.

load more comments (4 replies)
[–] sickcodebruh@kbin.social 8 points 1 year ago

Mistakes happen, what matters is how you recover from them. Keep doing what you’re doing!

[–] roofuskit@kbin.social 8 points 1 year ago

Lol, she picked a hell of a username on codeberg. Very fitting.

"Hey Ernest, I see you have used my code from (project) without proper attribution as required by the license. Can you please correct the attribution or remove the infringing code?"

How hard would that have been? If she didn't get the response she wanted she could then escalate.

[–] Anon2971@kbin.social 8 points 1 year ago

That's ok dude. That's the nature of coding. We all copy and paste and take ideas from other places. Attributing is a low priority for minor personal projects and now suddenly your personal project is a bit bigger.

All good. No harm done. I look forward to seeing how this platform grows even more.

[–] Grimlo9ic@kbin.social 6 points 1 year ago* (last edited 1 year ago)

However I feel about the wording Emma chose, at the end of the day it was within her right to call you out. It's a great sign of good faith that you took the criticism, apologized, and are acting on it. From personal experience I also take stuff from the internet for personal projects... except my personal projects don't grow a thousandfold in terms of users almost overnight.

Don't sweat it, man. You're doing great.

load more comments
view more: next ›