Rabbi Blog - Recent changes [en]

Powershell: Ping Range

Rabbi Bob — Thu, 06 Aug 2026 19:58:00 GMT

Created page with "Category:Powershell Category:Weblog-2026-08 Not an original script. =Usage= <pre> .\Test-IPRange-Threaded.ps1 -startIP "192.168.1.1" -endIP "192.168.1.50" </pre> =Script= <pre> # 10.101.50.70 255.255.0.0 <# .SYNOPSIS Pings a range of IP addresses concurrently to check their online status. .DESCRIPTION This script takes a start IP address and an end IP address. It iterates through each IP address in the specified range (primarily designed for range..."

New page

[[Category:Powershell]]
[[Category:Weblog-2026-08]]

Not an original script.
=Usage=
<pre> .\Test-IPRange-Threaded.ps1 -startIP "192.168.1.1" -endIP "192.168.1.50" </pre>

=Script=

<pre>
# 10.101.50.70 255.255.0.0
<#
.SYNOPSIS
Pings a range of IP addresses concurrently to check their online status.

.DESCRIPTION
This script takes a start IP address and an end IP address. It iterates through
each IP address in the specified range (primarily designed for ranges within
the same /24 subnet) and sends two ping requests to each IP concurrently
using PowerShell runspaces for improved efficiency.

- If an address responds to one or more pings, it's marked as "Online".
- If an address does not respond to either ping, it's marked as "Offline".
- Errors during a specific IP ping are marked as "Error".

.PARAMETER startIP
The starting IP address of the range (e.g., "192.168.1.1"). This is a mandatory parameter.

.PARAMETER endIP
The ending IP address of the range (e.g., "192.168.1.254"). This is a mandatory parameter.

.PARAMETER ThrottleLimit
The maximum number of concurrent ping operations. Default is 30.
Adjust this based on your system's resources and network considerations.

.EXAMPLE
.\Test-IPRange-Threaded.ps1 -startIP "192.168.1.1" -endIP "192.168.1.50"

This command will ping IP addresses from 192.168.1.1 to 192.168.1.50 concurrently
(using the default throttle limit), sending two pings to each and reporting their status.

.EXAMPLE
.\Test-IPRange-Threaded.ps1 -startIP "10.0.0.1" -endIP "10.0.0.254" -ThrottleLimit 50

This command will ping IPs in the 10.0.0.x range with up to 50 concurrent operations.

.NOTES
- This script uses PowerShell Runspace Pools for threading, compatible with PowerShell 5.1+.
- For PowerShell 7.0 and newer, ForEach-Object -Parallel offers a simpler syntax for parallel execution.
- The script assumes the IP range is primarily within the same /24 subnet. It uses the first
three octets of 'startIP' as the base network prefix.
- If 'startIP' and 'endIP' have different network prefixes, a warning is displayed, and the scan
proceeds using 'startIP's' network prefix.
- To run this script:
1. Save it as a .ps1 file (e.g., Test-IPRange-Threaded.ps1).
2. Open PowerShell.
3. Navigate to the directory where you saved the file.
4. If needed, adjust your execution policy: Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
5. Run: .\Test-IPRange-Threaded.ps1 -startIP "YOUR_START_IP" -endIP "YOUR_END_IP" [-ThrottleLimit DESIRED_NUMBER]
#>
param (
[Parameter(Mandatory=$true, HelpMessage="Enter the starting IP address (e.g., 192.168.1.1)")]
[string]$startIP,

[Parameter(Mandatory=$true, HelpMessage="Enter the ending IP address (e.g., 192.168.1.254)")]
[string]$endIP,

[Parameter(HelpMessage="Maximum number of concurrent ping operations. Default is 30.")]
[ValidateRange(1,200)] # Practical limit for throttle
[int]$ThrottleLimit = 30
)

# --- Script Body ---

Write-Host "🚀 Initializing threaded ping scan..." -ForegroundColor Yellow

# Basic IP address format validation (IPv4)
$ipPattern = '^\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}$'
if (-not ($startIP -match $ipPattern)) {
Write-Error "Invalid format for Start IP: '$startIP'. Please use a valid IPv4 format (e.g., 192.168.1.1)."
exit 1
}
if (-not ($endIP -match $ipPattern)) {
Write-Error "Invalid format for End IP: '$endIP'. Please use a valid IPv4 format (e.g., 192.168.1.254)."
exit 1
}

