archi42

Ah, yes, common people and cryptography. I've recently been in a meeting with industrial people, the topic was securing industrial communication in production lines and such stuff: "Someone told us zero trust means we can establish secure communications between random devices without any root of trust". I think they plan to eventually standardize something around that. I'm looking forward to either be pleasantly surprised, or do a side quest to prevent them from making fools of themselves.

The future is now: Modern houses around here often feature a "Ventilation system with heat recovery": You get fresh air that's heated using the air it replaces. And just let the system run 24/7. You can also recover/regulate humidity.

These systems can sometimes be retrofit into older buildings (we're doing that for our 1950s SFH), but the necessary piping is often labor intensive to install and hence prices can be insane (we were able to combine it with other measures and significantly reduced costs - I installed pipes while the roof was removed). It's much easier for new buildings of course.

> Comparing Bambu to Voron is an absurd comparison

I politely disagree. I was in the market for a more modern printer, and it boiled down to either a BL or a Voron - in the end I decided against ease of use and in favor of an open ecosystem. I agree in that they are not universally interchangeable, but for some people either can be an option, each with distinctive advantages and disadvantages.

For some it's just a beloved ritual and shared experience :-)

I've certainly seen it at least as many times sober as I have seen it drunk. First as a kid of course, but also now that I'm older (even though we have no kids and no other requirement not to drink). I have to admit it's funnier while enjoying a nice drink, though ;-)

How do you manage heat? I'm looking at a hashcat build with a few 5090, and water cooling seems to be the sensible solution if we scale beyond two cards.

This reads as if you did multiple API calls per "ping", and opened a new http connection for each API call?

Did you try reusing the http connection (one per ping)? How about putting all data in a single API call and let the server handle that?

Did you try compression? Not sure if compression makes sense, but a simple+fast compression like gzip could also be worth a try to reduce the actual bytes to put on the air; especially if your data is very verbose or repetitive. (Do that before connecting to wifi, even if that means not using http's compression).

I suppose you're talking http, not https. The latter will of course use much more energy.

Using UDP and the ensuring TCP-like qualities seems like a last resort solution.

Sorry if I misread your article and the suggestion were tried or are not feasible for you.

Uh, even the 3080ti had 12GB RAM; in that generation only the 3090 had more (24GB). The 2080 had 8GB.

Just a nitpick; the guess is sound (though I would expect 4GB to stay for the office PC market), and obviously only time will tell what they'll really be doing.

OTOH don't underestimate the power of artificial market segmentation - "oh, you want 16GB VRAM? Too bad, get a xx60 instead of a xx50. After all it's just 25% more expensive!".

That's security theater. Some decision makers want to "see" it's secure, so that's what some "security" people sell. If I was doing consultation for your employer, I'd tell them that's insane and that they will only push people to circumvent security instead of embracing it.

Others made good points, a decent SSO is the way to go.

(Ironically we also have an internal system that's equally degenerate and mostly a shitload of useless theater; it's secure of course, but there are a few pointless layers stacked on top of what makes it actually secure)

Inertia is stored energy. To emulate an energy storage, you need to be able to get energy from "somewhere". That's just physics. Plus, it works both ways: If there is excess power, you also need to dissipate power from the grid.

But an individual solar inverter fluctuates wildly, and has no significant amount of energy stored (e.g. in capacitors). It also has no place to put power (okay, you can put it in the PV panels to produce heat, but they won't like that during a hot summer day).

That's why they are using batteries to emulate inertia: They are energy storage, and thus can act like inertia. Both putting energy into the system and "removing" it. The power industry is slow moving, so we're only seeing it now.

(Not an EE, but I think the reasoning is sound. Proper EEs feel free to teach me)

Contacts are just a toy example, aren't they?

Else this is a privacy nightmare waiting to happen: It's easy to accidentially share numbers. Also it might turn out your new friend J. is superficially pleasant, but actually a horrible human being once you get to know them - congratulations, J. has access to all your shared contacts. If I was friends with Alice, I'd be very annoyed that J. is now harassing me.

Or suppose you created a list of all doctor's phone numbers in your area. You can then look up if any of your contacts (friends, family, loose aquintance) share any of them (e.g. because they recommended a specialist to a friend).

This needs a tremendous work to setup access rights, and it's easy for an individual to screw this up and put themselves in a bad spot.

Sharing contacts on a need-to-know basis (using e.g. Threema or WhatsApp) is the established standard in my peer group; be it the number of a Pizza place or my SO's new number, so a common friend can invite her to a party. And while it's less cool and adds some effort, it requires an explicit action to share a contact. This is more safe.

In my humble opinion, and I might have a bad hunch there: The overall mistake with that example is lies in how it associates identities with phone numbers. In reality, it's the other way around. We want to share identities (be it the Pizza Place, Mum, or a doctor), and should have control who can access the information (not just phone numbers) associated with them. But that's essentially re-inventing social networks with a narrow focus.

From a academical perspective the technical issue can be interesting of course, and valuable insights might be gained from this research. There might be use cases beyond the basic contacts example; in fact, I think in a company phone directory this can be incredibly useful as part of the CRM.

Regarding little differences: Sometimes(!) hits on the crash cymbals sound "wrong". Since compression is pretty good, most of the time it sounds fine though. Plus, in other instances that's just how it was recorded/sampled.

So it's not a good indicator for your test (and I wouldn't dare claim what your audiophile friends claimed). But in a few cases a "wrong" sound cymbal can actually caused by compression.

But I sit down to listen to music as a hobby (and used to play drums, so I listen closely to them). And while I don't have audiophile-grade snake oil, I have both decent headphones and speakers; including the electronics.

Would you care to elaborate? It also matters what counts as "bad password manager" to you - Poor crypto? Poor UX? A reddit post ;-)? LastPass?

With passkeys, both the website and the user can be pretty sure that the "password" is secure. The website knows that it's based on enough entropy, and the user knows that the website can not loose it.

Of course if I use a random generated 80 char password I only mildly care if the website stores it plain text or not.

But if I was a site operator, I could additionally trust that the users are using secure passwords. Without insane strength requirements (which people only work around anyway, e.g. Passw0rd!123 is usually accepted, but thisisasuperlongpassphrase often is not).

I'm in the business of testing security, which means I sometimes crack passwords. No matter how much training you put your employees through: Somebody gonna use ${some name}${0 or 1 special char}${some birthday} - is it's the spouse, kids or affairs data, your guess is as good as mine.

There are normal people out there who have been hacked, or knew someone who was.

Also, some normal people are computer-smart enough to understand problems like credential-stuffing, if someone explains it to them.

What are the equivalent VR games? Just curious.

I don't play too much VR these days, but enjoyed Beat Saber for "stationary movement", Gorn for beating up stuff and the VR ports of the original Serious Sam games for "run and shoot like a maniac".

For those not familiar with how this works/worked: At most universities, a similar fee was collected from all students. That was then used to finance a regional "public transport flatrate".

N.b.: mk89 is technically not quite correct, it wasn't free (nothing in life is). It's usually bundled with the tuition/enrollment fee.

Implementation details differed per University, but for us the fee (80 or 100€, can't recall) was socialized across all students and payed together with the tuition fee; opting out was not possible (with some exceptions, like disabilities). The money went from the University administration to the AStA - the "general students council" (the executive section of the elected student self-government). The AStA then negotiated with the local public transport company/companies as well as with the Deutsche Bahn (e.g. to get access to certain inter-regional train connections - we still have cooperations with 3 or 4 nearby universities, and students somehow need to get there). Those negotiations can be a royal pita, and often the students were in a weak position.

Source: I was in the AStA (~12 people), but not involved with that task.

A router you can flash with a modern OpenWRT is likely a good option. Check the project website and/or forums and/or reddit for recent recommendations. That's what I did in the past.

Personally I've moved to OpnSense: Some run it natively on a refurbished low-power SFF hardware (6000 or 7000 series Intel should be fine, or some Ryzen), so even in countries with high electricity costs that's feasible these days.

More specifically, I run OpnSense in a qemu/libvirt VM (2C of a E5-2690v4) and do WiFi with a popular prosumer APs. Mind that VMs are likely to introduce latency, so if you try this route, make sure to PCIe-passthrough your network devices to the VM - I was prepared to ditch the VM for a dedicated SFF.

I would love that, but I can see some issues: Embedded stuff (e.g. in your car) might use a proprietary RTOS, like "VxWorks" [1]. Then the developers might had to use a commercial toolchain from e.g. Hightec [2]. They could also have licensed some 3rd party libs. What about external verification tools for critical stuff? What about cloud-connected services (e.g. music streaming)?

For a manufacturer to opensource "all that's necessary to build, deploy and use the soft-/hardware", the whole ecosystem would need a massive paradigm shift.

For certain device classes this is probably much easier than for others. And expecting/dictating a reasonable lifetime from a product might be the better choice - and as the EU directive regarding user-replacable smartphone batteries shows, this goes beyond software.

[1] https://en.wikipedia.org/wiki/VxWorks [2] https://hightec-rt.com/products/development-platform

A quick Google search suggests that in the US, you're on the hook.

Not only tech... I live close to the French border. My wife asked me to go to some criminal dinner event thing in France, and all the leaflets and the website were English. Great! Checking out the details, a small remark in a table with the dates and such catches my eye "Language: French". Well, maybe that's the French date,... Nope, that's for all scheduled events. Kthxbye. At least we were not surprised on site, because my French c'est no bene.

Not all that glitters is gold. I had a horrible experience with Hollow Knight on the Switch and can't understand how anyone would enjoy that game on that console. I did a video recording and the lag playing on the console screen was easily in the 100ms (iirc; can't find it).

From what I read on Reddit, there are some people who don't notice any lag (even in the aforementioned HK), others notice it in most games. For me, even the Zelda titles have some lag (though these I play on the TV, so it's a bit unfair).

