shadoxx · HackerTrans

2 ปีที่แล้วdiscuss

I've noticed this as well, across pretty much all of social media that I use. I can't quite place my finger on it, whether it's just a reflection of the state of the collective feelings of people, or if it's mass manipulation. At this point it could be both.

shadoxx

2 ปีที่แล้วdiscuss

Auto-reverse means Auto RDNS zone creation. Where you're usually trying to translate hostnames to ip addresses, a reverse lookup translates an ip address to a hostname.

So, if I have an internal record, record.example.com @ 192.168.1.2, I can query the server to ask "Hey, who is at 192.168.1.2?" and the server would reply with "record.example.com". This works by creating not only the example.com zone, but also a "1.168.192.in-addr.arpa" zone with the proper mappings. Technitium server will ask you to create the zone if it doesn't already exist when you create an A record for a zone.

https://knowledge.digicert.com/constellix/standard-dns/rever...

shadoxx

2 ปีที่แล้วdiscuss

Glad Technitium is getting its day on HN! I've been using this for around six months now, did a deployment on my home network after rebuilding it from scratch. Multiple zones, forward zones, hosting SOA for internal domains, DNSSEC. Hands down the BEST modern DNS infra you can deploy if PiHole doesn't fit all of your needs. I'm running it on a Raspberry Pi 4 alongside my Unifi controller with zero issues!

Using Technitium on your local network is like rolling your own Route 53 management console internally. I hate to use that comparison, but I think that'll hit more for some users on HN! If you need that kind of fine grained control, or if you just don't want your hand held on DNS, that is why you would choose this over PiHole.

Thank you to the Technitium team for giving us such a great product! Even if your name is hard to spell.

shadoxx

3 ปีที่แล้วdiscuss

Hive13 in Cincinnati seems to be flourishing in all regards! The core membership and leadership has always taken the organization seriously, and that attitude has helped them curate and sustain membership for over a decade now. I just checked their financials (the entire org is open), and it seems like the formula they have continues to sustain their bank account and membership numbers. I think that in general, hackerspaces haven't really gone anywhere. Like most organizations, sometimes they fail due to no fault of their own, or leadership decides to pivot to a more sustainable model - as some have mentioned here a more "WeWork" model. The hackerspaces/makerspaces are still there. You just have to look!

https://hive13.org/

shadoxx

7 ปีที่แล้วdiscuss

Once VR gets to a certain point, and the resolution becomes so undeniably crisp, we'll want things exactly like this. You can already do this on Windows with Virtual Desktop Streamer and a companion application for either the Go or the Quest (paid application). If you can touch type, it's very easy to strap on the Quest and use it as your primary monitor. Having had this experience, I'm guessing that we're only one or two generations of hardware away from this being a normal way of computing. You know, provided smartphones, tablets, and otherwise proprietary operating systems don't take over first, Brother Oculus included.

shadoxx

8 ปีที่แล้วdiscuss

Here's a story I haven't shared in awhile.

One of my first gigs actually getting paid to code was getting hired on as a last ditch effort to save what was (unknown to me at the time) a failing business. It was a company that basically relisted real-estate auctions on their own site, coded entirely in PHP, by a single developer who had read "How to Code PHP in 24 Hours". They had one client that was basically keeping them afloat. It was so disorganized that at one point I was tasked with making a quick YouTube commercial in Adobe Premier for a client, showing off the features of our whitelabel product with their logos, edited from a stock template. I do not know Adobe Premier. I digress.

The main PHP file (yes) was 20,000 lines of code. Want to add a new feature? Copy that file into a new file and save it as newfeature.php. Database operations weren't transactional, there was no change management, and for about a week we were using production systems to code until development environments were made for us.

There was other shady stuff going on too, like using over a hundred proxy accounts to scrape content from other listing sites. I refused to touch or even look at that logic in the codebase, and it was always talked about in kind of a hushed way. I was young, didn't know any better, would nope the eff out if a similar opportunity came along at this stage in my career.

They folded shortly after laying off pretty much everyone but the CEO and the lone coder. Dumpsterfire would be an understatement, but my coworkers were chill and helped make the best out of a bad situation.

EDIT: Oh yeah! I forgot to mention the hardcoded password the was site wide that we used as a sort of "impersonation" feature. You could type in any user account and this password, and it would log you in no problem. No, we did not have auditing controls.

comments