Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Everything I own, owned

schlarp.com

Post reply on HN
Print view View original

361–366 of 366 posts

Re: Everything I own, owned

#361

Post by MayeulC »

cromka wrote: post #328
MayeulC wrote: post #295

Earlier quoted context omitted.

Please make sure you fix the 3.3 V output if you get that device. Most revisions have a PCB layout issue that will output 5V even in 3.3 V, which has bricked stuff before. There are many ways to fix it, one trace cut and one jumper is how I did it. https://libreboot.org/docs/install/spi.html#do-not-buy-ch341...

I think all of them sold nowadays have this fixed but yes, absolutely worth checking.

The kit I bought 10 months ago had the issue. Luckily I was only unable to read some chips, and did not fry anything. Definitely check it before using it.

Re: Everything I own, owned

#362

Post by DiabloD3 »

radlad wrote: post #310
DiabloD3 wrote: post #277

Earlier quoted context omitted.

And thats why we have the warning that everyone bitches about: "Hey, the timer is up, but I'm not gonna make you do it, its just gonna wear the display out faster". Early OLEDs really did need to be pixel cleaned every 8 hours according to manufacturer estimates, the choice isn't have warning or not, its have a lifespan or not. I don't want to blame early adopters for being early adopters, but they early adopted, and…

I have an MSI OLED monitor, and if I accidentally turn it off (trying to find the input switcher), and then back on, it shows this warning. But it automatically runs when it's turned off. The warning is shown because I interrupted it running early. The warning, for my purposes, is completely useless, and only an annoyance. The automatic feature is more than enough, and I don't need to know if it was aborted early.

Then turn off the warning: all modern OLED monitors that do not force you to run it can both change when the timer fires, but also just disable the notification altogether.

This is what I have done on mine, and mine as well also runs it when its off.

If your monitor is a Samsung OLED panel, yours is a near identical sibling of mine.

Re: Everything I own, owned

#363

Post by DiabloD3 »

troupo wrote: post #297
DiabloD3 wrote: post #277

Earlier quoted context omitted.

And thats why we have the warning that everyone bitches about: "Hey, the timer is up, but I'm not gonna make you do it, its just gonna wear the display out faster". Early OLEDs really did need to be pixel cleaned every 8 hours according to manufacturer estimates, the choice isn't have warning or not, its have a lifespan or not. I don't want to blame early adopters for being early adopters, but they early adopted, and…

Because the run a full blown OSes on monitors now, and for some reason it cannot figure out the simple "wait until you're off for at least 10 minutes to do the cycle instead of bothering the user at random intervals"

They do run it when its off as well.

Re: Everything I own, owned

#364

Post by HDBaseT »

ryandrake wrote: post #117
ks2048 wrote: post #77

I can see the benefit of from-scratch personalized software, but in the spirit of open-source, how about all the world contributes to useful software for everyone else? Better than each person doing “4.2 hours of Claude churn, 32 prompts” for each device. And of course LLMs can help personalize existing things for your use case.

I'm starting to believe that bespoke, personalized software is the only way to combat feature bloat. Every software (proprietary or open source) I download and use has features I don't want getting in the way and bugs that the developers/maintainers are not prioritizing. I ended up vibe coding my own Android TV media player because every single other one out there has too much feature bloat and show stopping bugs. My…

A highly modular plugin system would solve this though. A great base product, with plugins (both community & official) which could expand feature sets.

Re: Everything I own, owned

#366

Post by SomeHacker44 »

trencedamp wrote: post #248
SomeHacker44 wrote: post #92

Earlier quoted context omitted.

Surprising. I have hit its BS guardrails a lot lately, working on my vintage computers from the 80s and early 90s. Just about done with Claude.

What were you trying to do with vintage computers?

In this case, get an ancient VAXstation running with VAX LISP so I could port my Z-machine interpreter from CLOS to their CLtL flavors implementation and try to get Zork and other games running on it. But goodness forbid you ask Claude for help with 35 year old software without hitting their guardrails.
Post reply on HN