I support #CoSocialCaTechOps for the CoSocial community.
I'm based in Vancouver. I like to cook and eat. DWeb, open source, and community building.
More: https://bmann.ca
My wishlist would be to be able to link Mastodon accounts to Lemmy accounts, so the Lemmy system "knows" it's the same person. Including being able to edit the posts that come in from Mastodon, which right now is the biggest issue.
This post as an example, I was framing it as a Masto post, and it's pretty terrible on Lemmy. I'd focus on optimizing favourite/boost/comment from Mastodon as that is I think going to work best - comments don't need first class titles, links, and feature images.
For OPs, wouldn't it be amazing if I could DM some links and images and stuff, and then login to Lemmy/kbin and have it appear as a draft, and then publish it natively with rich text tools on the Lemmy/kbin side.
Subscribing via Mastodon works much better for me, even if I then go over and interact with my Lemmy account. I want both OPs and comments, and it's easy enough to put in a list or otherwise manage notifications from my clients. Micro-blog native vs Thread native people are going to differ in their opinions here :)
It's literally a quick test with me filling out two, and @waglo@jasette.facil.services submitting one. Can you dump a link to a CSV or source into an issue there of the stuff you're gathering please -- I need examples to build out the schema, so I can actually display that rather than just the blog post stuff. Well, and the JSON file underneath that is meant to be used as an API.
It’s still new, but the Takahē server is now focused on homepage functionality.
I wrote a whole article with screenshots of how Mastodon and Lemmy interop.
Hey @wakest@lemmy.ml thanks for sharing. This was a quick weekend hack. Mostly need some feedback and discussion on good ways of presenting the info and and what info to gather.
There are a number of licenses that do this. And yes, many of them are not OSI approved and people will say mean things about not using the word open source. Which you should ignore and instead perhaps say fair source instead if you care.
A couple to look at:
Big Time License
Prosperity License
I also recommend going through the back log of posts by Kyle Mitchell, an engineer - lawyer who has authored a number of great software licenses, including the two I listed.