veaviticus

I mean, the real answer is that most open source developers aren’t here for freedom at any cost. They’re here like a startup… Waiting to be acquired for big bucks. Open source doesn’t pay bills, and if a megacorp pulls up in a Brinks truck full of cash, I wouldn’t be surprised if 80% of open source projects sell

Are you looking for this to be passive income? Or a full time job? Clear cutting a half or full hectare and doing intensive market gardening can almost always turn a profit. But it’s a hard industry requiring lots of knowledge and tons of work/time (think 6 days a week for at least half the year).

You can utilize the rest of the forest as sustainable forestry, using the cut wood for wood chips for the farm, and interplanting critical native wildflowers to boost pollinators.

Plenty of space to do an apiary (bee keeping) for extra income selling the honey.

And on the side you can do mushrooms like the other commentor said. It can be a relatively low amount of work once you’ve mastered the technique.

And all of this can be a net benefit to the land. Losing a few trees can open up a forest to allow better long term growth, increase top soil over time (via organic no-till gardening) and support native pollinators via human-maintained wild spaces.

I get that, and I agree with it in general, but there’s literally no company on earth that would approach open source developers with the intent to pay them to work on a closed source product, or to buy out their open source work without having an NDA in place. Hell, even if Meta just wants to pay them to do open source work to support the community, there will still likely be an NDA covering what they can say to the public about the arrangement or anything they learn from having access to internal systems.

It’s like saying “Meta has security guards at the doors to their datacenters! They must be doing something illegal in there!”

Meta is evil and is very likely doing something bad with these developers, but the NDA isn’t the smoking gun evidence of evil… It’s Meta’s history in general

I don’t know why everyone is so upset about the NDA thing… It’s such a standard business practice. Whenever I (a mid tier infra engineer at a mid sized software company) needed to talk to a vendor, get a product demo/consultation, get support on a licensed application, etc… We either sent an NDA to that company or bad one on file already with them. Nobody discusses internal processes, policies or roadmaps with an outside contact without an NDA first. It’s literally just a standard business practice.

It could be nefarious, since it’s meta afterall, but I wouldn’t be shocked if there’s thousands of people/companies who have standing NDAs with meta just so they could come on campus and demo their product to some team

I’m guessing it’s based on the new Instagram twitter-alternative that’s rumored to be based on the mastodon code base. But I’ve also heard rumors about Instagram wanting to make it on a rust code base and have been investing internally into rust a lot more lately, so it wouldnt surprise me if they’ve been consulting Lemmy or other fediverse devs for their experience

It has a 1st party mobile app for Android and iOS right on the main download page (https://logseq.com/downloads).

I use the android app and it’s ok. Still has some work to do, but honestly trying to handle the complexity of logseq style editing in a mobile app is rough, so I mostly just use it for rough note taking that I clean up on desktop later

Oh I’m not saying what your doing over at programming.dev is wrong or insufficient… Honestly I don’t know what your doing to ensure the lemmy server exists long term (though its great to hear you’ve got some policies in place already).

I’m more thinking the rust community should evaluate options and vote, or some rust subgroup of the leadership should set criteria to ensure that another reddit-type event doesn’t happen again (the home of this community must be open-source, with data backups publicly available, with a governing body and a line of succession or something, etc).

If programming.dev meets those things today, I’d say sure lets move there. I think its better to have a lemmy instance for a concept (computer science) than a specific topic (rust), but that’s just me

I’ve replaced some “non replaceable” batteries in phones before… Only to find that after about 5 years of medium use the flash storage goes to shit (which causes massive slow downs), the chips begin to desolder themselves, the USB port gets janky and stops charging, etc.

Batteries are a great first step, but damn these $1000+ devices just are not built to last more than 3 years

It’s not the tech here. Postgres can scale both vertically and horizontally (yes there are others that can scale easier or in different factors of CAP).

The problem is how the data is being stored and accessed. Lemmy is doing some really inefficient data access and it’s causing bottlenecks under load.

Lemmy (unfortunately) just wasn’t ready for this level of primetime yet… It has a number of issues that are going to be quite tricky to fix now that it’s seen such wide adoption (database migrations are tricky on their own, doing so on a production site even harder, doing so on 8k+ independent production sites… Sounds like a nightmare)

Idk. I’m conflicted on this. While I agree… For bigger/broader topics, I can definitely see that the quality of discussion and the repetition of topic is already really bad for smaller/niche communities.

When the subreddit had maybe 2k subs worldwide, and now is comprised of 50 subs spread across 3 instances… It’s rough. That community is just dead and that sucks.

I guess I’d rather have one centralized community on one big (yet open source) instance where I know we can leave and move again, than have the community just for entirely