LPT: ChatGPT is incredible for generating and evaluating regex
This was a fun one to go in blind on! I really enjoyed this first episode, though I'm still not sold on the series. This episode just gave me really strong "one-shot" vibes, y'know? They've sort of already resolved the initial conflict and tied up all the loose threads to the point where I'm not really sure what's left to explore.
Well, whatever. I'll stick around for another episode because the author & production team clearly have chops. It'll be interesting to see if they keep the same lightly manic tone of the pilot or if they veer off into more grounded post-apocalyptic storytelling. I'd prefer the former, though I do think that would be the harder path to tread here!
At first I was surprised by how much visibly older Rudeus looked, but I think that's just because I'd forgotten how much Rudeus aged in the final episodes of the prior season. Looking back and comparing them makes me realize how much subtler the change is than I first imagined: S1/C2 poster vs. Now.
Commentary:
- Is it just me, or is that "cinematic" postprocessing effect more intense now? It feels "shakier" than S1 and I was kind of hoping that they would only use it during sidestory episodes...
- This shot is giving me serious deja vu. This has to be a callback to a prior OP/ED, right?
- Oof. Been there, buddy. Time for depression arc
- Oof! Mega depression arc incoming...
- What's up with the cliche of making panic attacks sound like a flash bang? So weird, but at least Rudeus gets over it quickly through the power of, uh... I hope that's not hair, but it's probably hair.
- How all healthy relationships begin. Calling this a "red" flag would be a little too on the nose, huh?
- I totally got baader-meinholf'd when the subleader called their battle plan a "dandoori". Translator's note: dandoori means "plan" 😄 -- well, according to the Pikmin 4 translation team it's "[...] the art of organizing your tasks strategically and working with maximum efficiency to execute your plans quickly". Good word imo
- Sad Rudeus is kind of a buzzkill, isn't he?
- Yay battle cured his depression and now it's impact frame time!
- Wouldn't be an isekai without one of these scenes. I give it 2 more episodes before they're beloved and cheered upon... or not! I suppose bribery makes for an efficient shortcut.
- omg... it's worse than I imagined. Why can't you just be normal, Rudeus?
- Oh, right... yeah kind of forgot that he's super depressed.
- I know I was against the hair thing, but somehow this now feels like a step backward. Can we go back to the hair thing, please?
Just wait until 2024 and it won't be deprecated anymore
@virtualras@lemmy.world Hey, uh, can we talk at some point?
I think it's important that we make sure the Holo fork can be merged back upstream to simplify future maintenance and make things like docker configs easier. I currently have a PR open on this, so I was hoping we could reconcile our two efforts together as part of that.
I've also had AWS lambda stuff stood up for this and waiting for a couple days now. It's optimized down to ~$0.30 a month for hosting so I'm happy to take on that part of the endeavor or just transfer the virtual cloud config to you if that works better?
I'm specifically thinking of starting a community exclusively for episode discussions. That way it's easier to moderate and won't directly compete with the other existing communities.
Who knows? It might even be possible to set up some sort of web-ring where we promote discussion threads by cross-posting them on partner communities and in return we direct discussion users back to partner communities for non-episode stuff. That feels very Fediverse, doesn't it?
Go figure, guess I heard people talking about the restriction on admins and heard "moderator". Thanks for keeping me honest.
I actually tested appointing a moderator from an outside instance once in the past, but only via the user page, so I never had a chance to find out that the "Appoint Moderator" UI is actually tucked away inside the comment expandos.
Well, I've already tried asking the guy that runs !anime@lemmy.world, but he turned me down.
According to lemmyverse, that's the only other major English language general anime community, hence my invitation to that other guy to run away with me and build a new community together.
We technically don't even need moderator rights to send bot posts to a community, though common sense dictates that you should generally try to get permission before spamming someone else's community with auto-posts. It seems ass-backward to me to try and take over someone's community without permission in order to feel better about sending bot posts without permission.
In any case, I don't believe that the Lemmy developers are overtly interested in managing community ownership drama when they can just tell people to go create a new community where they're in charge. It's a bad precedent and bad optics for them to get involved -- I would feel wrong for even broaching the question to them. Apparently they totally do requests, but most of the requests that get granted seem to require the moderators to be absent for 1yr+. There's also the minor wrinkle that communities can only be moderated by users on the same instance and new registrations for lemmy.ml are currently closed indefinitely.
Oh hey, me too! I've also been waiting for a response from the mods for about a week now.
I think the mods here are on a (permanent?) vacation. Wanna combine our work and start a new episode discussion community?
Hence, "Zot":
Zot's identity layer is unique. It provides invisible single sign-on across all sites in the grid.
It also provides nomadic identity, so that your communications with friends, family, and or anyone else you're communicating with won't be affected by the loss of your primary communication node - either temporarily or permanently.
The important bits of your identity and relationships can be backed up to a thumb drive, or your laptop, and may appear at any node in the grid at any time - with all your friends and preferences intact.
Crucially, these nomadic instances are kept in sync so any instance can take over if another one is compromised or damaged. This protects you against not only major system failure, but also temporary site overloads and governmental manipulation or censorship.
Nomadic identity, single sign-on, and Hubzilla's decentralisation of hubs, we believe, introduce a high degree of degree of resiliency and persistence in internet communications, that are sorely needed amidst global trends towards corporate centralization, as well as mass and indiscriminate government surveillance and censorship.
As you browse the grid, viewing channels and their unique content, you are seamlessly authenticated as you go, even across completely different server hubs. No passwords to enter. Nothing to type. You're just greeted by name on every new site you visit.
How does Zot do that? We call it magic-auth, because Hubzilla hides the details of the complexities that go into single sign-on logins, and nomadic identities, from the experience of browsing on the grid. This is one of the design goals of Hubzilla: to increase privacy, and freedom on the web, while reducing the complexity and tedium brought by the need to enter new passwords and login names for every different sight that someone might visit online. You login only once on your home hub (or any nomadic backup hub you have chosen). This allows you to access any authenticated services provided anywhere in the grid - such as shopping, blogs, forums, and access to private information. Your password isn't stored on a thousand different sites; it is stored on servers that you control or that you have chosen to trust.
You cannot be silenced. You cannot be removed from the grid unless you yourself choose to exit it.
I’ve never heard of a target temp for food safety for steak either tbh
Well... believe it or not there is a suggested internal temperature for cooking beef, even if it's not ground. The CDC recommends 145F (63C) and FSA recommends 70C (158F). It's certainly true that beef is one of the safer meats to eat at undercooked temperatures (at least in the U.S. & U.K.), but it's also true that you can achieve just about any level of doneness beyond blue while still following food safety guidelines.
As I've said elsewhere, I have difficulty maintaining a super-sterile kitchen, so I can't practically leave meat out at room temperature all day without risking food poisoning. I instead opt to expedite the process by microwaving at low power. Even if you view these guidelines as silly, there remains the practical application of being able to sear thicker cuts without leaving an overly raw center. When your total cook-time is <5 minutes, these things matter.
I use a meat thermometer to gauge when it's room temp, so I know how long it takes (spoiler: about a day).
I'm not great about food safety so keeping meat out that long is usually a recipe for food poisoning -- that's why I cheat by putting it in the microwave on 10% power for 3 rounds of 5 minutes. This usually gets the steak 90% of the way to room temp with minimal cooking (this obviously varies a lot by wattage and cut, that's why thermometers are useful!). After that, I wrap the steak in cling-wrap and let it rest on the counter for another hour (the wrap helps prevent evaporative cooling) which gets the steak the rest of the way to room temperature.
Depends on how you're cooking. It's all about that heat gradient!
Out on an open grill on medium heat for 20 minutes? Yeah, literally zero difference.
Pan fried on a cast-iron skillet that you've cranked up to ludicrous mode? That shit better be room temp if you want the inside to reach a safe temperature!
... and to those of you who cook steak but have never panfried: what are you doing? Get yourself some peanut oil, crank the heat to 11, and get cooking ASAP. Look up a guide because nailing the doneness will be hard, but I guarantee you that you'll become a better cook after a few attempts. It's a rite of passage, my fellow meatheads.
The Steam Deck is spec'ed with a UHS-1/SDHC slot, which means that you can't use SDUC-class cards and you won't get much benefit from using comparable cards with a UHS-II/UHS-III bus mark compared to one with a UHS-I mark, even if the other marks otherwise suggest better performance. You can basically ignore the A/V markings because they're not granular enough to help with comparing cards at this particular performance level (you should instead compare "Random Read"/"Random Write" performance benchmark scores).
Note that there remains a considerable amount of variance among similarly marked cards. For example, the Sandisk Extreme Pro (Bus: UHS-I, Speed: 3) can benchmark write speeds which are almost twice as fast as the Sandisk Extreme (Bus: UHS-I, Speed: 3).
tl;dr: The ideal card will have the following markings:
- Capacity Standard: SDXC (SDUC is not compatible)
- UHS Bus Speed: I (higher is fine, but not helpful)
- Speed Class: 3 (though you should really be comparing benchmark scores instead!)
doesn’t even have any good pacman wrappers since yaourt (that I’m aware of).
paru is cool
Killer stuff! Sorry for my contributing undue pressure on top of what was probably already a taxing procedure happening in the server room.
Out of curiousity: how do you feel about Lemmy performance so far? I'm actually a little bit surprised that we already managed to outstrip the prior configuration. I suppose that inter-instance ActivityPub traffic just punches really hard regardless of intra-instance activity?
It's all fun and games until Jerma985 shows up and tears apart your flip-flops, too. Tonedeaf posts like these are why he keeps getting away with it.
Are there any legal experts who could chime in to help me understand the why of this decision?
If these loans are held by the executive branch, why aren't they allowed to cancel their own loans? Is there really a federal law on the books against this?
I agree. SystemD is a great service daemon (or, sigh, unit daemon in the stupid parlance). I like unit file syntax and I like the ergonomics of systemctl. It's solid and I appreciate the feeling of consistency that systemd lends to the otherwise chaotic landscape of Linux distrobutions.
It's for this reason that I'm willing to forgive SystemD overstepping the boundaries of services somewhat. System init/mounting? Sure, that's a blurry line after all. Logging? Okay -- it does make sense to provide a single reliable solution if the alternative is dealing with dozens of different implementations. Network resolution & session management? Fine, I'll begrudgingly accept that it's convenient to be able to treat logins/networking as psuedo-services for the sake of dependencies.
If that's as far as the scope crept, SystemD and I would be cool, but the so-called "component" list just keeps on going. SystemD has no business being a boot manager, nor a credential manager, nor a user manager, nor a container manager, nor an NTP client. I understand why they can't deprecate most of this junk, but why can't they just at least make this cruft optional to install?
You can improve the reliability if you provide it test cases. You can now be the PM you wish you had for the robot that will eventually replace you.