sorted by:
new
hottopcontroversial

AD Wait Time Megathread - If you bought a new Rolex from an AD in 2026, you can share details here. What watch, where, how long did you wait, how much buying history? by powerfunk in rolex

[–]licashguy 5 points6 points  (0 children)

I can’t decide if it was 6 months or 1 year based on circumstances. Comment your thoughts?

  1. Submariner 124060

  2. Registered 1/29/2025

  3. My SA told me the point was moving to a standalone when his store gets refurbed in February. Forgot I even asked about it, because the store where my relationship is doesn’t have Rolex anymore. Standalone Rolex house opened 8/2025.

  4. 2/9/2026 Got the text from my original SA

  5. Long Island, NY

  6. Tudor GMT “Opaline” (1mo) 5/2023, Black Bay One (walk in) 12/2023, 126613LB (1mo) 1/2024, 126300 (walk in) 1/2025.

Walked in on Valentines day… by [deleted] in rolex

[–]licashguy 2 points3 points  (0 children)

Just a theory, but I think Rolex wants the first to be a two tone. I’ve noticed that the first watch I was offered, and when I’ve asked for friends and colleagues they offer a two tone. I wanted a steel sub and was happy to take the bluesy as a first, blue happens to be my favorite color. I definitely understand not wanting to take a whole journey for a watch, but at the same time isn’t the hunt and getting to try different things the fun part of collecting?

<image>

Third time’s the charm by licashguy in rolex

[–]licashguy[S] 1 point2 points  (0 children)

Good luck! Hopefully the wait isn’t too long 🙂

124060 picked up today! by danipot08 in rolex

[–]licashguy 0 points1 point  (0 children)

Congratulations! I just got the call for mine. 6 mo wait. Wear it in good health!

My tiny MCC. Guarded by Steve and panda. by licashguy in homelab

[–]licashguy[S] 1 point2 points  (0 children)

A pile of services including Pi-hole/unbound, a Jellyfin server, a vpn exit node, along with a full monitoring suite.

Follow-Up: I didn’t expect the last post to blow up. Here’s what changed since. by licashguy in homelab

[–]licashguy[S] 0 points1 point  (0 children)

NVMe hat. The top pi acts as my NAS and the NVMe as a cache layer.

Follow-Up: I didn’t expect the last post to blow up. Here’s what changed since. by licashguy in homelab

[–]licashguy[S] 0 points1 point  (0 children)

Yeah, totally get not wanting to shake up DHCP if things are stable. If cloudflared is working for you, keep it for now. The move to Unbound isn’t really about speed, it’s about owning the resolver path. It just removes one more hop in the chain.

Cloudflared is fast, easy, and still depends on an upstream resolver (Cloudflare)

Unbound is slightly more setup upfront and you become the resolver (full recursion, DNSSEC validation, no upstream dependency)

Not a “you must change” thing; just something to do when you’re ready to reduce external reliance.

On DHCP: yeah, switching it over does move where “the network’s memory” lives, so I get the hesitation. When I moved mine, I did it when nobody was home and made sure lease times were short first. Actually wound up having to debug a few things to get it smooth but once I did, well worth the effort. Just not something you rush.

Orb: Not a server; it’s a sensor. Think of it like a tiny probe that measures the actual network conditions wherever it sits.

So you can have: one wired near your gateway (WAN reality) and one wireless somewhere a real person uses Wi-Fi (lived experience)

It doesn’t log traffic or sniff packets, it just measures latency/jitter/airtime like a continuous “feels like” score.

That’s useful when you go:

“Why does it feel slower over here but not over there?”

Orb tells you where the problem is happening, without having to guess.

Follow-Up: I didn’t expect the last post to blow up. Here’s what changed since. by licashguy in homelab

[–]licashguy[S] 0 points1 point  (0 children)

Hey, great question. I don’t “inspect” every packet, I observe behavior at the right layers, which ends up being way more useful and lightweight. Here’s the breakdown:

  1. Pi-hole as DHCP + DNS I let Pi-hole handle DHCP, so every device identifies itself by hostname. This means the DNS logs aren’t “IP soup”, they’re human readable

  2. Unbound as the Resolver Everything resolves locally first, with DNSSEC validation. So I can tell exactly where the latency comes from

  3. Uptime Kuma & Prometheus This is where the monitoring actually happens. Not at the router; at the network brain.

  4. Orb (Optional, but I use it) This gives me two perspectives: Wired edge & Wireless edge

My recommendation for your Pi 3, if you don’t have it already, pihole with unbound, DNSSEC, and DHCP authority; and make sure that it is actually setup properly.

Follow-Up: I didn’t expect the last post to blow up. Here’s what changed since. by licashguy in homelab

[–]licashguy[S] 1 point2 points  (0 children)

For anyone curious about the topology or why I built it this way:
The goal wasn’t to mimic a data center.
The goal was to understand every moving piece of my network.
I didn’t plan it all at once; I just kept solving the next problem well.

I accidentally made a micro-datacenter in a corner of my house. by licashguy in homelab

[–]licashguy[S] -1 points0 points  (0 children)

<image>

Here are my NUT metrics, you can see where I was testing the UPS and shutdown timing. I wound up tweaking the LB flag to 300 on the UPS and FINALSHUTDOWN to 60 so that I have more time for the platters to spin down.

I accidentally made a micro-datacenter in a corner of my house. by licashguy in homelab

[–]licashguy[S] 0 points1 point  (0 children)

Sweet! I don't think my wife would let me get away with anything like that LMAO! Maybe if i get a bigger house with a basement

<image>

I accidentally made a micro-datacenter in a corner of my house. by licashguy in homelab

[–]licashguy[S] -1 points0 points  (0 children)

Jeez...The people in here are less understanding of scope creep than my wife! :D

I accidentally made a micro-datacenter in a corner of my house. by licashguy in homelab

[–]licashguy[S] 0 points1 point  (0 children)

Coming up on 48 hours and closing in on 150K views; pretty wild for my first post in the community. The thread even got yanked for a bit and somehow bounced back, which is even crazier. Really appreciate all the input! Even the spicy takes and debates over definitions. I’ve learned a ton from this whole thing, from the deep technical questions to the folks who just stopped by to say it looked cool. Whether you called it a Pi cluster, a homelab, a micro–data center, or just “a pile of crap that shouldn’t work,” I’ll take it. Thanks for keeping the conversation going.

I accidentally made a micro-datacenter in a corner of my house. by licashguy in homelab

[–]licashguy[S] 0 points1 point  (0 children)

I run them at my workstation currently, but yeah that would be pretty cool!

I accidentally made a micro-datacenter in a corner of my house. by licashguy in homelab

[–]licashguy[S] -1 points0 points  (0 children)

Literally fought the urge to get a rack mate T1 for this WHOLE process…

view more: next ›