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.

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

Not a direct answer... But why not roll a LetsEncrypt cert? That'll be accepted by Readrops by default

Nobody trains on a GUI desktop though. Training is done on a cluster. And the kind of models that can be run on a consumer grade GPU... Nvidia doesn't care about. They're focused on selling 50k a pop cards to AI companies not fixing the Linux desktop for $600 card users.

It's pretty clear that Linux users should buy AMD or Intel GPUs if you want to support even a semi open source world

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)

The official lemmy community is over at https://slrpnk.net/c/nolawns, spawned by the same mod who ran NoLawns btw

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

I always recommend opensuse for ex-windows admins because it's stable, long term version (don't need to move to a rolling model that tends to confuse people), but most importantly YaST. It's a big ol do everything GUI for managing the system

That's my issue. Loads of very niche subreddits that are the opposite of technical (gardening and plants and stuff). So the users will never switch... It took 5+ years to build those communities up in the first place.

But I popped back in to check today, and they're all back open and the users are terrible, just ranting against the blackout and licking reddits boot like crazy. So it makes me sad to lose those communities and all that information, but if thats the quality of the userbase... I can't bring myself to go back.

You'd think there'd be overlap between organic gardening, or NoLawns, or homesteading that would click with the federated, less capitalistic Lemmy... But nope.

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

I think they're saying that they like using the local view as a /r/all type replacement (a view of the highest voted content across all communities). But they'd like to be able to selectively add an entire other instance to their local view.

The only way to do this today is to subscribe to every community on your main instance and every community on the other instance, and use Subscribed as a mega view... But then that ruins the Subscribed view as a selected subset.

To put it another way, I want to view all the best content across N many instances at once, so I can discover new communities.

What's really the difference between a federated Lemmy instance for hosting vs a 3rd party anyways?

If another Lemmy instance goes down, all the content on it is gone anyways. Federated != Mirrored. Just because you can browse the content doesn't mean it's safe from going away at the whims of one person