For my part, I'll stick to PC; even if it means crying a little bit on each upgrade. And that's coming from the guy who used to often game at 25fps as a kid; and still enjoys playing the odd couch game (with friends) via wired Steam inhome streaming.

If you (or others) are happy with their experience, that's fine of course ;)

Depends on your definition of beginner. It's trivial to put a nrf52 module (like [1]) in a PCB design and wire a USB socket to it; just make sure to route the data lines as a differential pair in kicad (add protection diodes if feeling fancy). And speak a little prayer that it actually works as intended. No need to understand what any of that means.

Of course the notion of using such a module might be a step up from beginner for you, but IMHO it's more about the understanding. But I agree that there is no definite definition.

Disclaimer: I'm a beginner by my definition.

[1] example module: https://www.waveshare.com/core52840.htm

Seems the content is blurred for a few seconds (or until scrolling over it?).

I get the joke and think it's funny, but also found that it might miss the mark by confusing people. Maybe they should have done it for the first paragraph only.

Edit: The timing seems to depend on their page/CDN load speed.

Edit 2: On Desktop, with a hot cache, it's blurred for about 500ms. I only tried a few times, but cold cache can be as much as 5s. While it don't like parent's "tone" (as did many others, considering it's flagged now), I get the confusion.

TYDUI (IMTOU) - Then You Don't Understand It (I Made That One Up) ;-)

