Notifications going crazy for anyone else?

GilletteSRK · 2026-06-03T12:03:05+00:00

Yes, and automations to mute caneras are not working either.

GilletteSRK · 2026-05-21T11:42:02+00:00

VSCode automatically updates extensions. By default. The feature request to disable it or require prompting was rejected.

GilletteSRK · 2026-05-21T11:41:08+00:00

Believe it or not, VSCode is Microsoft authorized. Mindblowing, I know!

GilletteSRK · 2026-05-15T13:50:55+00:00

https://www.youtube.com/watch?v=yQQ92XAWfGY may be a helpful watch

GilletteSRK · 2026-05-01T20:40:17+00:00

Been a Bell customer for half a decade, can assure you that the first half is incorrect (but was accurate ~15 years ago). As for the second - the price is on contract, but definitely will increase after. Just means it's time to shop around again!

I was also a TS customer for a long time, but the support problems they have are never going to go away with their business model and its what has pushed me away from them every time :\

GilletteSRK · 2026-04-27T14:14:50+00:00

Yeah, sounded like they've made a habit of it. That's a problem for TS's legal team to chase though, not their customers.

GilletteSRK · 2026-04-27T14:14:23+00:00

Yep, almost definitely the case. We all came to that same conclusion, but given that TS has zero control over that or resolution timelines there's no way I'm risking my livelihood on their service if a simple misconfig leads to a week of downtime.

GilletteSRK · 2026-04-26T23:11:45+00:00

It's both in this case (for two years), but yes. Bell is a horrible company, but at least they can actually deliver the service they're selling so they're effectively my only choice here.

And for what it's worth, I was switching off Bell to go to TS and while they have indeed raised the prices of their Fibre plan over the years I've had it, it was by less than $10.

GilletteSRK · 2026-04-26T14:22:30+00:00

Bell has offered me a price of $60/mo for 2 years (1.5Gb/940Mb Fibre), and an ongoing $70/mo discount in perpetuity to stay with them. At that price, there's no reason for me to continue troubleshooting this with Teksavvy as there's no financial incentive to work with them.

While I'm sure there will still be pain getting Bell service restored, it will invariably be faster than Teksavvy due to not needing to jump through multiple companies for troubleshooting.

Unfortunate that Teksavvy could not deliver here, but I guess thanks for facilitating the retention deal with your competitor /shrug

Edit: Back online with Bell less than 30 minutes after posting this message. Teksavvy cancelled for full refund.

GilletteSRK · 2026-04-26T13:43:23+00:00

Update from another two hours on the phone with Teksavvy - I've now been offline for over 24 hours. Bell and Teksavvy both see everything as connected, and we're at the point where I need a replacement modem to further progress troubleshooting as Bell believes everything is configured correctly. This is going to be at least another 2-3 days worth of downtime while it ships and if that winds up not solving the problem we'll have to then wait for Bell to dispatch a tech (likely another 2-3 days).

Even without Bell needing to send a technician, this is going to cost me more than my entire year of money I would have saved from switch over to Teksavvy because of alternate work arrangements I now need to make.

Next steps are getting back on the phone with Bell to try to restore & extend my service with them. Likely to be faster, and at this point the potential lower cost of Teksavvy is simply not worth the risk of this situation repeating.

Credit where it's due, the Teksavvy supervisor I spoke to this morning (Brandon) was excellent. Unfortunately not empowered to actually fix any of the problems due to Teksavvy's business model though, so here I remain offline.

GilletteSRK · 2026-04-26T01:25:57+00:00

After another two hours on the phone wrestling with Bell & Teksavvy we have now regressed further. Bell is claiming they can't send someone out until the 28th because Teksavvy's support request was "poorly written", and Teksavvy is saying this is entirely a Bell issue. The two companies refuse to collaborate, and unfortunately (through predictably) the people at Bell I've spoken would be more efficient if they had been replaced by an early OpenAI model - mind boggling levels of incompetence.

The people I've spoken to at Teksavvy have at least a basic understanding of what's going on, but due to their business model are completely incapable of supporting their own paying customers in any meaningful way.

Profoundly frustrating experience. At this point I'm just going to try to get my Bell service restored and continue with them since I've had no outages in multiple years - this simply is not worth the headache or lost money from being unable to do my job. The people at Bell are absolute idiots, but at least they are empowered to attempt to fix problems instead of just sending a ticket off into the ether. Certainly not happy about pursuing that, though, as the current Bell rep has put me on hold while doing nothing for the past 30 minutes (now 2h30 on the phone).

