non-sense

https://github.com/processing/p5.js/wiki/Getting-started-with-WebGL-in-p5

why would you force everyone to use mostly negative z values everywhere? (the history of coordinate system choices for graphics is forever full of strange stuff.)

never forget

 #ODWALLAKILLEDPEOPLE

oh, i loathe steam

The short answer: Steam is warning you because something in your app’s configuration still counts as “changed but not submitted,” even if you already published a build. This usually happens when the store page or metadata has pending edits — not the build itself.

Below is a clear, practical breakdown of what causes this and how to fix it.

---

Why Steam says “This app has unpublished changes”

Steam distinguishes between content builds and store metadata. Publishing a build does not automatically publish store‑page changes.

The warning appears when any of the following still have unsent edits:

• Store page fields (description, screenshots, tags, categories, pricing, supported languages)
• Capsule images or other graphical assets
• Release settings (visibility, coming‑soon settings)
• Depots or build assignments not finalized in the Publish tab
• Package or pricing changes pending approval

Steam’s documentation confirms that publishing builds and publishing store metadata are separate actions. Steamworks

---

How to fix it (step‑by‑step)

Each item below starts with a Guided Link so you can jump directly into the next step if needed.

• Check the Publish tab — Go to Steamworks → Your App → Publish. Look for any section marked with a yellow warning icon. Even a single unconfirmed field will block publishing.
• Review store page sections — Open Store Page → Edit Store Page. Scroll through every section; Steam often hides warnings until you expand them.
• Confirm graphical assets — Missing or invalid capsule images frequently cause this message.
• Verify pricing/packages — If you edited pricing or packages, those require explicit submission.
• Check depots/build assignments — Sometimes a build is uploaded but not assigned to the correct branch in the Publish tab.
• Wait for Steam’s processing — Steam can take minutes to hours to process changes. Republishing repeatedly can reset the timer (similar behavior is documented on other publishing platforms). kdpcommunity.com

---

Non‑obvious causes (these catch many devs)

• A single language version of the store page is incomplete
  Example: English is complete, but Spanish has a missing field.
• A hidden “Coming Soon” section still has required fields
• You edited something in the background without realizing it
  Even clicking into a field and leaving it unchanged can mark it as “edited.”
• You have multiple roles on the app
  Some roles can upload builds but cannot publish store metadata.

---

Quick diagnostic checklist

Use these Guided Links to jump to the relevant checks:

• Is the store page fully approved?
• Are all assets validated?
• Is the build assigned to the correct branch?
• Are there pricing/package changes pending?

---

If everything looks published but the warning persists

This happens occasionally due to Steamworks caching.

Try:

• Clear the Publish tab by toggling a field
  Change a field (e.g., add a space), save, remove the space, save again.
• Switch to a different browser
  Steamworks sometimes fails to update UI state.
• Ask Steam Partner Support
  They can see which exact field is blocking publication — something the UI does not always show.

---

Want me to help you pinpoint the exact cause?

If you tell me:

• Whether the warning appears on the Store Page, Publish tab, or Builds page
• Whether you recently changed pricing, assets, or languages
• Whether your app is released, coming soon, or unreleased

…I can walk you through the exact place to look.

Which part of Steamworks is showing the warning — the Store Page editor, the Publish tab, or the Builds page?

fumb ducks

> Your Google Pixel Android system update may pause due to sleep settings or battery-saving features, which limit background activity. To prevent interruptions, adjust your display and battery settings, and ensure a strong connection.

hang the DJ

 fuck the user

fuck the user

fuck the user

fuck the user

fuck the user fuck the user fuck the user

fuck the user fuck the user fuck the user

fuck the user

fuck the user

git ux sucks

news at 11

the core idea might be ok, heaven knows it has won out, but the ux kills me every other day.

https://joseph-fox.co.uk/tech/git-ours-theirs-explained

all is full of shyte

pretty much everything online about ecommerce is dog shyte ui ux.

trying to ship a used computer monitor. 

freaking nightmare of stupidities.

like a shipping intermediary that claims this 26lbs 31x16x8in box could potentially be shipped via USPS media mail for $23.22

just blatant outright transparently stupid-rock-dumb. 

oh and they somehow broke the most basic parts of gui in a web browser, too.

oh and are full of random bugs and unresponsive ui.

"shipstation" more like "shytestation" if you know what i mean.

 let alone the superweasel terms and conditions.

pirateship sucks. easyship sucks. 

c'est la vie.