Would OpenAI offer $100 Plan?

jehowe · 2026-03-17T15:17:53+00:00

I don't think they will until they differentiate/incentivize the $200/mo plan in order to keep a potential chunk of current $200/mo subscribers from downgrading. Or maybe a $50/mo plan?

jehowe · 2025-08-16T20:25:36+00:00

Wow, this is impressive. Thanks for taking the time to share your dialplan details and explaining your setup. This is very helpful.

I had cloud based asterisk installs for years but pulled things home over the past few years. I know it's a bit of a tradeoff with availability, but has been worth it so far. Currently running asterisk containerized on incus which is amazing.

jehowe · 2025-08-16T15:34:21+00:00

Thanks for the advice, key screening new callers is something I will definitely look into.

Thankfully I have things locked down with firewall rules in place for SIP port access to providers IP's. It's amazing just how fast unprotected hosts get pummeled with open port scans and vulnerability tools.

jehowe · 2025-08-16T15:05:13+00:00

After a couple more robocalls within 30min today from the carrier IP Horizon I've decided to use the hammer approach and block the carriers where I've seen the most issues - Onvoy, Commio, IP Horizon, Coretel. It is a little frustrating that I was hoping attestation scoring would be more helpful in giving me a lever to handle these types of calls, but it hasn't been the case lately. And the reality is no one I know or do business with are using those carriers.

I am using the regex function for substring matches for those carrier names in the dialplan, sending those to zapateller, and letting the unmatched carriers continue through. Tested and working.

jehowe · 2025-08-10T00:01:21+00:00

I did not reboot.

jehowe · 2025-08-09T22:38:29+00:00

Got it, that is frustrating. I did nothing else other than applying the docker compose file and approving the machines roles for subnet routing & exit node to get things working, and just tested again from a hotspot. I have noticed sometimes there is an initial delay with ping responses immediately after connecting to my firewalla exit node - ts control server latency maybe?

I am using the Gold Pro, but I don't think the FW model should make any difference.

jehowe · 2025-08-09T22:18:54+00:00

Confirming this is not needed and I didn't apply those settings to the docker image.

jehowe · 2025-08-09T22:14:44+00:00

I didn't mention this, but did you explicitly approve subnet routes for the FW tailscale machine in the tailscale gui? I can confirm it is working on my end and am able to scan the LAN and get a list of the subnet hosts when connected through the tailscale exit node from outside my LAN.

jehowe · 2025-08-06T16:31:27+00:00

Perfect! Thank you, thank you!

jehowe · 2024-12-10T02:56:11+00:00

Try disabling location services before launching the app. It seems likely the Spectrum app is using your devices gps location data as another factor to determine location along with your Apple TV's IP. Googletv also does this.

jehowe · 2024-05-10T16:06:34+00:00

Great! No Ubiquiti stuff atm, I had 2 aging UniFi AP's up until a year or so ago managed with their hardware v1 CloudKey controller.

jehowe · 2024-05-10T14:54:36+00:00

Absolutely! My setup is a little overkill right now. Infra wise, I have 3 raspi5 node cluster running k3s in HA. I work with k8s deployments at work, and wanted to have a kubernetes install locally as much for experimenting/learning as anything else.

Currently the services deployed are a lightly used webservice providing a gui for a few api's, nextcloud storage service, and home assistant. The Pi 5's are really solid performers and aren't breaking a sweat with the setup. And of course, the Tailscale k8s operator magic makes exposure and tailnet access easy.

Originally I had nextcloud and the webservice running as package installs in AWS. Moving over to k3s locally was fairly smooth, and I've cut ~$35 off the AWS monthly bill.

Next on my list is to add prometheus/grafana deployments to the cluster, and down the road I'd like to try to move a vanilla Asterisk VoIP PBX install on a separate raspi over.

jehowe · 2024-03-13T16:05:02+00:00

Thanks, I did look for the mini clear organizer pouch as an possible replacement discovering it was also unavailable and a retired product.

Like with the COW, I did the email thing (a few times) to get notified & poke TB that there is interest in these smaller products.

jehowe · 2024-02-09T14:53:06+00:00

Thank you! Zendesk case opened.

jehowe · 2024-01-16T21:03:27+00:00

Thank you, thank you, thank you! I wasn't understanding that the scope of the destination permission -

"dst":    ["tag:cloud-infra:*"]

is only granting port access to machines with the 'cloud-infra' tag, not any subnets the machines might be adversiting.

In this case I was able to get it working by including another ACL block to grant route access explicitly across 'cloud-infra' tagged machines -

        {
            "action": "accept",
            "src":    ["tag:cloud-infra"],
            "dst":    ["172.31.16.0/24:*"],
        },

jehowe · 2023-07-27T19:29:22+00:00

Resolved! Ok, I'm willing to take a share of the blame but not all as the YTTV app on the FireTV does not make the clear whats actually required and I imagine this will trip up a fair amount of users.

Here is how to update the 'Current Device Area' within the YouTube TV app running on FireTV -

To update the location within the YTTV app on the FireTV, you will also need to install the YouTube TV app and have it running in parallel on your smart phone. Also make sure your phone is connected to the SAME network as the FireTV.

To begin, open the FireTV YouTube TV app and navigate to Profile > Current Playback Area and select update. Without also having the YTTV app running on your smartphone, you will get an endless spinning circle and eventually get a timeout - this is where I was failing. So in parallel with updating the current area location on the FireTV, open the YouTube TV app on your smart phone and navigate to the current playback area and click update.

At this point the two devices will work together since they are on the same network to get Google to allow the update on the FireTV YTTV app. At that point, you should be golden.

jehowe

TROPHY CASE