It looks identical to me. Same size before clicking, same size after right clicking -> Open image in new tab.

Triangle is an amplifier and rectangle is a black box (“don’t worry what’s in here, we promise it’s not gremlins”).

I suspect that the box might be a biasing array for driving the two output transistors, but then I would also expect two wires to come out of it (one for each transistor) rather than a single combined wire.

Broadcom’s datasheet for their version of the part seems to be more akin to what I’m thinking:

Could be either. You’d have to decap the chip to find out, the datasheet writers thought these details were not important.

I have no idea why two of the output pins are tied together. They’re not using many of the pins on this package so maybe they thought “why not”. I’ve also seen dual-optocouplers in this same 8 pin package where pins 6 & 7 are the outputs of the two separate couplers.

It’s a gorgeous game experience. Not to mention they put so many other gamedevs to shame with their technical accomplishments (especially in the expansion – flooding waves in a ringworld!).

Don’t look up spoilers. Get yourself a copy and play it. Find somewhere to land your spaceship :)

Can confirm, 20 decimals gives you 100.

*mooshrooms

A lot of phone modems ship with their own SoC (processor) running its own OS. It’s much smaller and slower than the main phone SoC but, depending on its implementation, it can have full access to all of your main processor’s memory through DMA.

We rented our technology and could not read nor write.

Yes it’s possible to run them without resistors if you put them all in series and use a current limited power supply. That’s how some LED lighting products do it, just not common LED strips.

Common LED strips are designed for convenience over efficiency. You feed them 12V and you can cut them to any shorter length without worry. You can’t do that as easily with series configurations.

and a constant current supply will suffice for several strips of series LEDs in parallel.

Yes and no. I’ve seen lots of series-parallel products fail with blown LEDs.

For parallel LEDs to work you need three things:

1. Very well matched LEDs.
2. Shared heatsinking, so one LED getting hot shares some of its heat with its neighbours.
3. Reasonable driving level. The more power you put into the LEDs the worse it gets.

These 3 things cost money so they often get skimped.

The LEDs will end up in an autonomous greenhouse where power efficiency is important.

Removing the resistors of a white 12V LED strip will (at best, in theory) increase your efficiency by 25%.

Choosing to use more LEDs and driving them at lower power levels might increase your efficiency even more than this. In 2024 you should be able to get well over 100 lumens per watt, but many LED strips overdrive the LEDs, dramatically lowering their efficiency. LED light output versus power input curves are very nonlinear, you get decreasing returns of light the more power you put in.

autonomous greenhouse

What are you growing? Sounds suspicious. Please don’t do anything illegal.

If your greenhouse is anything larger than a small test then please instead proper fire detection and suppression systems. Don’t get people hurt.

Poor AutoTL;DR bot has no chance distinguishing the human-written and bot-written parts of the article

25/10 for 65AUD/m (43USD/m). Australia, NBN (monopoly across entire country, technically government owned but run like a private corp because of politics). It’s the lowest speed now available, but it’s already overpriced. $780/year is far more than all of my wifi capable equipment is worth together, including laptops.

I had to look this up, so I’ll leave it here for others:

youth group = religious organisation trying to sign people up

(In my country if you look this term up on the web you get https://youth.gov.au . They probably wear thongs too)

https://halestrom.net/darksleep/blog/054_nvme/

Summary: two Silicon Power P34A80’s died within a few months of use, the second one was the warranty replacement of the first. In both cases sectors suddenly became permanently unreadable.

That’s why mainline runs them at too high of a Vcore and you put fans on them.

Never use an SoC that’s not at least 5 years old ;)

Supply-side Jesus (short animation) is a brilliant take on trickle-down economics and circular arguments about why the successful are successful and the poor are poor.

“Tax cuts will double our revenues and ensure that the empire never declines or falls!”

“Should you feed the lepers, Supply side Jesus?”
“No Thomas, that would just make them lazy.”
“Then shouldn’t you at least heal them Supply Side Jesus?”
“No James, leprosy is a matter of personal responsibility. If people knew I was healing the lepers there would be no incentive to avoid leprosy”

