If you think there is nothing posted there, it is because it is all in French and bluesky is only showing you English posts. The linked account has 1.5k posts.
I'm not sure it makes much sense that gitea is a bit too heavy, but forgejo (a fork of gitea) runs perfectly. But forgejo appears to have more developments momentum as a project and so you probably landed on the right choice anyway. 🙂
Would be pretty good to also take a note from the Dems and have Trudeau step down for the next election.
As a Canadian, I'm over him. I'd never vote for PP, but I'd like to see some new options please.
I'm coming back to you from the future to tell you that she can. 😥
However, the Federal government has limited options when it comes to influencing the provincial health care programs. They can offer money with strings attached, and that's about it. Given the hostile atmosphere from some provinces... they may not have been able to offer dental care by working through this traditional means.
Home Assistant invested quite a bit into the technology to create a FOSS voice assistant over the past year. It still needs quite a bit of work, but the foundation is there; it supports wake words ("Hey ..."), speech-to-text to hear your command, interpretation and command processing, and text-to-speech to return results.
The downsides are that it's still quite technical to set up primarily due to the lack of commercially available hardware, and the command library is fairly small at this point.
With some of this foundational work out of the way, I expect Home Assistant to move forward quickly to improve, and other projects can work off the same pieces if they desire to as well.
Here's their year-end post about it: https://www.home-assistant.io/blog/2023/12/13/year-of-the-voice-chapter-5/
I like it, but, there are upsides and downsides.
I usually play with a team that has some remote members, so Foundry is the mechanism by which I create shared visuals and battlemaps. I don't go as far as to run the whole game with Foundry -- PCs have their character sheets, they make their rolls themselves, and I still track most elements of the game myself (except initiative-order and NPC/monster HP).
Even with just this light usage, there are downsides -- for example, my prep as a DM takes longer because I have to create or adapt a map/visual for everything, as opposed to just describing it. I'm preparing an adventure right now that I might be done with if I didn't use Foundry; it's all documented, but not visualized.
Many (for example, the linked article) add more capabilities to Foundry until it runs and automates more and more of the game. I think I'm concerned about creating a slippery slope with that, to the point where we're playing a multiplayer video game rather than an TTRPG, and the flexibility of the game is lost. But!, I add a thing here or there, trying to make my players' experience better, and so far it's all been great.
For 2023 I'm running my second campaign, the highly regarded official adventure " Curse of Strahd ". Leading up to my prep time, I surveyed ...
I'm new to DM'ing, and new to Foundry VTT, and this blog post of Action Jay's work on how he's running the Curse of Strahd was a great resource to modules, tools, and approaches to improve my own gameplay.
Ultimately this is the fault of the poor democratic system implemented in the US. A truly progressive option can't be formed because it would split the support of the Democratic Party, leaving the Republicans to take everything in the first-past-the-post voting system. In the absence of electoral reform, or a progressive takeover within the Democrats, or maybe a gigantic scandal that shakes up ether party creating new opportunities... the best option for a progressive voters seems to be to support these idiots rather than letting those idiots in. And the best option for the Democrats as a party that wants power is to cater to the middle and be inoffensive, driving this entire thing into a loop where little of value gets done.
@GrindingGears@lemmy.ca -- Ooh, saw your post too late this time, but next year check out https://cyclepalooza.ca/event/summer-solstice-overnight-greenway-loop/. It was a blast.
😴
Hm... I think if they fucked up and were negligent, this is a reasonable slap on the wrist judgement. If they fucked up, and then were knowledgeable in a malicious cover-up of their fuck up, this seems like a light punishment. The evidence seems to weigh towards the second, but the punishment gives them the benefit of the doubt on that.
Adventuring with Pride -- A aeries of D&D 5e adventures with a focus on LGBT+ themes
A supplement for 5e focused around queer themes and LGBT+ culture. 50% of proceeds go to Stonewall!
I came across these published supplements recently as they one was listed as a winner of the 2023 LGBTQ Tabletop Game Award. They have a series of adventures, as well as pregen characters, and some additional subclasses, monsters, backgrounds, and items.
I'm sure this won't be everyone's jam, but I've been reviewing this content and I'm really intrigued with the settings and culture that it would bring to the right campaign and players. Thought it would be worth a share!
Bisecting the Linux Kernel with NixOS
Recently my kernel started to panic every time I awoke my monitors from sleep. This seemed to be a regression; it worked one day, then I received a kernel upgrade from upstream, and the next time I was operating my machine it would crash when I came back to it.
After being annoyed for a bit, I realized this was a great time to learn how to bisect the git kernel, find the problem, and either report it upstream, or, patch it out of my kernel! I thought this would be useful to someone else in the future, so here we are.
Step #1: Clone the Kernel; I grabbed Linus' tree from https://github.com/torvalds/linux with git clone git@github.com:torvalds/linux.git
Step #2: Start a bisect.
If you're not familiar with a bisect, it's a process by which you tell git, "this commit was fine", and "this commit was broken", and it will help you test the commits in-between to find the one that introduced the problem.
You start this by running git bisect start, and then you provide a tag or commit ID for the good and the bad kernel with git bisect good ... and git bisect bad ....
I knew my issue didn't occur on the 5.15 kernel series, but did start with my NixOS upgrade to 6.1. But I didn't know precisely where, so I aimed a little broader... I figured an extra test or two would be better than missing the problem. 😬
git bisect start git bisect good v5.15 git bisect bad master
Step #3: Replace your kernel with that version
In an ideal world, I would have been able to test this in a VM. But it was a graphics problem with my video card and connected monitors, so I went straight for testing this on my desktop to ensure it was easy to reproduce and accurate.
Testing a mid-release kernel with NixOS is pretty easy! All you have to do is override your kernel package, and NixOS will handle building it for you... here's an example from my bisect:
boot.kernelPackages = pkgs.linuxPackagesFor (pkgs.linux_6_2.override { # (#4) argsOverride = rec { src = pkgs.fetchFromGitHub { owner = "torvalds"; repo = "linux"; # (#1) -> put the bisect revision here rev = "7484a5bc153e81a1740c06ce037fd55b7638335c"; # (#2) -> clear the sha; run a build, get the sha, populate the sha sha256 = "sha256-nr7CbJO6kQiJHJIh7vypDjmUJ5LA9v9VDz6ayzBh7nI="; }; dontStrip = true; # (#3) `head Makefile` from the kernel and put the right version numbers here version = "6.2.0"; modDirVersion = "6.2.0-rc2"; # (#4) `nixos-rebuild boot`, reboot, test. }; });
Getting this defined requires a couple intermediate steps...
Step #3.1 -- put the version that git bisect asked me to test in (#1)
Step #3.2 -- clear out sha256
Step #3.3 -- run a nixos-rebuild boot
Step #3.4 -- grab the sha256 and put it into the sha256 field (#2)
Step #3.5 -- make sure the major version matches at (#3) and (#4)
Then run nixos-rebuild boot.
Step #4: Test!
Reboot into the new kernel, and test whatever is broken. For me I was able to set up a simple test protocol: xset dpms force off to blank my screens, wait 30 seconds, and then wake them. If my kernel panicked then it was a fail.
Step #5: Repeat the bisect
Go into the linux source tree and run git bisect good or git bisect bad depending on whether the test succeeded. Return to step #3.
Step #6: Revert it!
For my case, I eventually found a single commit that introduced the problem, and I was able to revert it from my local kernel. This involves leaving a kernel patch in my NixOS config like this:
boot.kernelPatches = [ { patch = ./revert-bb2ff6c27b.patch; name = "revert-bb2ff6c27b"; } ];
This probably isn't the greatest long-term solution, but it gets my desktop stable and I'm happy with that for now.
Profit!