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

/kbin meta

5 readers
6 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 1 year 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.

you are viewing a single comment's thread
view the rest of the comments
[–] neonfire@kbin.social 0 points 1 year ago (2 children)

Copyright is the enemy of freedom and knowledge. What if Einstein copyrighted E=MC^2? Emma didn't create the software, they just figured out how to make it.

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

And instead of making it closed they made it available under open source licensing. With the only terms being attribution.

They’re not the bad guy here. Nor is Ernest. There’s no bad guys here just a mistake, a call to fix it, a fix and an acceptance of that fix.

Really Ernest showed the perfect example of “if you have to eat crow eat it while it’s young and tender”

[–] andromedusgalacticus@lemm.ee 1 points 1 year ago (1 children)

What an interesting phrase. I've never heard that one before. Perfectly sums up less elegant forms of phrasing it.

[–] airsay@kbin.social 1 points 1 year ago

We have a similar one in Nigeria. If you are going to eat a frog, eat a fat one that has eggs

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

He couldn't have copyrighted E=mc^2, he'd have had to patent it. But laws of nature are excluded from patent eligibiligy in the US, and presumably most other jurisdictions.

Software code is an interesting edge case in the middle. The code itself is a creative expression, and so copyright applies. This brings benefits as well as restrictions; software code is also speech as far as many free-speech rights are concerned. The algorithms expressed by the code are subject to software patents, which is a more controversial grey area.