When I visited Scotland, I had a deep fried Mars Bar. It was okay.

Okay, but consider that the ultra-rich technofascists are a group that has had a disproportionate impact on the continued pillaging of the climate. They aren’t just opportunists wanting to make the most of the fragments of society that will remain after climate disaster, but people who have been working to bring that scenario into fruition because it’s profitable in the short term whilst positioning them to take even more power.

I cannot emphasise enough that they want this, and that this ideology goes further back than the current wave of them. The reality of climate change is unfathomably dire, but I hope you understand why it’s necessary to resist these people as part of whatever climate resilience we can build. I’ll probably be dead before shit really hits the fan, climate-wise, so my goal is to do whatever I can to support the people who come after me. If those techno-assholes are allowed to inherit the fragments of society, the entire planet is even more fucked

I find myself commenting far more often than I did on Reddit. I remember once that I lamented that Lemmy doesn’t have a “super upvote” in the way that Reddit gold used to be (which is a silly thought, given that I have never, and would never pay money to gild a comment). However, I realised that on this more discussion based platform, a short but meaningful comment can readily function as a super upvote. I think the lack of karma accrual for comments/posts also promotes this.

(tangent to your question because someone already answered) I think that courtroom stenographers (people who type up what’s said) use special chording keyboards. I’ve also been to a few events where there has been someone transcribing things in real time for accessibility purposes, and they also use a cool looking chording keyboard. It takes some learning, but the max typing speed is way faster than any conventional keyboard could manage — which is why skilled people use them for transcribing stuff

A brand that I’m aware of that does them is Charachorder.

Just adding onto the good answer you already got, but the thing that made this click to me was understanding that if you’re not port forwarding, you’re limited in the connections you can make to other peers. Specifically, you can only connect to peers who are fully available. Whereas if you’re port forwarding, then you can connect both to people who are limited, and to people who are fully available.

I imagine you would get faster download speeds if you were port forwarding, but my impression is that this mainly is a factor for seeding, which matters more if you’re on a private tracker that requires a certain download/upload ratio; it’s way harder to keep that ratio above 1.0 if you’re limited in the peers you can connect to.

I really like it. The composition of the elements is excellent, which is great for both clarity of reading, and also a sense of understated elegance.

I wonder if this might have been why they shared it. Sort of like “We’ve got an idea that we think is good, but it also clearly needs work”

I see your point, I hadn’t thought about it this way. I think what you’re suggesting is this:

           |                        |
           |          rest of LAN <-/

Reasonably difficult, I think. I’m basing my answer off of the vibes I get from open source firmware projects for routers, which are far more common. I haven’t heard of similar for printers, which suggests that there is less of a foundation to work on. I think Brother, in particular, was a brand that has typically been decent up until now.

I also get the sense that programming firmware is different enough to programming software that a software developer trying to contribute would find it really difficult(?. Someone correct me if I’m wrong — I’m not a software developer, but a scientist who writes code, so I’m speaking outside of my main expertise). But this loops back in with the lack of existing projects making it harder to get to grips with how to do stuff — part of why I like open source programs is because I can look through a project and try to understand what the code is doing.

I hadn’t noticed this until you pointed it out, but yeah, their logos are fire

I’m just an internet stranger, but I’m proud of your growth. Many people in similar positions would’ve spent those years digging themselves deeper, because confronting the cognitive dissonance is not easy (you may well have spent some of that time digging deeper, but you made it out, and I’m glad you’re here with us)

That’s a pretty facetious reply. Lemmy has tons of ways of curating your feeds and that’s one of its big strengths in my opinion.

This isn’t about seeing the occasional bit of NSFW material (which I still see occasionally on my Lemmy feed, despite having blocked a bunch of NSFW communities). This latest Instagram debacle involved people’s entire feeds being full of not just pornography, but also heavily NSFL gore stuff.

However, the real crux of this issue is clear when I imagine how I’d feel if a problem like this happened with Lemmy — I’d be unhappy, but I wouldn’t flee the platform, because I trust various admins to not bullshit me about what had happened and what was going to be done in future. Meta has burned through any goodwill it might’ve once had, and the only thing that’s transparent about them is their bullshit

Recently, I recommended to a friend that basic vim/vi is worth learning because it’s a baseline that you can always trust will be there across different Linux systems.

They asked me what I used most on my home system, and the answer was emacs, but I was very clear that I was not recommending it. It’s a particular kind of person who finds themselves at home in emacs, and for everyone besides those people, selling them on emacs would feel like persuading them to do hard drugs.

