Every community I care about is dead
You’re right, and I suppose I was half-thinking along the lines of “we have all the pieces to solve this, but we don’t because we’re frozen in place by greed” instead of “this is something we could do with infrastructure today”. If everyone could collectively let go and re-distribute wealth and materials efficiently everyone would be much better off for it, but instead we’re stuck in some game theory hell where the optimal personal choice results in one of the worst outcomes.
The existence of poverty/hunger/homelessness in a post-scarcity world. if we wanted to eliminate those problems we could, but humans are blocked on how it can be done without hurting their own wealth.
The real problem is that everyone is using the “All” tab as a content feed. Ideally everyone would subscribe to communities and then they wouldn’t have to worry about seeing things they don’t want to see. Lemmy needs to be bigger before we can break that anti-pattern.
These will probably need to grow naturally again. We have enough techy users to carry tech-related discussions, but we probably don’t have enough users to carry niche communities yet. By gaining more users of any kind, techy or otherwise, we have better odds of gaining people with a secondary interest in those niche communities. It’ll take some time, but the Fediverse is much more permanent, and investments here will pay off theoretically forever. Even if another open platform supersedes Lemmy, it will be easy to port our community over to it.
Not very surprising to lose users after the big intake from June. If that were the only intake we’d ever get I would be worried but we all know that Reddit will continue to do user-hostile things. Lemmy now exists as a permanent lifeboat for those who get fed up with Reddit over time, and the next time something big happens we’ll be better prepared.
I didn’t mean my post to be read as trying to convince someone to use Linux, but as someone trying to convince themselves to use Linux. It’s fairly common that people want to switch but have convinced themselves that unless they have their exact same workflow from Windows they won’t be able to.
I’ve seen a trend where people move the goalposts on the reasons they’re not able to switch. “If only this program worked I could switch”, but when that program is ported it’ll be a new excuse next. Sooner or later you’ll have to draw a line and say “99% of my stuff works, the 1% that doesn’t can get bent”.
Yeah I wouldn’t bother. It intends for you to have a duplicate copy on every device, which is probably not what you want. Syncthing is really good for things like synchronizing notes, calendars, password databases, music, etc to your devices. Things that you want to access in both places, but that are usually disconnected from each other from time to time.
I’ve been using Nala for a while now, and I highly recommend it. The way it displays all the info is a little bit opinionated but I got used to it. Note that I’d only recommend using nala fetch with ~2-3 extra servers - don’t add 15 servers because you’ll need to wait for each one every time you nala update.
As a Debian user I agree with Loius Rossmann’s sage advice.
Edit: (make sure you enable unattended security upgrades at least so you can pretend that you only update once every few months)
Conduit is also licensed under Apache 2.0, so it could also be taken closed source at any point in time. The reason this wouldn’t impact Conduit as much is that there’re other contributors, whilst Synapse and Dendrite are almost exclusively developed by Element.
Right. The current perspective is based on the idea that if Synapse/Dendrite go closed-source right now, an open source version would be good as dead. Element is responsible for 95% of Synapse/Dendrite and I’m sure a community fork would have to play a lot of catch-up to figure out how to keep it going. If the community was more involved in Synapse/Dendrite implementation (and if Element let them) there would be less cause for alarm, as closing the source would just mean an immediate community fork and putting Element on ignore. Also to reiterate, The Matrix Foundation is not going along with Element on this move, and even if Element pulled something shady the Matrix Core Spec etc. would still remain open and under the Foundation’s control, so the max we have to lose is Synapse/Dendrite and all of Element’s developers.
As for the rest I agree and I do actually trust that Element is simply playing their only card here. These maneuvers are all required in order for Element to survive as a company at all, but they also unfortunately leave this backdoor open as a consequence. Matthew has pinky-promised over and over that they are only acting in good faith and that they would never use the backdoor, but it’s understandable that the presence of the backdoor is putting everyone at unease. Best case scenario we take this as a warning sign that if Element drops dead tomorrow then Matrix is also dead. If people want Matrix to not be practically owned by Element then we should diversify and prepare escape plans.
It depends on what your workflow/usecase for putting documents on the drive currently is. Syncthing is usually intended to be put on two separate devices, and then a folder on each device gets synchronized - meaning you have a folder of your documents on each device. Is there any reason not to just mount the network drive’s folder and drag the documents in that way?
This is actually quite a controversial change mainly because of their switch to a CLA. This indirectly gives them the opportunity to switch the license to closed source whenever they feel like it in the future. Semi-controversially, they are also primarly making this AGPL change in order to begin selling dual-licensing to companies. The Matrix Foundation itself does not support this change from Element, though Element is within its rights to do so.
You can read some more thoughts on this from the pessimistic folks at HackerNews. My main takeaway is that I don’t trust Element because I don’t trust anyone. I’m sure they’re doing this in good faith but I don’t like the power they have at the moment. I hope this is what’s needed to begin focusing efforts on alternative homeserver implementations like Conduit.
Syncthing - No introduction needed. Couldn’t live without it.
Healthchecks.io (you can self host this) - Dead man’s switch monitoring for all my automation. Most of my automated scripts hit up a Healthchecks endpoint when they run, and if they fail to hit the endpoint on a regular schedule I get notified. Mandatory for my anxiety.
Architects vs developers.
I switch around a bit. New is nice because there’s a deterministic order, but you also won’t have any comments to read. Every once in a while I scroll through active to see which posts have gotten discussion.
I prefer recertified ones if they’re significantly cheaper, but that’s up to you. Recertified will likely fail faster but when they’re close to ~60% of the cost it makes sense to gamble.
As for which RAID that is up to you and how you’re setting up your array. If you’re running ZFS then mirrored pairs are somewhat flexible since you can add a pair whenever you want of any size disks, but they will cost you 50% of your disk space in redundancy. For RAID5/6 you want the disk sizes to match and for ZFS you won’t be able to add any disks to a RAID5/6 array for about a year - the code that adds that feature is coming in the next release which will take about a year.
I’m not sure what’s around for Germany, sorry. You may be able to use eBay to find local sellers cross-posting from their normal website?
It was probably me. I use these two places + eBay primarily but I’m sure there are other good ones out there.
Edit: also for posterity this is a cool site but shucking drives hasn’t been viable for a long time as far as I’ve seen: https://shucks.top/
I wrote a short guide on this method recently: https://lemmy.ml/comment/6708735