xcr.jp

Bluesky is pretty neat but every user being @*.bsky.social isn’t really my thing since I’m a nerd with my own domain. So rather than be @superpj.bsky.social I changed mine to @superpj.xcr.jp with a simple DNS entry but you can also do it with just a text file on your personal hosting if that’s not your jam.

So sigh into Bluesky and go to settings.

Click on Account

Next click on @ Handle

Leave the top part alone but at the bottom click “I have my own Domain”

Type your domain without the www in the text box then select DNS Panel if you’re comfortable with that method.

Sign into your DNS manager and find the domain you’re using.

Create a TXT record with the info on the screen with the _atproto in the host field and the enter the line that starts with did= in the value field.

Select Verify DNS Record, however this may take a few minutes to activate.

Alternatively you can use the No DNS Panel option which is as easy as making a text file and uploading it to the ./well-known path on your domain. Follow the on screen instructions for this. If you don’t see ./well-known when you’re looking at your hosting you might need to pick your domain from the folder list and see if it’s in there. Once uploaded click Verify Text File.

That’s it, now you’re fancy.

PSA, repairing the Crowdstrike BSoD on Azure-hosted VMs

Hey! If you’re like us and have a bunch of servers in Azure running Crowdstrike, the past 8 hours have probably SUCKED for you! The only guidance is to boot in safe mode, but how the heck do you do that on an Azure VM??

I wanted to quickly share what worked for us:

1) Make a clone of your OS disk. Snapshot –> create a new disk from it, create a new disk directly with the old disk as source, whatever your preferred workflow is

2) Attach the cloned OS disk to a functional server as a data disk

3) Open disk management (create and format hard disk partitions), find the new disk, right click, “online”

4) Check the letters of the disk partitions: both system reserved and windows

5) Navigate to the staged disk’s Windows drive, deal with the Crowdstrike files. Either rename the Crowdstrike folder at Windows\System32\drivers\Crowdstrike as Crowdstrike.bak or similar, delete the the file matching “C-00000291*.sys”, per Crowdstrike’s instructions, whatever

From here, we found that if we replaced the disk on the server, we would get a winload.exe boot manager error instead! Don’t dismount your disk, we aren’t done yet!

6) Pull up this MS Learn doc: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/error-code-0xc000000e

7) Follow the instructions in the document to run bcdedit repairs on your boot directory. So in our case, that meant the following — replace F: and H: with the appropriate drive letters. Note that the document says you need to delete your original VM — we found that just swapping out the disk was OK and we did not need to actually delete and recreate anything, but YMMV.

bcdedit /store F:\boot\bcd /set {bootmgr} device partition=F:

bcdedit /store F:\boot\bcd /set {bootmgr} integrityservices enable

bcdedit /store F:\boot\bcd /set {af3872a5-} device partition=H:

bcdedit /store F:\boot\bcd /set {af3872a5-} integrityservices enable

bcdedit /store F:\boot\bcd /set {af3872a5-} recoveryenabled Off

bcdedit /store F:\boot\bcd /set {af3872a5-} osdevice partition=H:

bcdedit /store F:\boot\bcd /set {af3872a5-} bootstatuspolicy IgnoreAllFailures

8) NOW dismount the disk, and swap it in on your original VM. Try to start the VM.

• Canon M50
• TTArtisan 35mm F0.95
• Urban Filmic Pack for Canon by Thomas Fransson
  • https://thomasfransson.gumroad.com/l/vwxus

Disable CoPilot/AI features on Windows 11, you can follow these steps:

1. Remove CoPilot from the Taskbar:
   • Go to Settings > Personalization.
   • Scroll down and select Taskbar.
   • Toggle off CoPilot.
2. Disable CoPilot Completely:
   • Click Start and search for “gpedit” to open the Group Policy Editor.
   • Navigate to User Configuration > Administrative Templates > Windows Components > Windows CoPilot.
   • Double-click Turn off Windows CoPilot.
   • Click Enabled, then Apply, and OK.

To allow it back into your life follow the Disable steps and change Enabled back to Not Configured.

I’m always forgetting the commands so here’s the short easy version

From the Terminal menu

system/check-installation
#hopefully it says “status: installation is ok”

#if you’re upgrading from 6 to 7 it needs to know that.. If not skip the below line.
system package update set channel=upgrade

#check for updates
system package update check-for-updates

#get the update
system package update download

#reboot
system reboot

#that’s it.

Thank you Threads. Now please stop having a dozen sex bots follow me a day. Unless you make real life sex bots. Then we need to talk about a subscription service.

I don’t understand Threads at all. It’s a social media site that you can add friends to but has 0 ability to see what your friends have posted besides going to each individual profile. How the hell was that overlooked but there’s a whole algorithm to show you what’s trending and what your friends have liked.

Obviously I switched back to Hyper-V but my environment is built for 2gig internet. Speedtests were south of 1meg… So on each Hyper-V host I ran this powershell command for each external vmswitch to clear it up..

Set-VMSwitch -Name "The switch name" -EnableSoftwareRsc $false

Like

Set-VMSwitch -Name External -EnableSoftwareRsc $false
Set-VMSwitch -Name Bridge -EnableSoftwareRsc $false