That makes more sense. Thanks.
h3ndrik
joined 1 year ago
I think it's a bit of a chicken and egg problem if the revenue depends on the product. Lemmy needs to be shiny, grow and be attractive to attract more money. And they need more money to do it. Currently the userbase is stagnant at a bit less than 50k active users. I'm not sure if the community will jump in and provide the required amount of money if the situation stays as is.
Thanks. So the number on join-lemmy.org already includes the NLnet fund? I suppose that means you get ~600€ a month from the other (independent) supporters?
I'm confused. Liberapay 1.679$ + Patreon 1.165€ + OpenCollective 935$ + Crypo
adds up to the ~3.600€ but in which category are the NLnet bank transfers?
Kinda depends on productivity. I'd say 45k to 60k€ is alright for an average coding job in some company. I don't know the details here. For self-employed people that varies a lot and developing Lemmy propapbly doesn't compare to a salaried job at all.
Since I'm dabbling in AI at the moment: What about llama.cpp? Dude handles like 50 pull requests a week, coordinates everything and codes himself. And it's really complicated stuff and not the only project. And I mean there is lots of Linux software I use, (web-development) frameworks, smarthome stuff and electronics projects that I participate in and I'm always fascinated by their pace and how they manage to do that in addition to a day-job?! And they regularly push new features... I've had contact with some, filed bugreports and sometimes the next day they solved my issues and pushed a new version.
With Lemmy, my UI bugreports from a year ago are still open and not fixed. And it feels like contributions and bugreports are more a burden to the devs here and not that welcome like I'm used to from other projects. And yeah, I'm glad the last release was a bit bigger. But I mean it took 5 months... And moderation tools are traditionally an issue here. I'm glad something gets implemented. But we're still far from where we need to be. Same with the image handling and proxying.
I'm not sure what to make of this. Sure, software development ain't easy. But every new release I check the changelog and usually it's just some minor bugfixes. And twice a year a bigger release like this month with new features, yet the last bigger user-facing feature I can remember was instance blocking in december. And this is more or less adding the ability to hide posts and change how voting is displayed, if you're just a user.
Edit: I appreciate the work, though. And I like the idea of the platform. It's just that I'd like it to grow and flourish. But to me it seems we're often taking baby steps. And in the meantime stuff breaks and admins complain they barely cope with everything with the tools they have.
I'm not sure about the numbers but it should be like 6,600€ a month?! join-lemmy.org shows 3,656€ per month from donations, plus ~750€ a week they said in their last AMA from the NLnet fund.
I'm not sure if I'd consider that low... Sure it's not much compared to the revenue of a commercial platform. But still, you can build something with like 2x40h weeks. (plus a community)
Maybe they already factored in the 3k from NLnet and it's just 3.6k in total, I don't really know. But they're always talking about two full-time developers plus one more they'd like to pay... So that makes me think it's probably 6.5k€. Maybe someone can fact-check it.
AFAIK the NLnet funding is still running and there were still some milestones to claim as I last asked them in some AMA. Should be paying them an additional 3.000€ a month?!
They really should be more transparent an link that stuff and their progress.
I suppose stack overflow is a really good use case for AI. Just make it stick to what it knows once you start implementing AI answers and not just funnelling user data the other direction.
Hope that gets open-sourced and made in to an complete out-of-the-box advertising platform. I've tried selfhosting ads and as of now there isn't much except for revive-adserver. Sure, and the big (closed) surveillance tech platforms everyone uses.
Though Lemmy has funding for full-time developers.
And it's not like other features get implemented in the meantime. Progress is really slow here, even compared to hobby projects.
Edit: Lol, thanks for downvoting.
Yes, you'd damage the car's electrical system. First of all it's not designed to feed in energy through that outlet. It's made to output energy.
And most importantly: 24V is way too much. 2 times the intended voltage would fry most electronics. Your stereo, the power steering, airbags, ... There is a good margin and car electronics are designed to be pretty robust, but you're pushing it.
I think they're still fine because what happens is your car battery absorbs that extra voltage. But it's really dangerous. On a sunny day you'll charge your car battery beyond the 14V or so the chemistry can handle. And at that point it'll degrade fast. The acid in there is going to start to boil, producing hydrogen, so in addition to a destroyed battery, you're in for a small explosion if you're very unlucky. And once the battery is gone it'll start frying the cars electronics because now there isn't anything keeping the voltage down.
Get a switch that exclusively connects either the car or the solar panel to the bluetti. One switch that switches between two things, not an On/Off switch. And make sure it's rated for the current.
Edit: Or a relais that toggles between both. It can switch if there's power on the 12V rail, and connect the bluetti to either or.
Yeah, you're not doing it right. On Github you have to click on "Insights". And alike Lemmy which is split into two parts, llama.cpp also has a backend called ggml that does the (tensor) maths. Combined, the git stats are as following for the last four weeks:
So they definitely touch a lot more code regularly. Whichever PRs you clicked on, they added 50 times as much new lines of code in the same timeframe. And coding things like that is maths heavy and you also need to read the scientific papers and implement the maths. And they did quite some maths themselves and contributed their quanitzation techniques and benchmarked and studied them in addition to the coding. I'm really impressed by the guy. And he seems nice and attracted quite some contributors with his excellent and fast software. Reviews and comments their ideas and integrates them fast. And now it's a flourishing project that leads in its field. And the project isn't even that old...
I get it. Software development isn't that easy. Especially the 'touching different parts of the code' is something I don't really like. I mean it is like it is. And having architectural patterns like this is fairly common (logic, database, UI) and you have like 2 models of the data, one for federation and then the internal representation. I'm not that familiar with the Rust frameworks and how cumbersome it is to deal with them. With the correct database abstraction toolkit and other frameworks it gets better and you can often tie the stuff together. Also helps with the bugs. If it's really bad, maybe the architecture isn't optimal. Or the chosen frameworks suck. Other than that it's the job of a programmer to tie those aspects together, deal with the complexity and combine it into a working product.
I'm not even sure if you can assure that Lemmy has no bugs... I mean unit tests, integration tests and reviews won't cut it with distributed or federated software, right? I mean you'd need to roll out a small cloud of instances and do end to end tests, check if everything federates and if there are performance regressions... I'm not sure where Lemmy is regarding this. I occasionally observe when something big happens like federation breaking.
Sure. And UI programming is also something that is not really fun to me. I'm also not sure why it hasn't more contributors. Maybe the atmosphere isn't that welcoming to new people. Or the userbase in total is just too small. I mean fediverse observer reports like 50k Lemmy users, and that's not that much people if we're talking about the subset of people who learned programming and have the spare time to contribute. Maybe it's too interlinked with the rest of the code or not documented enough. I'd say it's probably not that attractive to get involved because it's mainly small bugfixes that can be implemented without also getting involved with the rest of the project. And apart from drive-by pull requests, people usually have some bigger vision when they join a project.