this post was submitted on 12 Jan 2026
290 points (97.7% liked)

196

5233 readers
1610 users here now

Community Rules

You must post before you leave

Be nice. Assume others have good intent (within reason).

Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.

Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.

Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".

Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.

Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.

Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.

Avoid AI generated content.

Avoid misinformation.

Avoid incomprehensible posts.

No threats or personal attacks.

No spam.

Moderator Guidelines

Moderator Guidelines

  • Don’t be mean to users. Be gentle or neutral.
  • Most moderator actions which have a modlog message should include your username.
  • When in doubt about whether or not a user is problematic, send them a DM.
  • Don’t waste time debating/arguing with problematic users.
  • Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
  • Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
  • Ask the other mods for advice when things get complicated.
  • Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
  • Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
  • Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
  • Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
  • Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
  • First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
  • Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
  • No large decisions or actions without community input (polls or meta posts f.ex.).
  • Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
  • Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] ChaoticNeutralCzech@feddit.org 8 points 4 days ago* (last edited 3 days ago)

Tap into the button wiring in the control panel (if you're qualified!). Maybe you'll be able to type FF (hexadecimal) seconds, resulting in cooking time of 150+15=165 seconds!

Now seriously, a big portion of BCD (binary-counting-decimal) equipment is actually binary-to-hexadecimal but the counter is expected to reset before reaching A. Sometimes it doesn't:

https://www.youtube.com/watch?v=MvZgfj0_hJU&t=86

Another video, super compressed, by me, shot on a feature phone:
personal scale in st/lb mode goes up to A
You also see it go to 3 st 14 lb, which should not be possible because it's suppoded to show 4 st 0 lb at that point. (I use kilograms, I was just wondering what the switch in the battery compartment does.) I originally thought the ASIC inside would be a kind of microcontroller stripped down to what's needed: CPU (8- or even 4-bit, likely von Neumann) with a few registers (hard to call that RAM), (EE?)PROM for the program and calibration data (there's a pair of pins labeled "CAL" for a jumper or serial interface; I won't mess with them), 1:4 multiplexed LCD driver, digital input (not even GPIO) pins for the unit switch and calibration interface, differential amplifier and A/D converter, plus some support circuitry like an RC oscillator for the CPU clock, charge pump for the LCD, low battery voltage detector and sleep/wake circuit for power saving. This could enable the same ASIC to be used in personal and kitchen scales, maybe even pressure gauges, thermometers or more, just with a different program, LCD and external components. However, now I see that there is likely no CPU because doing the math in software would make such errors impossible. So there's most likely a hardwired logic system with hardware counters (just a little more complex than those cheap 3½-digit multimeters), binary-to-hex-7seg-digit converters and a flaky analog threshold system in the st:lb mode (the kg mode is a robust 1500-count decimal counter).