osaerisxero

I was under the impression the programmer socks were compulsory for anything requiring you to compile your own kernel

The critical thing you’re going to want to keep in mind for ethernet wiring is getting everything wired back to a central location is key, and spending the extra time and effort to do home runs instead of having multiple junctions can save you a lot of headaches down the line. That being said, you can run more than line at the same time.

For where to start, deciding where you’re pathing to and how you’re getting there is what you want to focus on. If there’s no existing ethernet, what about existing fiber coming into? Or is there a central block where all the RG59/6 terminates? Even just a nice shelf near the furnace can be fine if the furnace doesn’t cook the room its in. Is there a crawlspace or attic where you can run all the wiring through?

Getting answers to those questions are where I would start. I would suggest though that retrofitting ethernet wiring is a project that you might be better off waiting on until you’re also doing other work in the space(s), and you can get away with a lot just using low profile cables and tacking them around doorframes apartment-style in the short to medium term until you’re ready to do it all at once and/or need to do related work (like if part of the building’s power lines need to be replaced or you decide to get new flooring or whatever).

EDIT: Well, my notifications went rogue and said this was a new thread lol. Leaving the above anyway.

Specifically B is the standard. Edit: the Wikipedia article has a more complete explanation as to why, but you should always wire to B unless you have an explicit reason to do otherwise.

I believe it is traditional to do so written in blood in the style of an apocalypse log, dealer’s choice for who’s blood. Make sure it’s disjointed and nearly incomprehensible, but that everything is there.

Bonus points if you print the config files and write your documentation on them after stapling them to the walls

Listen here you little shit

edit: WHICH ONE OF YOU FUCKING MEMELORD FOUND MY ADDRESS AND SENT ME THIGH HIGHS AND CAT EARS?

Ok but how did they fit tho

Also do you have enough paper for the entire bee movie script.

Asking for a friend.

Ironically, that’s probably what’s needed to get the yapping started. With the fediverse being what it is, there’s lots of highly technical people kicking around (networking people included), but little need for us to be posting stuff about it unless it’s time to shit talk HPE again or something.

Most people don’t have a RAID to fall back on either, and I would argue most cars’ donuts or spares haven’t been checked since the car was new so I think it holds up better than you’re giving it credit for lol

This only guarantees your WANip:8100 will map to 192.168.0.113:81, and doesn’t address whether or not dns resolution is correct. I would also be weary of using port numbers on wikipedia’s known ports list, as some ISPs will filter those upstream. The last thing is that your router may not want to hairpin that traffic, so if you’re not coming in from the outside it might not be a valid test.

This is likely correct but the browser’s errors should be telling you what the error(s) is/are.

Lol, I think we might be closer than you think. Lemmy and reddit are both basically unusable in web form on mobile, but Ernest took the time to make the layout of kbin in such a way that it compresses down to a PWA/Mobile layout without becoming a complete clusterfuck, something the mbin maintainers have maintained support for and I think is one of the key distinguishing features of the platform. The way it works feels very similar to the old RIF layout, and as such was everything I wanted from a reddit replacement from day one :)

+1 for the kbin >>mbin pipeline. I like that it still has pwa support since I really don’t need a phone app for a text based forum

Common valve W

This, but with the asterisk of Bluetooth sometimes not recovering gracefully from soft updates