# Parse IP addresses
try {
$startAddressBytes = [System.Net.IPAddress]::Parse($startIP).GetAddressBytes()
$endAddressBytes = [System.Net.IPAddress]::Parse($endIP).GetAddressBytes()
} catch {
Write-Error "Failed to parse one or both IP addresses. Ensure they are valid IPv4 addresses."
Write-Error "Error details: $($_.Exception.Message)"
exit 1
}

$networkPrefix = "$($startAddressBytes[0]).$($startAddressBytes[1]).$($startAddressBytes[2])"
$startHostOctet = [int]$startAddressBytes[3]
$endHostOctetLoopEnd = [int]$endAddressBytes[3]

if (($startAddressBytes[0] -ne $endAddressBytes[0]) -or `
($startAddressBytes[1] -ne $endAddressBytes[1]) -or `
($startAddressBytes[2] -ne $endAddressBytes[2])) {
Write-Warning "The Start IP ($startIP) and End IP ($endIP) do not share the same first three octets."
Write-Warning "This script will use the network prefix of the Start IP ('$networkPrefix.x') and iterate the last octet from $startHostOctet to $endHostOctetLoopEnd."
}

if ($startHostOctet -gt $endHostOctetLoopEnd) {
Write-Error "The last octet of Start IP ($startHostOctet) is greater than the last octet of End IP ($endHostOctetLoopEnd) for the determined network prefix '$networkPrefix.x'. This forms an invalid range for this script's logic."
exit 1
}

# Generate list of IPs to test
$ipsToTest = [System.Collections.Generic.List[string]]::new()
for ($currentHostOctet = $startHostOctet; $currentHostOctet -le $endHostOctetLoopEnd; $currentHostOctet++) {
$ipsToTest.Add("$networkPrefix.$currentHostOctet")
}

if ($ipsToTest.Count -eq 0) {
Write-Warning "No IP addresses generated for the given range. Exiting."
exit 0
}

$fullStartRangeIPToScan = $ipsToTest[0]
$fullEndRangeIPToScan = $ipsToTest[$ipsToTest.Count -1]

Write-Host "Scanning IP addresses from $fullStartRangeIPToScan to $fullEndRangeIPToScan."
Write-Host "Using up to $ThrottleLimit concurrent threads."
Write-Host "Each IP will be pinged twice."
Write-Host "--------------------------------------------------"

# Define the script block to be executed in each thread
$scriptBlock = {
param($targetIPToPing)

# Test-Connection sends ICMP echo requests.
$pingReplies = Test-Connection -ComputerName $targetIPToPing -Count 2 -ErrorAction SilentlyContinue -WarningAction SilentlyContinue

if ($pingReplies) {
return [PSCustomObject]@{
IPAddress = $targetIPToPing
Status = "Online"
Timestamp = Get-Date
}
} else {
return [PSCustomObject]@{
IPAddress = $targetIPToPing
Status = "Offline"
Timestamp = Get-Date
}
}
}

# Initialize Runspace Pool
$runspacePool = [runspacefactory]::CreateRunspacePool(1, $ThrottleLimit)
$runspacePool.Open()

$activeJobs = [System.Collections.Generic.List[object]]::new()
$finalResults = [System.Collections.Generic.List[object]]::new()

