• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • 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



  • 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



  • 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


  • It’s not that they’re for this specifically… It’s that they are self centered. They’re the same 75% of the population that is willing to cross the picket line at Starbucks cuz they want their coffee. They don’t think about the workers rights, they only care about coffee.

    The same people just want memes and football and porn. They don’t care about what’s behind the scenes unless it directly impacts them. And let’s be honest, the reddit changes (for now) impact like 10% of reddits user base. That’s not enough for them to give up some dumb memes for


  • It’s just amazing really. Had they rolled out a reasonable rated plan, and maybe even a discount to highly known apps, and even set a “the price will go up each 6 months for the next 2 years till we reach this higher, but still reasonable price”… All the apps would have added a subscription model for like $0.99 a month and none of us would have really complained.

    Like, honestly most of us would have paid and maybe grumbled slightly but said “that’s the cost of maintaining this huge community, and I get more than $0.99 in value from it” and just kept shit posting on Reddit all day.

    If they wanted to block AI models, limit the API keys to only well known apps or those that are manually verified to be not-an-AI by reddit admins.

    It’s amazing how dumb a corporation can be sometimes (or has some nefarious endgame ala Twitter)


  • Not exactly the same but similar… There’s 4 major providers who service my area, but only one of them extends down my block. So I can choose from DSL (which to be fair goes up to like 35 Mbps), but if I want higher, I’m vendor locked to Xfinity, who charges at least 2x the price of the local companies.

    Ive asked several times, but they quote hundreds of thousands of dollars to trench fiber down my street, and it’s just not worth it.

    Except, you know, there’s already fiber from Xfinity… They just wont share.

    The physical cabling needs to be government owned and rented out to the companies, not exclusively owned by one single company. We’ll never have competitive pricing unless it’s nationalized infrastructure




  • Second the bokashi method. As a composter in Minnesota, we stay pretty cold for quite a long time. I swapped to bokashi in my basement and ferment a ton over the winter. Once its finished, I dump it into a large container outside to freeze for the winter, and in the spring either direct bury into my garden beds that like a huge dose of fertilization, or put it into my hot pile to jumpstart for the spring (it heats up a pile sooooo fast).

    I personally don’t feed bokashi to my worms because

    • it stinks (normally its sealed in an air-tight bucket so you can’t smell it… feeding it to worms exposes it)
    • the worms can’t eat that volume (bokashi can ferment anything, so everything goes in; meat, dairy, citrus, etc. Between my wife and I we ended the winter with over 30 gallons of very finely chopped material fermented… which was probably 100+ pounds in total)
    • the worms don’t like the acidity. Bokashi is anaerobic fermentation, which produces acidic compounds, and it takes ages to adjust your worms to that PH and going slightly too heavy on a feeding can cause a mass worm escape, since the acid will absorb and distribute throughout the soil (they can’t really escape by just balling in a corner)

  • Yeah, apparently I was wrong about this (still learning lemmy and fediverse stuff…). Text content of posts and comments are “synced” to your server and stored in your database there. Then future requests for that content are served from your instance. So its not as bad as I thought it was (the network load should be lower since you aren’t acting as entirely a proxy, more like a cache), but database bloat will be a huge problem (its already a big problem in other federated things like mastodon and matrix, where every server ends up saving everything they want into their own database).

    I’m not sure what happens when the original server goes down, does the federated servers discard that data? Or do we each maintain a forever copy until we want to get rid of it ourselves? There’s also some notes I’ve seen about how servers only incrementally cache federated content (only posts and comments that are viewed by someone are fetched, and new comments may not be fetched until someone wants to see it)… so not everybody has a “pure and full” copy of posts necessarily.

    But overall I wonder how all the various sysadmins hosting these lemmy instances will deal with the expotential growth they’re going to see, or if smaller instances will start defederating to save on hardware costs (no reason for my tiny instance that only talks about blue shiny rocks to federate with lemmy.world and store all that content)


  • Yes. If you run the server, then you are the source of truth of that community. All other servers that federate your community query your server to access the community and show it to their users.

    So if you run a server and a community explodes there, you might only have 500 users on your instance, but you might have 50k users reading that community and interacting with it from other Lemmy instances, thus your server needs to scale to 50k users worth.

    And ever more essential, your server is the source of truth of that community. So if your server is hacked or corrupted or deleted, that community is gone. Other instances don’t mirror it (except for temporary caching), so the Lemmy network essentially is a trust network of other people maintaining servers long term (and each inventing a monetary system to pay for it). I still think the network might be better than a centralized system like reddit, but it definitely has a lot of growing and policies that need to be sorted out very soon


  • The downside to individual servers, and micro-communities, is the cost and maintenance of lemmy instance. Its more scalable, reliable and cheaper to have a bunch of relatively low-churn communities exist on one bigger instance.

    The upside is that the rust community gets to own its own data. If programming.dev decides to shut down tomorrow, and posts and comments made there are gone. Lemmy doesn’t mirror or cache… all that data lives solely on the server ran by somebody.

    I’d vote lemmyrs at least for now until a governance and stability model is figured out to ensure these conversations don’t go into /dev/null like /r/rust (sort of) did.

    If say the Linux Foundation or a similarly large open source foundation (Apache, FSF, OSI, etc) decided to host a larger “open source” server, I’d consider moving there to improve discoverability and lessen the burden on the rust community itself


  • A much better use of resources, but you shard the data amongst potentially untrusted hosts (ie, anybody can stand up a lemmy instance and start hosting posts/comments, and then get sick of hosting it and delete their instance and all the uploaded data).

    Federation only allows access to the network of servers, it doesn’t protect the data at all, which means at any moment an entire community of useful historical information could just be wiped away (especially since there’s currently no monetary incentive to continue hosting, its only being done out of desire to be part of the network).

    I guess I’d rather see the blockchain (or simpler caching/mirroring) approach, something like the torrent network, so that no single person has access to delete content. We can all choose to not view or not mirror content we don’t agree with, but nobody can single-handedly own or modify the data


  • That has the same problem as any federated service like Lemmy… all that content only exists at the whims of whomever is willing to run the server and foot that bill. If they decide to delete their server, or just screw up and it dies… all that is gone.

    We’re basically relying on thousands of individuals to be good quality sysadmins and infosec engineers, all for free.

    I guess we could move to a mirroring/caching concept so that no single node contains the only copy of loads of data, but then we’re duplicating huge quantities of data.

    Like even today with Lemmy, there’s now thousands of instances stood up and I bet 2/3 of those will be dead within 6 months. So all those posts and comments that get made on those nodes will just go poof… which might be fine for a chat system, but for forums and microblogging (mastodon) that seems terrible