I once met a person that never drank water, only soft drinks. It’s not the unhealthiness of this that disturbed me, but the fact they did it without the requisite paperwork.

Unlike those disorganised people I have a formal waiver. I primarily drink steam and crushed glaciers.

  • 8 Posts
  • 198 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle



  • plus a phosphorus layer on top that smooths those two perfect lightwave color peaks in the wavelength domain into a broader light spectrum

    The phosphor absorbs some of the blue and downconverts it to green and red. Some of the blue is let through for us to see. The mixture of R, G and B looks like white to us (but not necessarily to other animals with different cones in their eyes).

    2 kinds of light emiting diode (LED) junctions inside - red and blue

    I’ve never seen a red LED die inside a white LED. I’ve only ever seen blue dies on their own.

    Technically UV-pumped white LEDs exist, but they’re rare and I’ve never seen one. They’re less efficient and require a third phosphor (to make the blue).

    You can remove the yellowish looking phosphors on the LED with a small pick to reveal the blue die underneath. Fun fact: some high-power “red” LEDs are actually blue leds + phosphors, not that it’s a particularly good choice but it’s a thing: https://halestrom.net/darksleep/blog/018_led_cob_cutting/



  • Something to be wary of when interpreting the datasheet:

    • Act10 = LED blinking when Ethernet packets transmitted/received at 10Mbps.
    • Act100 = …
    • Act1000 = …

    Bad wording on their part. What they really mean is: “LED blinking when Ethernet packets transmitted/received AND the link is currently in a XYZMbps link speed mode”. The mode is negotiated once after you plug a cable in and usually does not change after that, regardless of how much data you try to send.

    Technically each linkspeed/mode is a whole ethernet standard of its own, but we mostly gloss over that and pretend to end users that they’re backwards compatible.



  • WaterWaiver@aussie.zonetoSelfhosted@lemmy.worldOpenWRT router
    link
    fedilink
    English
    arrow-up
    29
    ·
    edit-2
    3 months ago

    Thing is, its EOL, per Asus. Does this mean that it won’t be supported on OpenWRT for much longer?

    OpenWRT tends to support devices longer and better than the OEM, but it depends on the popularity of the chipset inside the router.

    Many different routers by different companies are almost identical internally, because they use the same chipset. Eg the RT-AC3100 seems to be a bcm53xx variant, of which OpenWRT supports a few dozen products. Support will probably only be dropped when every single one of those devices goes EOL and several years pass (ie no people left contributing/maintaining it and the builds break somehow).

    Router chipsets can be very long lived. Many new devices use decade old chipset designs. Some chipset families have almost identical chips released every few years with slightly different peripherals, clocks & pinouts; but are supported by the same kernel drivers.

    (This is all much better than the world of mobile phone hardware support. Maybe it’s because of different market pressures? Not to mention you don’t have a monopoly that benefits from keeping the hardware fractured. Imagine if people could make a competitor to Android that works across most devices out there)



  • WaterWaiver@aussie.zonetoSelfhosted@lemmy.worldWireguard over IPv6
    link
    fedilink
    English
    arrow-up
    37
    ·
    edit-2
    4 months ago

    As far as I understand, wireguard is designed so that it can’t be portscanned. Replies are never sent to packets unless they pass full auth.

    This is both a blessing and a curse. It unfortunately means that if you misconfigure a key then your packets get silently ignored by the other party, no error messages or the likes, it’s as if the other party doesn’t exist.

    EDIT: Yep, as per https://www.wireguard.com/protocol/

    In fact, the server does not even respond at all to an unauthorized client; it is silent and invisible.






  • WaterWaiver@aussie.zonetoRetroGaming@lemmy.worldBuilt to last
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    6 months ago

    Ty. Sorry it was a grumpy warning :(

    From memory, it felt like the electrostatic discharge that used to happen whenever I was touching my car.

    That’s likely a valid comparison. Some parts of the tube might give you the same style of event as static electricity discharge when you touch them. Other parts would give you something more though :D so please don’t take this as a generalisation.

    Interestingly, the PC suffered no damage at all and didn’t blow its internal fuse, either.

    Fuses are OK as fire prevention devices, but mostly useless as electrocution prevention. They blow based off power draw and time. Many human-electric interactions don’t actually draw that much power or last that long when compared to normal circuit power draws & timescales.


  • WaterWaiver@aussie.zonetoRetroGaming@lemmy.worldBuilt to last
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    6 months ago

    Thankfully, it must have been all volts and no amps so I was OK, even though I let out quite the yelp. 😁

    Complete myth. Please don’t repeat this. It’s not even remotely close to a generalisation, it’s completely wrong and dangerous.

    (Sorry, pet peeve of mine. Have had family members happy to play with mains wires but terrified to touch car batteries for fear of death)

    100mA through someone can be harmless. 1mA through someone can be fatal. Lethal conditions occur under certain complex circumstances involving not just voltage/current, but frequency, exact waveforms, duration, contact points and the individual’s physical parameters (human skin resistance varies a LOT, it’s not an insignificant factor).

    The most commonly encountered electrical hazards involve 50/60Hz 120/230V mains and hand/foot dermal contacts. This is a lethal combination that can cause heart fibrillation. Even 5mA or 100VAC can cause this (sometimes you will see lower numbers cited, “it depends”). Death can occur a day later, see immediate medical attention if you believe you have been shocked by mains wiring.

    At very high frequencies our nervous system is not sensitive, so we can pass larger amounts of current or deal with higher voltages without much harm. I’ll still hedge this with “it depends”, you can get thermal burns (which if on the eyes includes blindness) and pathways through the body vary with contact points, changing the risks.

    Static electricity discharges can be crazily high voltages and currents (many amps, sometimes hundreds of amps). Yet they are not a hazard.

    The high voltages in your CRT will supply very high currents when applied to dermal contact points on the human body. This will likely induce involuntary muscle contraction. Prolonged contact could cause burns and unwanted chemical reactions to occur internally, but is unlikely to cause heart fibrillation because of the non-repeating DC nature.


  • WaterWaiver@aussie.zonetoRetroGaming@lemmy.worldBuilt to last
    link
    fedilink
    English
    arrow-up
    20
    ·
    edit-2
    6 months ago

    I was young and did not have access to soldering irons. So I bridged the two pins with aluminium foil and sticky tape.

    It would slowly peel off and my controller would suddenly stop working mid game. I couldn’t reboot the console because I couldn’t save (no VMUs). So I’d fix it live – I’d leave the screws out of the case, jiggle my fingers in there and fix it.

    This was fine, worked for most of a year. Until I killed the console by accidentally touching the controller PCB to another PCB whilst doing this fix. I still have the corpse somewhere, to this day I still feel awful about it.



  • WaterWaiver@aussie.zonetolinuxmemes@lemmy.worldWe have POSIX at home
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    7 months ago

    If something is POSIX compliant then it’s very likely to work on any Linux, BSD or the like; and probably very easy to port to windows. It’s a sign that the developer is willing to go the extra mile to make users’ lives easier.

    N.B. “POSIX compliance” is not just considered in black or white terms, it’s also done in degrees. There are many things that have never formally been changed or been specified in POSIX but informally things have evolved. By attempting any level of compliance (or a similar equivalent) you tend to be doing better than most software.