try {
foreach ($ip in $ipsToTest) {
$powershell = [powershell]::Create().AddScript($scriptBlock).AddArgument($ip)
$powershell.RunspacePool = $runspacePool

$activeJobs.Add([PSCustomObject]@{
IP = $ip
Pipe = $powershell
AsyncHandle = $powershell.BeginInvoke()
})
}

$totalIPs = $ipsToTest.Count
$processedCount = 0

# Monitor and process completed jobs
while ($activeJobs.Count -gt 0) {
# Create a temporary list of jobs that have completed in this iteration
$completedThisIteration = [System.Collections.Generic.List[object]]::new()

foreach ($jobHandle in $activeJobs) {
if ($jobHandle.AsyncHandle.IsCompleted) {
$completedThisIteration.Add($jobHandle)
try {
$resultObject = $jobHandle.Pipe.EndInvoke($jobHandle.AsyncHandle)
if ($resultObject) {
$finalResults.Add($resultObject)
}
} catch {
Write-Warning "Error processing IP $($jobHandle.IP): $($_.Exception.Message)"
$finalResults.Add([PSCustomObject]@{
IPAddress = $jobHandle.IP
Status = "Error"
Message = $_.Exception.Message
Timestamp = Get-Date
})
} finally {
$jobHandle.Pipe.Dispose()
$processedCount++
}
}
}

# Remove all completed jobs from the active list
if ($completedThisIteration.Count -gt 0) {
$completedThisIteration | ForEach-Object { $activeJobs.Remove($_) }
}

if ($activeJobs.Count -gt 0) {
Write-Progress -Activity "Pinging IPs" -Status "Processing... ($processedCount/$totalIPs completed)" -PercentComplete ([math]::Round(($processedCount / $totalIPs) * 100)) -CurrentOperation "$($activeJobs.Count) tasks remaining"
Start-Sleep -Milliseconds 200 # Wait a bit before checking again
}
}
Write-Progress -Activity "Pinging IPs" -Completed
}
finally {
# Close and dispose the runspace pool
if ($runspacePool) {
$runspacePool.Close()
$runspacePool.Dispose()
}
Write-Host "Runspace pool closed." -ForegroundColor DarkGray
}

# Sort and display all collected results
Write-Host "`n--- Scan Results (Sorted by IP) ---" -ForegroundColor Yellow
$sortedResults = $finalResults | Sort-Object { [System.Net.IPAddress]$_.IPAddress }

foreach ($result in $sortedResults) {
switch ($result.Status) {
"Online" { Write-Host "> $($result.IPAddress) - $($result.Status) ✅" -ForegroundColor Green }
#"Offline" { Write-Host "> $($result.IPAddress) - $($result.Status) ❌" -ForegroundColor Red }
#"Error" { Write-Host "> $($result.IPAddress) - $($result.Status) ⚠️ (Message: $($result.Message))" -ForegroundColor Magenta }
#default { Write-Host "> $($result.IPAddress) - Status Unknown" }
}
}

Write-Host "--------------------------------------------------"
Write-Host "🎉 Threaded ping scan finished." -ForegroundColor Yellow
</pre>

Powershell: Ping Stuff

Rabbi Bob — Thu, 06 Aug 2026 19:54:41 GMT

Created page with "Category:Powershell Category:Weblog-2026-08 Provide a list of IP addresses, run the script. Checks DNS and outputs a results file. =Code= <pre> $deviceNames = Get-Content "devices.txt" $results = @() foreach ($name in $deviceNames) { $status = "Unknown" try { # Attempt to resolve DNS [System.Net.Dns]::GetHostEntry($name) $status = "Resolving..." # Check if device pings (up to 4 attempts with 1 second timeout) if (Test-Connect..."

New page

[[Category:Powershell]]
[[Category:Weblog-2026-08]]

Provide a list of IP addresses, run the script. Checks DNS and outputs a results file.

=Code=
<pre>
$deviceNames = Get-Content "devices.txt"

$results = @()

foreach ($name in $deviceNames) {
$status = "Unknown"

try {
# Attempt to resolve DNS
[System.Net.Dns]::GetHostEntry($name)
$status = "Resolving..."

# Check if device pings (up to 4 attempts with 1 second timeout)
if (Test-Connection -ComputerName $name -Count 1 -Quiet) {
$status = "Up"
} else {
$status = "Down"
}
} catch {
# Handle DNS resolution failure
$status = "NO DNS"
}

# Create a custom object for each device
$result = New-Object PSObject -Property @{
Name = $name
Status = $status
}

# Add object to results array
$results += $result
}

# Export results to CSV
$results | Export-Csv -Path "results.csv" -NoTypeInformation -Force

Write-Host "Results exported to 'results.csv'"
</pre>

Adventures in ProxMox

Rabbi Bob — Tue, 28 Jul 2026 19:21:07 GMT

Local Backups

@@ Line 40: / Line 40: @@
 pvesm set LocalBackups --is_mountpoint yes
 </pre>
+minutes was better (1TB VM).  Probably could better better, but it's ok enough.
 [[Category:ProxMox]]

Right In The Pi-hole

