@bhtooefr

303 Followers
136 Following
12.1K Posts

Migrated to @bhtooefr.

Computing, transportation, energy... really anything interesting.

Webhttps://bhtooefr.org/
Alts@[email protected], @bhtooefr
Pronounshe/him

If you follow me here, I've moved to @[email protected] and will only use this account as a backup.

Please follow me over there!

If you follow me here, I've moved to @[email protected] and will only use this account as a backup.

Please follow me over there!

BTW, although follower import isn't working so I haven't actually followed anyone that I follow here over there, if you follow me, you probably want to follow me over at @[email protected]

idea for Fediverse software: timed mute

mute a user, but only for a certain time period, with customizable permeability (for instance, maybe allow them to directly reply to you, but not appear in your home timeline)

this way, when someone's being lewd as fuck and you're at work, you can mute them and not forget to unmute them when you're no longer at work

(yes this is a subpost)

(and the specific user I'm subposting has suggested another feature that could deal with this equally well before)

if you think people are making a conscious decision to not save enough to retire, I will invite you to look at the moldering corpse of "pensions" and suggest you hunt for the real killers
I'm going to shoot linkedin with a gun

OK

tbh it's slightly ridiculous that the easiest way for me to get a file into my OmniBook involves copying it to my file server, mounting it on my ThinkPad 365XD, copying from there to a PCMCIA card, and shoving that card in the OmniBook

I mean, I could've used Kermit or Xmodem or whatever, but ehh, easier to sneakernet it

you could set up some sort of quadrature pattern or something like that so that the chassis knows exactly where the beam is, and can adjust geometry on the fly to maintain perfect geometry

the only real problem that this can't directly correct for is issues with geometry blooming because of brightness variation, and there's ways you could detect that happening (basically run in overscan at varying power levels to see what happens to geometry in a calibration cycle), and possibly compensate

thought that I've probably shared somewhere before: a beam index/aperture grille hybrid CRT

the problem with beam index CRTs is that they have to constantly run a minimum beam energy to illuminate the internal UV phosphor, for proper beam indexing

but... what if you didn't use beam indexing for *color* at all, using something like an aperture grille or slot/shadow mask for color... and instead used beam indexing for *geometry*?

then, the beam only need be active in the overscan area.

And yes, I know, an upright bicycle would be better than the trike at the specific things that I complain the most about, while also being able to negotiate terrain that the scooter can't safely. (I do also have a folding upright bike...)

But, one interesting thing with the scooter is just how fluid it is to switch between riding at 25 km/h, and walking when needed. Even on a step-through bike, dismounting and remounting is much more of a conscious action, whereas on the scooter you just do it.