Friday, September 4, 2026

Experiencing Technical Difficulties - I Can No Longer Comment in the Comments

Technical Issues Magically Resolved themselves this morning.  WTF, over!

from Google AI:
Google finally deployed a back-end fix to resolve a widespread bug that was blocking the platform's commenting system. [1]
If you or your readers noticed comments getting stuck indefinitely on the "publishing..." status over the last 24 to 48 hours, you were caught in a verified, global platform glitch. [1, 2, 3]
What actually happened?
  • The "Publishing" Loop Bug: Starting around September 3–4, a massive influx of users reported that whenever they attempted to submit a comment on any Blogspot site, the form would get stuck on "publishing" and never actually post. [1]
  • The Chrome Disconnect: The issue was heavily tied to script execution errors on specific browsers (primarily Google Chrome). While alternative browsers like Microsoft Edge or Apple's Safari occasionally bypassed the bug, Chrome users were entirely locked out of interacting with comment sections. [1, 2]
  • The Behind-the-Scenes Fix: Because the problem was escalated directly to Google's engineering team by forum experts, a patch was pushed to their servers overnight. Once that patch fully propagated across Google's massive global network, the comment system "magically" went back to normal. [1, 2]
Should you do anything?
Since the fix was server-side, you don't need to change any settings on your dashboard. However, if you or any of your regular readers still experience a lag, doing a quick clear of your browser cache and cookies will force Chrome to load the newly patched version of the page. [1, 2, 3]
Are you missing any comments that were submitted while it was broken, or is your dashboard completely back to normal?

On Neo-Racism...

...born from an 'Excess' of Freedom
...Stop Oppressing Me, Man! Respect the Pronouns!

Thursday, September 3, 2026

When will Mamdani Enact the Jizya in NYC?

from Google AI:
Jizya is a historical per capita yearly tax levied by Islamic states on non-Muslim subjects, known as dhimmis. [1, 2]
Historical Purpose and Conditions
  • Protection and Rights: In return for paying the tax, non-Muslims (primarily Christians, Jews, and later Zoroastrians and others) received state protection, exemption from military service, and the right to practice their religion with communal autonomy. [1, 2]
  • Who Paid: Classical Islamic law generally required free, adult, sane, and financially able-bodied non-Muslim men to pay the jizya. [1, 2]
  • Exemptions: Women, children, the elderly, the poor, slaves, monks, and the mentally or physically ill were typically exempt. [1, 2]
  • Shifting Interpretations: While initially framed as a financial contribution for governance and safety, classical and medieval jurists increasingly interpreted or applied the tax in ways that marked a subordinate social and legal status for non-Muslims


Mamdani saying the "quiet part" out loud on the Jizya: 

  • "Shift the tax burden from overtaxed homeowners in the outer boroughs to more expensive homes in richer and whiter neighborhoods."
    (From his official housing policy campaign platform document.)
    [1]
  • "The use of that language is just an assessment of the neighborhood... I’m just naming things as they are."
    (Defending the platform's specific terminology during a Fox News Interview.)
    [1]
  • "That is just a description of what we see right now. It's not driven by race."
    (Responding on NBC's Meet the Press to criticism that the tax proposal was racially motivated.
     
  • If it wasn't racially motivated, then why say "white" neighborhoods at all? Why was it important to mention the racial demographics?  Sounds like what was intended was something akin to the "indirect" racial taxation methods being employed in South Africa.  In fact, it appears as if all "progressive" taxation  has been a de facto indirect racial tax all along.

     Is NYC the beginning of a New South Africa?