Rabbi Bob — Sat, 25 Jul 2026 21:30:56 GMT

Install

← Older revision		Revision as of 21:30, 25 July 2026
(2 intermediate revisions by the same user not shown)
Line 120:		Line 120:
	sudo pihole-FTL --config webserver.api.app_sudo true		sudo pihole-FTL --config webserver.api.app_sudo true
	==Install==		==Install==
			Don't do a round robin setup. It doesn't go well. Ask me how I know this...<br>
			I also opted to do a non-full sync as I have split DHCP scopes running.<br><br>
	<pre>		<pre>
	wget https://github.com/lovelaze/nebula-sync/releases/latest/download/nebula-sync_0.11.2_linux_amd64.tar.gz		wget https://github.com/lovelaze/nebula-sync/releases/latest/download/nebula-sync_0.11.2_linux_amd64.tar.gz
Line 132:		Line 134:
	<pre>		<pre>
	PRIMARY=http://192.168.1.9\|PASSWORD		PRIMARY=http://192.168.1.9\|PASSWORD
	REPLICAS=http://192.168.~~110~~\|PASSWORD		REPLICAS=http://192.168.1.10\|PASSWORD
	FULL_SYNC=false		FULL_SYNC=false
	SYNC_CONFIG_DHCP=false		SYNC_CONFIG_DHCP=false
Line 138:		Line 140:
	SYNC_CONFIG_NTP=true		SYNC_CONFIG_NTP=true
	SYNC_CONFIG_RESOLVER=true		SYNC_CONFIG_RESOLVER=true
			SYNC_CONFIG_DATABASE=true
			SYNC_CONFIG_MISC=true
	SYNC_GRAVITY_AD_LIST=true		SYNC_GRAVITY_AD_LIST=true
			SYNC_GRAVITY_AD_LIST_BY_GROUP=true
			SYNC_GRAVITY_DOMAIN_LIST=true
			SYNC_GRAVITY_DOMAIN_LIST_BY_GROUP=true
			SYNC_GRAVITY_CLIENT=true
			SYNC_GRAVITY_CLIENT_BY_GROUP=true
			SYNC_GRAVITY_GROUP=true
	RUN_GRAVITY=true		RUN_GRAVITY=true
	CRON=0 * * * *		CRON=0 * * * *
	TZ=America/New_York		TZ=America/New_York</pre>
	</pre>

	<pre>		<pre>

Adventures in ProxMox

Rabbi Bob — Sat, 25 Jul 2026 21:03:11 GMT

Local Backups

@@ Line 20: / Line 20: @@
 <br><br>
 Pretty slick.
 [[Category:ProxMox]]

Right In The Pi-hole

Rabbi Bob — Thu, 23 Jul 2026 23:10:28 GMT

Install

Show changes

VoYD

Rabbi Bob — Thu, 23 Jul 2026 00:24:12 GMT

Gigs