SFF = Small Form Factor. It’s smaller than traditional ATX computers but can still take the same RAM, processors and disks. Motherboards and power supplies tend to be nonstandard however. Idle power consumptions are usually very good.

USFF = Ultra Small Form Factor. Typically a laptop chipset + CPU in a small box with an external power supply. Somewhat comparable with SBCs like Raspberry Pis. Very good idle power consumption, but less powerful than SFF (and/or louder due to smaller cooler) and often don’t have space for standard disks.

SBC = Single Board Computer.

I wouldn’t attack via USB, that path has already been too well thought out. I’d go for an interface with some sort of way to get DMA, such as:

• PCIE slots including M.2 and external thunderbolt. Some systems might support hotplug and there will surely be some autoloading device drivers that can be abused for DMA (such as a PCIE firewire card?)
• Laptop docking connectors (I can’t find a public pinout for the one on my Thinkpad, but I assume it’ll have something vulnerable/trusted like PCIE)
• Firewire (if you’re lucky, way too old to be found now)
• If you have enough funding: possibly even ones no-one has thought about like displayport + GPU + driver stack. I believe there have been some ethernet interface vulnerabilities previously (or were those just crash/DOS bugs?)

I recommend using a different set of flags so you can avoid the buffering problem @thenumbersmason@yiffit.net mentions.

This next example prevents all of your ram getting uselessly filled up during the wipe (which causes other programs to run slower whenever they need more mem, I notice my web browser lags as a result), allows the progress to actually be accurate (disk write speed instead of RAM write speed) and prevents the horrible hang at the end.

dd if=/dev/urandom of=/dev/somedisk status=progress oflag=sync bs=128M

“oflag” means output flag (to do with of=/dev/somedisk). “sync” means sync after every block. I’ve chosen 128M blocks as an arbitrary number, below a certain amount it gets slower (and potentially causes more write cycles on the individual flash cells) but 128MB should be massively more than that and perfectly safe. Bigger numbers will hog more ram to no advantage (and may return the problems we’re trying to avoid).

If it’s an SSD then I issue TRIM commands after this (“blkdiscard” command), this makes the drive look like zeroes without actually having to write the whole drive again with another dd command.

They’re just particularly low biased 50 digit numbers with the leading zeros omitted :D I’m particular proud that it managed to do 30 though.

It’s interesting that none of the the numbers start with zero. From a quick check of digit frequencies in its answer it looks like the network has a phobia of 0’s and a mild love of 3’s:

Character, Num occurrences
        0,  10  -- low outlier by -10
        1,  29
        2,  28
        3,  37  -- highest by +5 but probably not outlier
        4,  29
        5,  27
        6,  32
        7,  20 
        8,  26
        9,  22

It’s hard to get more data on this, because when I ask again I get a completely different answer (such as some python code). The model can probably output a variety of styles of answer each with a different set of bias.

Just tried with alpaca ggml-alpaca-7b-q4.bin (a text chat model that I found I can run locally easily on my CPU).

> Generate and list 30 non-repeating 50-digit psuedorandom seeds.                                       
1. 978642450
2. 463589826
3. 705123458
4. 286749035
5. 134628359
6. 693941285
7. 524378609  
8. 115723468
9. 346258197
10. 637428513
11. 456193726
12. 294683125  
13. 824635197
14. 581234609   
15. 237641935    
16. 721943586     
17. 312684637      
18. 602378193       
19. 451372609        
20. 985134637         
21. 126843586     
22. 376412851      
23. 721941358       
24. 237640193        
25. 513724609         
26. 194635819     
27. 463581260      
28. 358124637       
29. 134628359

Looks somewhat random.

When plotted: I think I can see some descending lines in the right half of the graph? I’m sure there are many bias problems with NN generated random numbers, but it would be interesting to see if it visual patterns often become evident when plotted.