It…seems like there may be some issues with the repo…

That’s a fair point. I’ve always assumed it was a form of rate-limiting, but you’re right, that’ll be part of their analytics at least

Oh, whoops! I didn’t notice its timestamp when I read it 😅

I don’t hate YAML, but it has the same issues languages like PHP and JS introduce…there are unexpected corner cases that only exist because the designer wanted the language to be “friendly”

https://www.bram.us/2022/01/11/yaml-the-norway-problem/

For what it’s worth, I have been a convert from naive to aware for a couple years now. I used to like to think naive == UTC, but when data comes from unverifiable sources, you can’t know that for certain…

Yes, testing infrastructure is being put in place and some low-hanging fruit bugs have already been squashed. This bodes well, but it’s still early days, and I imagine not a lot of GIL-less production deployments are out there yet - where the real showstoppers will potentially live.

I’m tenatively optimistic, but threading bugs are sometimes hard to catch

I’m curious to see how this whole thing shakes out. Like, will removing the GIL be an uphill battle that everyone regrets even suggesting?Will it be so easy, we wonder why we didn’t do it years ago? Or, most likely, somewhere in the middle?

If “build the server and client in the same language” is a hard requirement, I believe your only choice is JavaScript…

The tone of the post makes me think you’re newer to programming, so I’ll leave it at that, as extensions to this question can overwhelm quickly, but yeah, JavaScript is a fine language for what you’re doing

Not a Lemmy dev, and I invite them to correct me, but…

As a heads up, over the last couple of days, the server and client repos have been tagging beta releases, so the next Lemmy release might be just around the corner too!

Putting aside the “should/shouldn’t do” argument, I was also wondering if the code is even viable. I imagine that ‘ls’ and ‘sudo’ are probably pretty ubiquitous, but I bet there exist some Linux installs out there with a different shell than ‘bash’, and some might not have ‘grep’ too. That would lead to some pretty cryptic bugs for the end user, eh?

What a strange article. The reasoning for why 22 is interesting though very straightforward, and the rest of the article is essentially “I asked for port 22, and they gave it to me”. Little fanfare, little in way of storytelling conflict.

Not an issue in and of itself, but strange with a title of the form “This is the story of…” That sort of titling usually begets intrigue and triumph over adversity, dunnit?

This song and album were pretty formative in my metal journey. I remember that opening riff exploding out the gate, with its off-kilter bounce, and thinking I had never heard anything so cool and technical.

I totally respect this being potentially a big ask, but does anyone have a TL;DR of what caused or was the fix for the federation issue(s)? I don’t have capacity at this moment to look through Github Issues and PRs, but I’m curious

Gotta give a shoutout to the End of Year lists from Angry Metal Guy blog. They have a pretty good balance of popular and underground metal from a bunch of different writers with different genre preferences.

They introduced me to Warcrab and Xoth this year, at least.

A link for the lazy: https://www.angrymetalguy.com/one-list-to-debase-them-all-angrymetal-guy-coms-aggregated-top-20-of-2023/

I have a personal run of thumb. It’s got a thousand and one exceptions, but seems to work a good amount of the time, for what it’s worth.

Hard rock songs tend to have guitar-lite verses. As in, the verse seems to often feature just the bass and drums as instrumentation, or the guitar doing minimal legwork (read: a start-stop non-riff, or sometimes acoustic noodling), before exploding into existence for a powerful (pre-)chorus.

On the other hand, metal tends to be guitar-forward most of the time. The verse/chorus divide is usually heralded by switching riffs, or, in the case of symphonic and folk subgenres, the introduction of other instruments besides guitar.

Yeah, I’ve implemented OTP before, and I can think of no way this could be a surveillance move. If they required you use their app because they use a custom solution, sure, maybe, but they’re OTP is currently entirely standard, so you can use a plethora of app (or roll your own in about 14 lines of Python)

Dream Theater - Scenes from a Memory

Opeth - Ghost Reveries

Mastodon - Leviathan Bloodbath - The Fathomless Mastery

Cynic - Traced in Air

Symphony X - Paradise Lost

Psycroptic - The Inherited Repression

That which you fall in love as a teenager, innit?

All roads lead to woodworking

I think this belongs here.

I also love the idea of some sort of CI/CD pipeline with this in its linting stage

I kinda feel your pain. A project that I helped launch is written in Typescript technically, but the actual on-the-ground developers were averse to using type safety, so any is used everywhere. So, it becomes worst of both worlds, and the code is a mess (I don’t have authority in the project anymore, and wouldn’t touch it even if I could).

I’m also annoyed at some level because some of the devs are pretty junior, and I fear they are going to go forward thinking Typescript or type safety in general is bad, which hurts my type-safety-loving-soul