← Older revision		Revision as of 00:24, 23 July 2026
Line 1:		Line 1:
	=Gigs=		=Gigs=
	* https://~~www~~.~~rabbibob~~.com~~/voydcalendar/~~		* https://voyd.mikebeane.com
	* [https://docs.google.com/spreadsheets/d/e/2PACX-1vS3fepEaCnI1XjzccsC7SXo5Dno9X6jm9Ghy7ubFGn9BAleei9UiFG3L8lFoSh6xmEpiqH8OiIRLVIG/pubhtml?gid=2044986723&single=true Calendar Output]		* [https://docs.google.com/spreadsheets/d/e/2PACX-1vS3fepEaCnI1XjzccsC7SXo5Dno9X6jm9Ghy7ubFGn9BAleei9UiFG3L8lFoSh6xmEpiqH8OiIRLVIG/pubhtml?gid=2044986723&single=true Calendar Output]
	==Older==		==Older==

Adventures in ProxMox

Rabbi Bob — Wed, 22 Jul 2026 23:45:29 GMT

Wednesday

← Older revision		Revision as of 23:45, 22 July 2026
Line 16:		Line 16:
	Executed a backup of Attic2024 over to the NAS and then used the backup utility to restore it with a uniqueID. Threw in another gig of RAM for yucks.		Executed a backup of Attic2024 over to the NAS and then used the backup utility to restore it with a uniqueID. Threw in another gig of RAM for yucks.

			=Wednesday (The Next)=
			And now we're up on a completely different box running ProxMox, having backed up the server to NAS, then restored it to the new setup.
			<br><br>
			Pretty slick.
	[[Category:ProxMox]]		[[Category:ProxMox]]

Right In The Pi-hole

Rabbi Bob — Thu, 16 Jul 2026 22:16:53 GMT

@@ Line 1: / Line 1: @@
 Ran into issues with ubuntu-26.04-standard container in [[ProxMox]] in regards to dig: there was no output.  Tested 22.04 and it worked. Resorted 25.04.
-=Setup=
+=Pi-hole=
-==Pi-hole==
+==Setup==
 <pre>
 sudo apt update && sudo apt upgrade -y
@@ Line 21: / Line 21: @@
 Go to http://IP:80/admin and login
 [[Category:Pi-hole]]

Right In The Pi-hole

Rabbi Bob — Thu, 16 Jul 2026 22:08:31 GMT

Created page with "Ran into issues with ubuntu-26.04-standard container in ProxMox in regards to dig: there was no output. Tested 22.04 and it worked. Resorted 25.04. =Setup= ==Pi-hole== <pre> sudo apt update && sudo apt upgrade -y sudo apt install curl -y sudo systemctl stop systemd-resolved sudo systemctl disable systemd-resolved sudo rm /etc/resolv.conf echo "nameserver 1.1.1.1" | sudo tee /etc/resolv.conf curl -sSL https://install.pi-hole.net | sudo PIHOLE_SKIP_OS_CHECK=true bash..."

New page

Ran into issues with ubuntu-26.04-standard container in [[ProxMox]] in regards to dig: there was no output. Tested 22.04 and it worked. Resorted 25.04.

=Setup=
==Pi-hole==
<pre>
sudo apt update && sudo apt upgrade -y
sudo apt install curl -y
sudo systemctl stop systemd-resolved
sudo systemctl disable systemd-resolved
sudo rm /etc/resolv.conf
echo "nameserver 1.1.1.1" | sudo tee /etc/resolv.conf
curl -sSL https://install.pi-hole.net | sudo PIHOLE_SKIP_OS_CHECK=true bash
</pre>
==Selections==
Do the setup questions...
==Password==
<pre>
pihole setpassword
</pre>
==URL==
Go to http://IP:80/admin and login

[[Category:Pi-hole]]

Adventures in ProxMox

Rabbi Bob — Wed, 15 Jul 2026 23:05:57 GMT

← Older revision		Revision as of 23:05, 15 July 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
			=Monday=
	On Monday evening I stood up a ProxMox host server with some lesser hardware than the webserver (though it does have a wee bit more RAM). Established an ISO folder off the NAS and did some basic things. Set up a Win7 Home instance just to test getting a VM going: that went fairly well. Finding a 32-bit browser on the VM was the bigger challenge.		On Monday evening I stood up a ProxMox host server with some lesser hardware than the webserver (though it does have a wee bit more RAM). Established an ISO folder off the NAS and did some basic things. Set up a Win7 Home instance just to test getting a VM going: that went fairly well. Finding a 32-bit browser on the VM was the bigger challenge.
			=Tuesday=
	On Tuesday evening, I powered off the webserver and clonezilla'd it. I thought I was having cloning issues, so I ended up doing that twice. Just as I was going to bed, I fired up Clonezilla from the blank VM and kicked off the restore... from my phone. I really missed having arrow keys, but otherwise that was a kick.		On Tuesday evening, I powered off the webserver and clonezilla'd it. I thought I was having cloning issues, so I ended up doing that twice. Just as I was going to bed, I fired up Clonezilla from the blank VM and kicked off the restore... from my phone. I really missed having arrow keys, but otherwise that was a kick.
			=Wednesday=
			==Morning==
	This morning, restarted the VM after cloning: "Booting from Hard Disk.." message. Same thing from last night where I had assumed it was the cloning. Ends up I needed to change the BIOS to UEFI and then add an EFI disk. BOOTS GALORE! Updated the network info and... well, this update is on the VM!		This morning, restarted the VM after cloning: "Booting from Hard Disk.." message. Same thing from last night where I had assumed it was the cloning. Ends up I needed to change the BIOS to UEFI and then add an EFI disk. BOOTS GALORE! Updated the network info and... well, this update is on the VM!
			<br><br>
	It will probably be a few days before the next steps, which is to remove the disks from the old server and stand up another ProxMox instance, then verify that backups work to where I can restore to a different ProxMox server.		It will probably be a few days before the next steps, which is to remove the disks from the old server and stand up another ProxMox instance, then verify that backups work to where I can restore to a different ProxMox server.
			<br><br>
	All this for snapshots (I kid, there are many more reasons)!		All this for snapshots (I kid, there are many more reasons)!<br><br>
			From an "ease of use" perspective, this was very straight-forward, even with the hiccups. ProxMox+++
			==Evening==
			Hello from Attic2024-2.
			<br><br>
			Executed a backup of Attic2024 over to the NAS and then used the backup utility to restore it with a uniqueID. Threw in another gig of RAM for yucks.

	[[Category:ProxMox]]		[[Category:ProxMox]]

Adventures in ProxMox

Rabbi Bob — Wed, 15 Jul 2026 10:45:23 GMT

Created page with "On Monday evening I stood up a ProxMox host server with some lesser hardware than the webserver (though it does have a wee bit more RAM). Established an ISO folder off the NAS and did some basic things. Set up a Win7 Home instance just to test getting a VM going: that went fairly well. Finding a 32-bit browser on the VM was the bigger challenge. On Tuesday evening, I powered off the webserver and clonezilla'd it. I thought I was having cloning issues, so I ended up..."

New page

On Monday evening I stood up a ProxMox host server with some lesser hardware than the webserver (though it does have a wee bit more RAM). Established an ISO folder off the NAS and did some basic things. Set up a Win7 Home instance just to test getting a VM going: that went fairly well. Finding a 32-bit browser on the VM was the bigger challenge.

On Tuesday evening, I powered off the webserver and clonezilla'd it. I thought I was having cloning issues, so I ended up doing that twice. Just as I was going to bed, I fired up Clonezilla from the blank VM and kicked off the restore... from my phone. I really missed having arrow keys, but otherwise that was a kick.

This morning, restarted the VM after cloning: "Booting from Hard Disk.." message. Same thing from last night where I had assumed it was the cloning. Ends up I needed to change the BIOS to UEFI and then add an EFI disk. BOOTS GALORE! Updated the network info and... well, this update is on the VM!

It will probably be a few days before the next steps, which is to remove the disks from the old server and stand up another ProxMox instance, then verify that backups work to where I can restore to a different ProxMox server.

All this for snapshots (I kid, there are many more reasons)!

[[Category:ProxMox]]

Mediawiki 1.43 from 1.39

Rabbi Bob — Mon, 13 Jul 2026 17:45:53 GMT

@@ Line 34: / Line 34: @@
 ** SQLite 3.31.0 or higher
-=The Approach=
+=June Notes=
 ==PHP 8.4==
 * This can be done prior to the major jump as 1.39 supports 8.4
@@ Line 50: / Line 49: @@
 * sudo systemctl restart apache2
 * Check wiki version, should be at 8.4.x
 ==Prepping the Databases==

Guitar Chord Webpage Converter

Rabbi Bob — Sun, 12 Jul 2026 17:10:55 GMT

@@ Line 1: / Line 1: @@
 =Name=
@@ Line 7: / Line 87: @@
 You are a guitar chord sheet formatting assistant. I want you to take the raw text of the song I paste below and clean it up perfectly so I can copy and paste it directly into a Google Document. Immediately prompt the user for what they need to do when a new chat is started.<br><br>
 Please follow these exact formatting constraints:<br><br>
 # If tablature exists in the information, ask the user if they want to keep the tablature intact so they can read how parts are played.  They can use the keyword "keep tab" at the start of the submission.
 # Wrap the entire song inside a monospaced code block (fixed-width font).
 # Ensure every single chord is precisely aligned above the exact lyric/syllable where the change happens. Use standard spaces to preserve this alignment.
 # Clean out any web clutter, ad banners, pop-up text, or site navigation artifacts.
 # Keep the labels like [Intro], [Verse], and [Chorus] on their own separate lines.
 # If a song mentions having a capo (example: "capo on 3rd fret")
@@ Line 19: / Line 101: @@
 # If there are multiple versions in the paste, ask the user which version to focus on.
 #* Example: if there is an Official Version and an Acoustic Version, ask which to focus on.  Ignore all other versions.
+# Remind the user that in order to keep your chords and lyrics perfectly aligned when copying and pasting into Google Docs, you must use a monospaced (fixed-width) font.
 ==Commands==
 ===Compress===
 * place the chords in line with the lyrics to condense the document, however carriage return when appropriate.
@@ Line 36: / Line 122: @@
 * Ask them what key they would like to convert the song to.
 * Always use the sharp rather than the flat whenever possible.
-===restart===
+===Dedup===
 * Reset the chat and introduce yourself to the user
 ===reset===

Guitar Chord Webpage Converter

Rabbi Bob — Sun, 12 Jul 2026 13:50:13 GMT

Created page with " =Name= * Guitar Chord Webpage Converter =Description= * Converts pasted webpage information from guitar chord\lyric sites into something useful to paste into Google Docs. =Instructions= You are a guitar chord sheet formatting assistant. I want you to take the raw text of the song I paste below and clean it up perfectly so I can copy and paste it directly into a Google Document. Immediately prompt the user for what they need to do when a new chat is started. Plea..."

New page

=Name=
* Guitar Chord Webpage Converter
=Description=
* Converts pasted webpage information from guitar chord\lyric sites into something useful to paste into Google Docs.
=Instructions=
You are a guitar chord sheet formatting assistant. I want you to take the raw text of the song I paste below and clean it up perfectly so I can copy and paste it directly into a Google Document. Immediately prompt the user for what they need to do when a new chat is started. 
Please follow these exact formatting constraints: 
# If tablature exists in the information, ask the user if they want to keep the tablature intact so they can read how parts are played. They can use the keyword "keep tab" at the start of the submission.
# Wrap the entire song inside a monospaced code block (fixed-width font).
# Ensure every single chord is precisely aligned above the exact lyric/syllable where the change happens. Use standard spaces to preserve this alignment.
# Clean out any web clutter, ad banners, pop-up text, or site navigation artifacts.
# Keep the labels like [Intro], [Verse], and [Chorus] on their own separate lines.
# If a song mentions having a capo (example: "capo on 3rd fret")
#* If there is no capo, do not ask the question.
## Ask the person if they want you to transpose the chords so that the actual chords that are being played are stated in the final output.
##* This should be a Yes\No question.
# Include the song title, artist, song key, and tuning at the top.
# If there are multiple versions in the paste, ask the user which version to focus on.
#* Example: if there is an Official Version and an Acoustic Version, ask which to focus on. Ignore all other versions.

==Commands==
===Compress===
* place the chords in line with the lyrics to condense the document, however carriage return when appropriate.
** If carriage returning, always start with the chord.
* Page justification is left justified.
* Remove any leading spaces if the line is starting with a chord.
* Each chord should be encapsulated in brackets.
* After a chord bracket, include 1 space.
===Recompress===
* Rerun the compress command again
===Decompress===
* Revert back to the information before "Compress" was used.
===Transpose===
* Always give the user the current key of the song
* Ask them what key they would like to convert the song to.
* Always use the sharp rather than the flat whenever possible.
===restart===
* Reset the chat and introduce yourself to the user
===reset===
* Reset the chat and introduce yourself to the user
</pre>

[[Category:Guitar]]
[[Category:AI]]
[[Category:Gems]]

Mediawiki 1.43 from 1.39

Rabbi Bob — Fri, 10 Jul 2026 14:16:17 GMT

The Approach

@@ Line 36: / Line 36: @@
 =The Approach=
 * ALL THIS STUFF IS FROM THE LAST PAGE, REVAMP IT!
 ==Prepping the Databases==
 # Backup the MW databases
@@ Line 69: / Line 84: @@
 ** Some were not
 * Fiddled until things were working.  Had to fix some code for YouTube.
 =Summary=
 * I tried this about seven months ago and I was attempting to update the extensions as I went: this was not the way to go.  Getting the database updated was the key and ignoring everything else made that easier to do.  All a wiki really is at the base is the information (database) and the images/... everything else is functionality.
 [[Category:Wiki]]