My gosh, these are incredible. Thank you for sharing them. I cried at Select Star; that is legitimate art.

When I realised I had ADHD, being able to recontextualise my struggles and set aside all the negative self talk allowed me to see that actually, there are parts of my ADHD-ness that I think are really cool. For example, I found it useful to have multiple tasks on my “menu” for a given day, so that I can cycle between them and not get burnt out on any one task. As well as being a strategy to cope with some of my ADHD deficits, it turns out that putting a tricky problem on a back-burner while I focus on something completely different is a great way to generate new ideas and connections about the original task.

Have you found anything like that so far? It took me a while to get to that point, but I think it’s part of the liberation of neurodiversity as a framework — it’s a way of acknowledging the quirks of our brains in a way that isn’t constrained to thinking of ADHD as a disorder.

“I’ve seen 5+ clones of Papers Please. I doubt that if you surveyed people describing the mechanics that they would be interested especially if Papers Please never came out.”

I think this is a great example. You can’t distill things down to a formula because these things exist in conversation with each other. An example that comes to mind is the game “Not Tonight”, a Brexit themed Papers Please clone. Mechanically, it does very little to distinguish itself from papers please, but narratively, that’s sort of the whole point: It being a clone specifically leverages the energy of “Glory to Arstotzka” to satirise the UK’s institutional racism.

Surveys don’t capture that games like this aren’t just clones of Papers Please, they’re actively in conversation with Papers Please

Lmao

The main reason I like vi/vim is that if you’re having to use multiple different computers (such as if one is a sysadmin, or in my case, does scientific computing), because if you’re running on Linux, you can be confident that vi/vim will be on it.

For personal use, I’ve been using emacs, but I can’t recommend that without feeling like I’m suggesting you try some heroin. I enjoy emacs because of it’s complexity and how much power it gives me to modify it. It’s very easy to fall into feature creep and over complexity though. That’s why I can’t recommend it — it’s good for me because I am a chronic tinkerer, and having something to fuck around with is an outlet for that.

I would recommend learning the basics of vim though. As you highlight, getting back to your current level of productivity would take a while, even if you loved vim and committed to it wholeheartedly. It is possible to try it out with little commitment though, for the perspective. If you’re on a machine that has vim installed already, try the vimtutor command, which will start the ~30 min long inbuilt tutorial for vim. I liked it for giving me perspective on what on earth vim even was.

I know you don’t use it anymore, but I just want to fistbump you re: sublime text. I really loved that as a basic text editor that was, for me, just a slightly nicer notepad.

I’m reminded of something I saw recently where a guy had a mini old screen for typing, but an e-ink main screen. It was a DIY cyberdeck, and weird enough that I don’t think it’s useful for you or OP, but I figured you’d find it interesting to hear that your suggestion seems to be on the right track

(n.b. I am neither a rust, nor C developer so I am writing outside my own direct experience)

One of the arguments brought up on the kernel.org thread was that if there were changes to the C side of the API, how would this avoid breaking all the rust bindings? The reply to this was that like with any big change in the Linux kernel that affects multiple systems with multiple different teams involved, that it would require a coordinated and collaborative approach — i.e. it’s not like the rust side of things would only start working on responding to a breaking change once that change has broken the rust bindings. This response (and many of the responses to it) seemed reasonable to me.

However, in order for that collaboration to work, there are going to have to be C developers speaking to rust developers, because the rust developers who need to repair the bindings will need to understand some of what’s being proposed, and thus they’ll need to understand some level of C, and vice versa. So in practice, it seems nigh on impossible for the long term, ongoing maintenance of this code to be entirely a task for the rust devs (but I think this is taking an abnormally flexible reading of “maintenance” — communicating with other people is just part and parcel of working on such a huge project, imo)

Some people have an ideological opposition to there being two different programming languages in the Linux kernel full stop. This is part of why the main thing that rust has been used for so far are drivers, which are fairly self enclosed. Christoph Hellwig even used the word “cancer” to describe a slow creep towards a codebase of two languages. I get the sense that in his view, this change that’s being proposed could be the beginning of the end if it leads to continued prevalence of rust in Linux.

I haven’t written enough production code to have much of an opinion, but my impression is that people who are concerned are valid (because I do have more than enough experience with messy, fragmented codebases), but that their opposition is too strong. A framework that comes to mind is how risk assessments (like are done for scientific research) outline risks that often cannot be fully eliminated but can be reduced and mitigated via discussing them in the context of a risk assessment. Using rust in Linux at all hasn’t been a decision taken lightly, and further use of it would need ongoing participation from multiple relevant parties, but that’s just the price of progress sometimes.