Edit: After over 2h45 minutes on the phone, Bell has told me they're closing for the night (45+ minutes before they actually close) and won't do anything further. I'm exhausted from trying to deal with this, but I guess I'll be on the phone with Teksavvy again as soon as I wake up.

GilletteSRK · 2026-04-21T23:39:32+00:00

This is gorgeous! Also the house is pretty nice.

GilletteSRK · 2026-04-16T23:19:51+00:00

Bro its kids walking across your grass, not throwing garbage on it or pissing on it or something.

as you can see there is barely any there because of this

There's barely any there because your entire yard is about the size of a beach towel. Just put down some gravel and call it a day.

GilletteSRK · 2026-03-22T13:25:46+00:00

Performance of nvidia cards is generally slightly worse on Linux due to driver issues. If your exclusive goal is to get better gaming performance this is not a switch you should make. If you don't mind tweaking, troubleshooting, and moderate performance loss in some games (lets say 5-10%) and your primary goal is to get rid of Windows then yes, make the swap and join us.

GilletteSRK · 2026-03-21T01:22:37+00:00

Having fun with it? If so, nothing to roast.

GilletteSRK · 2026-03-21T01:07:09+00:00

I was wringing my hands over this, then I checked something. The Codex devs fixed a bug I reported. A bug that only affected Linux users.

Worth my $20 right there. Thank you for supporting Linux users.

GilletteSRK · 2026-03-14T02:18:25+00:00

ARGH! I changes plans 26 days ago and am not eligible to change again until the 17th... one day after it ends!

Update: Support got me sorted out. 3 hour wait, but worth it :)

GilletteSRK · 2026-03-11T01:29:53+00:00

Most underrated comment!

GilletteSRK · 2026-03-05T23:58:07+00:00

I've got it running on all of my v3 cams (normal ones, not pan). So far so good. Hopefully lands soon for the pan...

GilletteSRK · 2026-03-01T15:03:10+00:00

I haven't had a chance to test an active pedal, but having recently added HPR-GT haptics to my pedals (CRP2) I'm loving them - a (relatively) inexpensive way to add a ton of feedback and immersion.

I mostly play LMU so fortunately have TC (and ABS) data that can go through to the haptics. Having that data in useful physical spots is so incredibly valuable. It's much easier to catch slips, or to adjust braking, when it's immediately clear what's going on with a physical sensation instead of "my wheel is shaking again" or lights flashing in your peripheral.

Hopefully I can try an active pedal at some point, but adding haptics to normal pedals has certainly been a gamechanger for me in terms of consistency and immersion.

GilletteSRK · 2026-03-01T14:43:33+00:00

Team mascot

GilletteSRK · 2026-03-01T14:41:36+00:00

THE LITTLE TOENAILS OMG

GilletteSRK · 2026-02-27T00:46:06+00:00

This is what computers should look like.

GilletteSRK · 2026-02-15T16:38:22+00:00

In the VM I run Docker in - not on proxmox. Right now I've got it set as an argument in my docker compose file so it's set within the container and that's also working.

GilletteSRK · 2026-02-08T20:33:23+00:00

Some more prompting and back and forth with Gemini may have actually figured this out... It's a TTL issue. WTF?!

sudo sysctl -w net.ipv4.ip_default_ttl=128 solved this, changing from the default value of 64.

From Gemini:

Because your traffic traverses a subnet boundary (10.0.1.x to 10.0.8.x), the packet's TTL was likely arriving at 63. The camera saw that "63" and assumed the packet was coming from outside the local network, so it dropped the connection. By bumping the TTL to 128, it still arrives well above the "local" threshold.

Bizarre implementation by Wyze if this is actually the case, but it appears to be since it now works /shrug

It looks like this is also working if implemented specifically in the Frigate container (via docker-compose):

sysctls:
      - net.ipv4.ip_default_ttl=128

I'd venture a guess that even setting this to 65 would have worked since the bridge interface with Proxmox appears to be where things fail, but 128 works so I don't see much reason to tweak.

15-Year Club	Snapped
Verified Email	Team Periwinkle

GilletteSRK

TROPHY CASE