• 0 Posts
  • 74 Comments
Joined 1 year ago
cake
Cake day: August 15th, 2024

help-circle



  • pixelscript@lemm.eetomemes@lemmy.worldAmerican measurements
    link
    fedilink
    English
    arrow-up
    3
    ·
    11 months ago

    Worse still, the pattern does not continue like one would expect.

    • Nominal: 2x4 – Actual: 1.5" x 3.5"
    • Nominal: 2x6 – Actual: 1.5" x 5.5"
    • Nominal: 2x8 – Actual: 1.5" x 7.25"
    • Nominal: 2x10 – Actual: 1.5" x 9.25"
    • Nominal: 2x12 – Actual: 1.5" x 11.25"

    There’s just an arbitrary point where they decided to take an extra 1/4" bite out of it. I’m not sure whether that’s more of an effect of shrinkage from kiln drying being proportional to the original length or an effect of industry practice to mill smaller boards to eke out more cuts per tree.

    And for the record, yes, I am aware the discrepancy is not entirely explained by shrinkage. They do a planing step after drying. But the shrinkage is a not insignificant part of it. They have to round down to the nearest convenient dimension from wherever the shrinkage stops.

    If longer boards shrink more, the finished boards would necessarily have to be smaller. I question whether that’s the effect at play, though, because I believe there was a phase in the industry where that extra quarter inch wasn’t taken off, and they changed their minds about it later.




  • I got a 1U rack server for free from a local business that was upgrading their entire fleet. Would’ve been e-waste otherwise, so they were happy to dump it off on me. I was excited to experiment with it.

    Until I got it home and found out it was as loud as a vacuum cleaner with all those fans. Oh, god no…

    I was living with my parents at the time, and they had a basement I could stick it in where its noise pollution was minimal. I mounted it up to a LackRack.

    Since moving out to a 1 bedroom apartment, I haven’t booted it. It’s just a 70 pound coffee table now. :/



  • I’m surprised I’ve yet to hear of a homebrew industry of completely cutting out the microcontrollers and soldering in a Pi or something to drive the raw display. I don’t predict it to be easy, but it doesn’t seem completely unobtainable?

    Flashing a custom bootloader would be even better, but I assume that hasn’t been done because they got that shit cryptographically locked down at the chip level.



  • Technically all you need is a DNS server.

    No computer knows where <whatever.tld> is located, unless that route is hard-coded in a host file somewhere. It always has to ask a DNS server for that information. If that DNS server doesn’t know, it will probably try asking some other DNS server, and so on up a chain. Eventually, it reaches a master DNS server that either has the answer on-hand somewhere in a database, or it says, “lmao, that doesn’t exist”. All the DNS servers and your PC down the chain take that answer. They might memorize it for a little while and hand it out to anyone who asks them, but after a while they’ll ask their way up the chain again to see if the answer has changed since the last time they asked.

    In order to “create” a TLD, all you have to do is make a DNS server that doesn’t ask up the chain. Just pre-program the list of valid domains yourself. You can make them anything you want. You can even “steal” existing domains and make them point to anywhere you want. Nothing is stopping you. Your DNS server will confidently report its pre-programmed answers to anyone who asks.

    The catch is that any Internet-enabled device that you want to be able to use your fancy new custom domains needs to be configured to ask your DNS server in particular. People would have to manually set your DNS server as their master server to ask, or they’d have to set it to ask some other DNS server that is itself pointed through some chain up to your DNS server. This is an explicitly opt-in system, and getting a significant mass of people to do that voluntarily is practically impossible. But it’s not technically impossible.

    The only reason you don’t have to do this manually with every single device you buy is because most devices either come from the manufacturer with a hard-coded list of DNS servers they should trust by default, or a device on the local network whispers in their ear and tells them who the local DNS server is and the device just goes along with it. It’s still technically an opt-in system; devices are simply either already “pre-opted in”, or there’s a system running on your network that auto-opts-in every device that connects, and most devices are designed to accept that auto-opt-in the moment they detect it.

    Provided you manage to get the devices you want to listen to your DNS server, you may additionally want to set up a root certificate authority. The thing that makes the little padlock show up in your browser URL box to let you know the connection is secure. Kind of like the DNS server thing, this is also very simple–just run a cheeky little OpenSSL command or two and you can be a root CA in no time–but it suffers from the same “opt-in” problem. You have to manually configure any device you want to use your system to trust your certificates. Most devices just come with a list of “acceptable authorities” built-in, and those defaults are all most people are using. But nothing is stopping you from adding anything you want to that list at any time. You’re just limited to doing it on a device-by-device basis.

    At my company, we’ve set up our own custom DNS server and our own root CA. We serve internal websites at a custom TLD we made up, and we sign them with our custom certificates to keep the connections secure. But that only works because we’ve manually configured our workstations to ask our internal DNS server for DNS requests, and we’ve manually configured all the workstations to trust our root certificate authority. A random device that connects to our network that isn’t configured with either of those things will not resolve any of our custom domains, nor will it securely connect to them. It also breaks if the configured devices aren’t on the local company network, since the DNS server isn’t reachable from the public web. Which is fine for us, since those internal websites aren’t reachable on the public web either. But yeah, that’s an example of the limitations.

    If you want to create a TLD that will be auto-accepted by everyone who is already running the default chains of trust (which is probably what most people actually mean when they ask something like this), you have to seek out the big daddy at the root of that chain of trust and ask them to poof your TLD into existence for you. That would be ICANN, and they probably won’t do anything like that without a big fat check and a lot of corporate lobbying.

    tl;dr - The tech is built in such a way that nothing is stopping you from making your own toy, and anyone can play with your toy without needing to do much. But if you want your TLD to “just work” for everyone in the world without asking every single one of them to explicitly opt-in, which is probably what you actually want, then no, you basically can’t do that.




  • There’s lots of software out there that is available to use without payment, but is still license restricted in such a way that you are not permitted to redistribute, modify, use for commercial purposes, etc. To many, these rights are the far more important facet of “free” software, above what it costs.

    But since the English language has the same word for all of these concepts, we have all these yucks running around with zero-cost but right-restricted software wearing the “FOSS” badge thinking they’re part of the club. So some people add “Libre” to the acronym to explicitly disambiguate.







  • pixelscript@lemm.eetomemes@lemmy.worldThere's a hierarchy
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    They are public drinking fountains. These aren’t meant to be put in homes or private spaces.

    America is absolutely filled with these things. They are everywhere. Public drinking access, no cups required, at an overwhelming number of public institutions. One of the extremely rare W’s of American public use infrastructure.

    On the few occasions I’ve been to Europe, I’ve honestly been quite frustrated at the lack of them. I can’t just roll up to a place and have a quick drink, I’m apparently just expected to carry it with me on my person when I leave my place of stay, or buy a disposable bottle of something from a shop. Even if there are public faucet taps available, I guess I’m expected to be carrying a drinking vessel already, or stick my face under the faucet and slurp awkwardly from the falling stream?

    I’m just baffled public drinking fountains don’t seem to be common elsewhere, to the point that there are several people in this thread questioning what they even are. I would consider them basic infrastructure for any civilized society.