There’s a tutorial for using Emacs - the key combination to enter the tutorial is on the welcome screen (I think it’s “CTRL-h t” but I don’t have it in front of me). It doesn’t cover elisp.

There are two elisp manuals available via the info system (CTRL-h i), a reference manual and an introductory text. They’re also available in other formats and are online as well. The reference manual is kept current with every release. I’m not sure about the introductory text, but the core of elisp hasn’t changed (I think) since lexical scoping was made the default several years ago.

Edit: added availability of manuals in non-info formats.

Exhibit #1 why Hexbear/Lemmygrad are unpopular: this guy

I believe you’ve answered your own question.

Lemmy isn’t Marxist-only. The majority of Lemmy users are what the more vocal Lemmygrad and Hexbear users deride as “libs.” As a thought experiment, imagine that you are one of us for a moment and then browse Local on one of those.

I’ve got a different Supermicro board. I’ve noticed that it’s extremely sensitive to SATA issues - if something isn’t just right it doesn’t boot or gets all kinds of wonky. A flaky cable is enough to cause issues.

I assume you’ve tried it with nothing but CPU, RAM, and video, but if not give it a shot.

I’ve never talked to an Arch user about Linux, so I dunno how toxic their community is. But I do read Arch documentation, and it’s fantastic. Arch’s documentation has (for me, anyway) taken the place that used to be held by the old HOWTOs back in the early days.

The kind of cooperation required to accomplish this doesn’t speak of a toxic community to me. I didn’t watch the video since I don’t watch YouTube on my phone, but I’m guessing it’s not the Arch community that has issues but annoying teenage “I’m more 1337 than you” jackwads that are the turd in the Linux punchbowl. Those little cretins are drawn to distros like Arch because they like feeling superior to the “normie” users.

I should know, I used to be like that thirty years ago. Most of us grow out of it after we start getting laid.

Emacs doesn’t follow the UNIX philosophy. It didn’t originate on UNIX - it was born in a mainframe environment. Instead of lots of independent specialized utilities it’s a Lisp engine with a text editor as its default program.

That said, there’s nothing to be afraid of. It’s not like vi will stop working. Just install it and run the tutorial, play around with customize, learn how to make an init file and install which-key, read some blogs (Mastering Emacs is a good one), browse the info pages, and use it.

Oh, I’ve got no complaints about the article or even its title. Few people learn Perl or Raku these days so it would be surprising for most people.

I thought it was interesting myself - Perl’s my go-to scripting language but I never used Raku. I might consider it next time I have a non-trivial scripting project.

I’m not sure why that’s surprising. Raku started out as Perl 6. Perl was designed primarily for use in a shell environment. Convenience features like the arguments to MAIN bit are in line with Perl philosophy.

Some of these issues are ones that were experienced and solved by the big IRC networks. They used different methods - nick registration and authentication via a bot, for instance.

The source for many of those is available. Why not see how others solved the problems? A brief look at the Charybdis IRCd source (at least the Freenode version) shows capabilities for limiting channel creation to authenticated users and what looks like built-in ChanServ and NickServ.

In any event, you may be worrying over nothing. I ran a friends-only IRC server back in the day and didn’t have issues with impersonation. I rarely saw any unknown users and it was easy to detect them because they weren’t part of my circle of friends. We had a couple bots that logged the channel and provided various services - it wouldn’t be hard to have one enforce security.