I envy your life, as it feels like every year the browser assimilates and consumes more and more.
I envy your life, as it feels like every year the browser assimilates and consumes more and more.
You’re greatly overestimating how many people that is; additionally, it was largely people that aren’t very committed to FOSS that got mad. The project maintainers and most users are fine with it. People who are committed to FOSS ideals are overwhelmingly progressive to leftist. That’s why those codes of conduct were added in the first place, and were largely uncontroversial amongst most actual contributors of those projects.
Agree with the former, not the latter.
Use lemmy.ml how you want to use it, and if you want to participate in other political leanings, go to a different instance. No one is really stopping you, and that’s the whole idea of the fediverse. And there really isn’t any value lost, because this isn’t a “choose one and only one” situation. You’ve got all of the fediverse at your fingertips.
Until you make the mistake of replying with the wrong kind of comment to the wrong sub, and get banned from the entire instance and lose the ability to post on many of the largest subs on this side of the fediverse. Or maybe they just see you out and about and decide to ban you on sight because they don’t like what you said. There’s nothing stopping that.
Admin overreach and abuse is a major issue for the fediverse because it affects more than just the user in question. Admins of large instances get to decide who has access to the users and communities on their instances, and very often the users of the instance aren’t even aware of the actions taken on their behalf. Mastodon recently implemented a notification for when blocks and defederation remove your follows or followers, and this is a great first step. Users deserve to know when they are impacted by decisions such as these.
I love the fediverse and want to see it thrive, so we need to stop putting our heads in the sand on this issue. It’s always discussed as if it’s an issue with a few problematic instances rather than the systemic issue in need of a solution that is is. Admins need the tools to protect their instances from real abuse, but we need to balance that with the right of the users to know what’s going on and not be unfairly deprived of the social aspect of this social media experiment, especially without knowing.
No that’s true, open source is superior is proprietary
“Let’s remove the social element of our social movement”
Great so what’s left at that point, the free value FOSS provides to corporations?
Criticizing people’s past and current actions relating to the subject and bringing up their direct history relavent to the subject is not a personal attack, nor is it out of line to point out he does his to advance his political agenda within the project, which is why he got banned in the first place. All of this directly relates to the subject at hand.
You know what doesn’t relate to the subject at hand? Your random little “sjw gender terrorists” comment. But it does make it rather clear why you want to obfuscate the facts about Srid’s history with the project, subsequent ban, and continued amplification of drama and general shit-stirring ever since.
You made one reply to me whining that I attacked the person by pointing out his beliefs, and then made another reply to me about “gender terrorist SJWs”. Do you just lack any form of self-awareness?
I attacked his beliefs which is perfectly valid. You should critically examine the motives and biases of people who feed you information.
You should know that the guy you cited in the second link, Srid, is a well-known right-wing shit-stirrer who is banned from basically all NixOS spaces because he cannot peacefully coexist. He literally gets up day after day with the seemingly sole purpose of fueling drama and causing problems. Don’t take his opinion at face value, he wants to see the project burn down and this colors his interpretation of events.
NixOS is going through a rocky moment for sure, but there’s no indication it will implode currently.
Whatever you get for your NAS, make sure it’s CMR and not SMR. SMR drives do not perform well in NAS arrays.
I just want to follow this up and stress how important it is. This isn’t “oh, it kinda sucks but you can tolerate it” territory. It’s actually unusable after a certain point. I inherited a Synology NAS at my current job which is used for backup storage, and my job was to figure out why it wasn’t working anymore. After investigation, I found out the guy before me populated it with cheapo SMR drives, and after a certain point they just become literally unusable due to the ripple effect of rewrites inherent to shingled drives. I tried to format the array of five 6TB drives and start fresh, and it told me it would take 30 days to run whatever “optimization” process it performs after a format. After leaving it running for several days, I realized it wasn’t joking. During this period, I was getting around 1MB/s throughput to the system.
Do not buy SMR drives for any parity RAID usage, ever. It is fundamentally incompatible with how parity RAID (RAID5/6, ZFS RAID-Z, etc) writes across multiple disks. SMR should only be used for write-once situations, and ideally only for cold storage.
When people recognize they were wrong about something, as smugly satisfying as it may be it’s not actually helpful to tell them that they should have been correct sooner.
I think they’re just making fun of the bad font kerning in the app which causes a gap in the word Unmanaged
Refurbished drives get their SMART data reset during the process, they absolutely had more than that originally.
“Because I feel like it.”
So in other words, because she wants to? As in, “because it’s her body and she can do whatever she wants with it”?
I don’t know, that sounds like hard, thankless work that will take years of consistent effort, dealing with countless setbacks and losses but not giving up, before finally achieving our goals of making real and meaningful change. What if instead if that I just don’t buy Starbucks, will that work?
Plants aren’t sentient. When we say they “feel pain” and “communicate” we don’t mean like sentient creatures. We just don’t have better words to accurately convey the mechanics at play here. Computers also “communicate”.
The games will still be designed by humans. Generative AI will only be used as a tool in the workflow for creating certain assets faster, or for creating certain kinds of interactivity on the fly. It’s not good enough to wholesale create large sets of matching assets, and despite what folks may think, it won’t be for a long time, if ever. Not to mention, people just don’t want that. People want art to have intentional meaning, not computer generated slop.
This is no different than anything else, we naturally appreciate the skill it takes to create something entirely by hand, even if mass production is available.
Something you might want to look into is using mTLS, or client certificate authentication, on any external facing services that aren’t intended for anybody but yourself or close friends/family. Basically, it means nobody can even connect to your server without having a certificate that was pre-generated by you. On the server end, you just create the certificate, and on the client end, you install it to the device and select it when asked.
The viability of this depends on what applications you use, as support for it must be implemented by its developers. For anything only accessed via web browser, it’s perfect. All web browsers (except Firefox on mobile…) can handle mTLS certs. Lots of Android apps also support it. I use it for Nextcloud on Android (so Files, Tasks, Notes, Photos, RSS, and DAVx5 apps all work) and support works across the board there. It also works for Home Assistant and Gotify apps. It looks like Immich does indeed support it too. In my configuration, I only require it on external connections by having 443 on the router be forwarded to 444 on the server, so I can apply different settings easily without having to do any filtering.
As far as security and privacy goes, mTLS is virtually impenetrable so long as you protect the certificate and configure the proxy correctly, and similar in concept to using Wireguard. Nearly everything I publicly expose is protected via mTLS, with very rare exceptions like Navidrome due to lack of support in subsonic clients, and a couple other things that I actually want to be universally reachable.