• 0 Posts
  • 112 Comments
Joined 6 months ago
cake
Cake day: August 15th, 2024

help-circle

  • I feel like the “we don’t know what this function does” meme is kinda bad. There’s no reason beyond maybe time crunch why you shouldn’t be able to dissect exactly what it does.

    Despite this, the notion of a load-bearing function is still very relevant. Yeah, sure, you know what it does, including all of the little edge case behaviors it has. But you can’t at this time fully ascertain what’s calling it, and how all the callers have become dependant on all the little idiosyncracies that will break if you refactor it to something more sensible.

    It has been several times now where a part of my system of legacy code broke in some novel fantastic way, because two wrongs were cancelling out and then I fixed only one of them.




  • It’s not clear at all, no.

    Is this proposal patently ridiculous? Yes. Do I believe there’s at least one legislator in Mississippi who unironically believes in this bill exactly as written, and is playing this completely straight? Considering all that’s happened so far, why not?

    Satire doesn’t work when the obvious hyperbolic nonsense is within actual expected behavior of the satirized.

    I won’t claim one way or the other that this is or is not satire. I don’t know who this legislator is and I don’t really care. But no, with the whole article you’re pasting everywhere in this thread as my only context clue, I certainly didn’t find enough evidence to be convinced he doesn’t actually believe this.









  • Of the people who say anything about it, there seems to be two mutually exclusive camps of people on Lemmy in regards to how it should be structured.

    There’s those who want it to be a drop-in replacement for whatever platform they migrated from (Reddit, ususally), with everything cultured in one simple, easy-to-browse place where there’s enough activity to support diversity, just without the enshittification, even though the centralization they crave is exactly what invites the enshittification…

    …and then there’s those who specifically want the site to stay fragmented, because that’s the whole point of federation, it keeps out all the riff raff, and prevents the platform from losing what makes it so great. But many of them complain about why it isn’t growing as fast as they’d like it to, despite the fact that the fragmentation of community is by far the single greatest barrier preventing the mass adoption they yearn for.

    Each one seems to want a piece of what the other has.


  • 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.




  • I assume the reflowing solder in the oven trick doesn’t reliably work anymore in the era of the high temp solders that are common in laptop manufacturing these days. Bringing the whole board up to flow temp in something as crude as a home oven is almost certainly going to fuck something else on the board.

    I recall trying to do a laptop repair with dinky little soldering iron I got at the hardware store and it could not melt a single thing on the board I touched it to. Definitely not a faulty iron because I used it to successfully solder other things. This was at least five years ago. If that little toy couldn’t do it, then the entire board would need to exceed that temp in an oven, which is probably a bad idea since the iron was still managing to visibly scorch things despite not melting any solder.

    Invest in a proper heat gun and learn how to use it, or just give up and give it to someone else who has one, imo.


  • It’s not states blocking porn sites. It’s states treating porn site companies similarly to bars. “If we catch you serving minors, we’re gonna sue the shit out of you.”

    The only legally airtight way to know you’re not serving minors is to check valid IDs for every visitor. Just like a bar. But since doing that for a website is a huge burden and still a tremendous risk, companies like Pornhub aren’t playing ball. Instead of complying with the new laws, they’re simply choosing to refuse service to any user from one of these hostile states. Can’t get in trouble for serving minors from certain states if you don’t serve anyone from those states at all.


  • 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.