It's an abbreviation, and you're one of today's lucky 10000 - https://xkcd.com/1053/ for an explanation of the 10000 phrase.

Thanks for agreeing :) safety also protects against preventable human errors.

Maybe my examples are bording on sabotage, eg "sabotage by accident".

See my reply to sibling comment: if you're thinking safety is purely PvE, you're in for a bad time.

Humans are reckless idiots. If circumventing safety systems means they can go home 15 minutes earlier (or if it's the only/simplest easy to get reach some unrealistic high daily goal dictated from higher ups), some of us will happily risk their own health, and that of a whole city, to do so.

Safety is not really about reliability. Maybe as a means to an end. It's about not killing people and maybe not destroying too much of your facility in case things go south.

Safety systems take over if your chemical reaction overheats the reactor; they prevent your logistics team from moving a train while it's being loaded with dangerous chemicals (real example, the safety system was disabled by the logistics people - ironically the company put those with poor safety record from production to logistics, because they could do no harm there).

You're mixing up safety systems with the property of "doing X is safe by construction" - but most plants inherently are not: e.g. in a small reactor that's manually fed, your employees can just input the wrong recipe by accident; the safety systems should then take care of the mess. Or your junior chemist (who needs an expensive, senior chemist for an established process?) can mess up the improvement to the recipe, resulting in rapid unscheduled disassembly of you poorly maintained reactor, including the building and one of its operators (sadly a real example).

They're related, but they're not the same thing: E.g. when analysing a JS-like language and you see "x = a + b" with raw memory content a = {0x1,0x2}, b = {0x3} you get x = {0x4,0x5,0x13,0x23} - because you can't tell if that + is a string concatenation or numerical addition.

Of course when analysing program code, you might want to carry type information with you. The math behind AI allows to combine basically any domain to a single domain without losing all the nice properties of the Galois connection. But usually you get away with tracking multiple domains simultaneously, since that's also a lot easier from an engineering perspective (someone has to understand and maintain that code for a few decades).

Edit: I recommend following funcDropShadow's advice.

I hate the app+cloud garbage as much as you, but have you considered how a VCR would be programmed today? Take your universal touchscreen device out of your pocket, select the VCR app, get a list of programms for the next weeks, touch the one you want to record (or do a full text search), select if you want to record this episode, all, or a certain set.

In the past, you needed to first buy this weeks TV magazine. Or if you got it by mail, find it between all the other magazines. Then, skip all the ads and find the schedule, in there find the program you're looking for. Now you either need to figure out the exact time slot the program airs, or some EPG code. This data now needs to be entered into the VCR. Either find the remote, or knee in front of the device. Enter the code using a rotary encoder, digits 0-9 and a few buttons, or a mixture thereof.

In both cases you need to set the receiver to the correct program before leaving the house, else the SCART-connected VCR wouldn't get the video signal. Also you'd need to hope the EPG sent by the station is updated properly - we often had some part of the recording missing, or the recording started to soon/stopped to late. I hope you did put in the correct tape and remembered to rewind it. (I'm ignoring that a modern "VCR" would store the video in the cloud and not need all of this; or a hybrid would at least get the video stream via IPTV and put it on a HDD).

Try speaking to other humans about this topic, they don't want these "good old times" back.

Also, apps suck because they are mostly always horribly made (they don't need be, but they often are, because the product needs to be cheap); and I hate being forced to use the cloud and have my hardware not work anymore after 5 years because someone decided their Amazon bill is becoming too expensive. Did I mention I don't want my data to be sold to virtually everyone - errr, I mean "shared with partners"? So I either buy things with local control, or no smarts at all.

I disagree. DLP resin printers use what can be described essentially as a UV beamer. The DLP IC is called DMD - digital micromirror device. It is what it says, and contains lots of micromirror that can direct the light. The resulting image projected onto the FEP film on the resin vat is quite sharp. They also require little power without affecting the exposure time.

Normal resin printers use a UV LED array with lenses to produce a more or less uniform light field. A display is then stuck underneath the vat to block light at certain spots. Since there is some distance between the display and the resin inside the vat, the resulting image has a slight blur on the edges; I think isn't an issue and is countered by using high resolution displays.

However, they consume a lot more power and require active cooling.

The display on a LCD resin printer has a limited lifetime, while the DLP is rated for 20000h. Being able to focus the image on the resin also allows for using arbitrarily thick (and thus stable) glas plates, while on a LCD the distance between LCD and resin needs to be minimzed.

Mind we're talking about a device that costs 4500US$ (before taxes).

Or am I missing some good reason to use a LCD display over a DMD in that device class?

Since Formlabs position themselves at the higher end, I was surprised they didn't skip LCDs and went straight to DLP.

PDF from TI from 2019, though I think they have updated their line up since: https://www.ti.com/lit/sl/dlpt019e/dlpt019e.pdf