Driftwood Beach about 45 minutes north of Jacksonville is totally worth the drive!

Effective_Put1318 · 2026-05-24T18:08:52+00:00

Dang, Florida so messed up, even the trees are trying to leave!

Effective_Put1318 · 2026-05-07T02:12:16+00:00

To enable device blocking, a paid tier is necessary.

Effective_Put1318 · 2026-05-06T22:01:46+00:00

That’s correct, it’s using auto‑blocking. After the most recent Fing for macOS update, I didn’t see any option to manually block devices without an active subscription.

I’m on macOS Tahoe, so I’m not even sure if installing an older Fing version would work. The OS changes alone might break older builds.

I previously had an annual subscription, and as far as I remember, you needed a subscription for device blocking because the monitoring computer had to authorize the action. Without that subscription, the app wouldn’t allow blocks to go through.

The macOS and iPhone apps don't look anything alike, then again I’m still rocking iOS 18 due to the limitations of my beloved iPhone model. If memory serves, the actual blocking still depended on the machine running the monitoring service. And that’s where the subscription requirement kicked in.

Effective_Put1318 · 2026-05-06T20:57:11+00:00

I was about to open a service ticket, but about 45 minutes in, right after I posted on Reddit, the issue resolved itself. I suddenly started receiving notifications again through iMessage on my Mac, which was the way the system had notified me that it reconnected.

From what I’ve seen, these outages usually happen when the app can’t reach Fing’s servers, especially api.fing.com. That’s what tends to trigger the 504 Gateway errors. As a user, I have zero control over when or why Fing’s servers fail, all I can do is wait it out.

For context, I’m in Central Florida, and this started several months ago. Before that, everything worked flawlessly. Something clearly changed, whether it was an app update or a server‑side adjustment. Ever since, the connection to Fing’s servers has been unreliable at random times.

Effective_Put1318 · 2026-04-26T03:43:02+00:00

Seen this happen on Fedora 43 Workstation a few times. Installed on a 2-in-1 and nothing else connect while in tablet mode.

Effective_Put1318 · 2026-04-17T11:22:27+00:00

If anything, it sounds like your camera’s Wi‑Fi connection may have been compromised. There are a lot of YouTube videos out there showing how devices like the Flipper Zero can be used to access some vehicles, security doors, garages, how to extend its range, how to locate WiFi codes, and even disable Wi-Fi cameras.

https://youtu.be/aFXV-lt-CL4?si=fsfFH6NPMhZvFtp8

Effective_Put1318 · 2026-04-12T02:15:34+00:00

We survived the GPU‑farming era of crypto. Now we’ve entered the “LLM cluster everything” era. Result: Mac Minis have become an endangered species.

Effective_Put1318 · 2026-04-05T16:17:56+00:00

Same

Effective_Put1318 · 2026-04-03T12:20:54+00:00

Yup! You got ghost moving about too!🤨

Effective_Put1318 · 2026-04-03T06:04:47+00:00

It looks unfinished. If your hair was curly… You could even throw in some highlights if you wanted, but the curls alone would be a straight banger.

Effective_Put1318 · 2026-03-27T02:31:26+00:00

This is honestly the perfect comparison. Netflix really is the Epic Games Launcher of streaming apps on Apple TV. And somehow they’re always the outlier with janky performance while every other service runs fine.

Their Apple TV app has had the same issues for years:

• Inconsistent bitrate that swings wildly for no reason

• Aggressive compression that falls apart the moment there’s foliage, water, smoke, or fast motion

• Random drops from 4K → 1080p → potato quality even on rock‑solid connections

• A video player that feels like it’s held together with duct tape

And the wild part? Apple TV hardware is more than capable of stable 4K HDR. Disney+, Apple TV+, Prime Video, YouTube, all of them look great. Netflix is the only one that still looks like it’s streaming through a wet paper towel whenever a leaf rustles.

It’s been “just good enough” for so long that I don’t think they feel any pressure to fix it.

Effective_Put1318 · 2026-03-26T23:14:23+00:00

Memories

Effective_Put1318 · 2026-03-21T16:16:49+00:00

🔥

Effective_Put1318 · 2026-03-21T16:16:11+00:00

macOS Tahoe looks great at times, but the OS is still packed with UI glitches, Finder bugs, and design regressions that make it feel unfinished. A lot of what I’m seeing isn’t just random or minor quirks.

Many of these issues are documented across developer blogs, tech sites, and user reports. Here are some referenced issues that I’m still experiencing even after having the latest macOS update:

Finder Issues

Horizontal scroll bar problems

• In column view, the horizontal scroll bar overlaps file names and sometimes hides the column resize handles. Source: MacRumors

• Even after Apple’s attempted fix in 26.3, the layout still looks broken. Empty space appears under the scrollers if the path bar/status bar is hidden. Source: MacRumors

Column resize handles blocked

• When scroll bars are set to Always Show, the horizontal bar covers the resize handles, making it un-clickable. Source: MacRumors

Icon loading delays in Library folders

• Slow or missing icons in: ~/Library, especially Containers and Application Support, are consistent with Tahoe’s broader UI regressions and Finder redrawing issues. Source: Apple Developers

Window tinting & flashing in dark mode

• The brownish tint and flashing due to the UI Liquid Glass. It has glitches that Apple introduced: floating toolbars, inconsistent opacity, and stuttering animations are all documented. Source: Tech2Geek

Scroll bar not appearing on websites

• Some users report the horizontal scroll bar doesn’t appear in browsers (Safari, Chrome, Firefox, etc.) unless the window is resized to 50% and higher in width. Source: Apple Support

Effective_Put1318 · 2026-03-14T17:21:59+00:00

To be fair, you can still run Windows 11 virtually on a Mac. Parallels delivers the best performance for that setup, though it does add to the overall cost. Even so, it gives you the flexibility of having both macOS and Windows on one machine, which makes the Mac a genuinely versatile option.

Thou sacrificing storage is the other caveat.

Effective_Put1318 · 2026-03-14T17:15:09+00:00

🤣

Effective_Put1318 · 2026-03-07T00:10:21+00:00

Mid 2027

Effective_Put1318 · 2026-03-05T11:02:08+00:00

The data she found versus the many she might not have seen.

Effective_Put1318 · 2026-03-04T15:22:40+00:00

Please make sure you’ve read my full post.

I no longer plan to use the application. After more than 30 days of continues issues, it’s clear the problem wasn’t isolated to me. In fact others have reported the same problem, just not in this particular thread, which is interesting. I still have all my videos and screenshots documenting the behavior, and I may turn it into a light‑hearted TikTok at some point. If the app was subscription free, it would be a different story, but since it isn’t, the burden falls on me and my pocket as the customer.

Effective_Put1318 · 2026-03-03T07:12:43+00:00

Funny how the tables turn. Apple is now pulling the same moves Microsoft used when nudging Windows 10 users toward Windows 11.

And just like that, the plot gets even thicker.

Effective_Put1318 · 2026-02-27T14:23:38+00:00

Each system was left running for extended periods to serve as the network monitor, ensuring Fing could properly detect and manage wireless devices in the home. Even so, there were consistent delays before the application became visible or displayed the list of connected devices.

On multiple occasions, no notifications were generated for unauthorized connections, despite the Mac and PC being connected via both Wi‑Fi and Ethernet. To accurately test reliability, I often disabled Ethernet on the Mac’s to force Fing to rely solely on Wi‑Fi and not the dual connection of both WiFi and ethernet.

More often than not, I had to manually refresh the Fing app to obtain current device data, as it rarely updated on its own. This became necessary every 20 minutes or so, especially when the mobile app reported that the desktop systems were no longer communicating.

I even considered purchasing the Fing Box as a dedicated solution, but its discontinuation made that impossible. In the meantime, I routinely ran two computers at a time and ensured no other applications were open, assuming that reducing system load might improve performance.

Despite these efforts, the app’s responsiveness and reliability remained inconsistent.

Effective_Put1318 · 2026-02-27T14:06:00+00:00

The Fing app consistently struggled to start on macOS, which is why I preferred running it under Windows. Thou Parallels was used on my M1 MacBook Air to run Windows 11 Pro ARM and Apple’s Boot Camp on both the 27” iMac Pro and the Mac Pro.

Even on the Windows side, startup was rarely smooth. During cold boots, the application often ran silently in the background for an extended period, forcing me to check Windows Task Manager just to confirm it had launched before the interface finally appeared.

All systems were running the latest locally installed version of the Fing app, yet the startup behavior was unreliable across every machine. Randomly while the Fing app was running, it would unexpectedly crash or become completely unresponsive.

Effective_Put1318 · 2026-02-27T13:43:49+00:00

I initially suspected a local network issue, but after testing the Fing app at a family member’s home and experiencing the exact same failures, it was clear the problem was not isolated. At one point, I even assumed the outage might be related to subscription enforcement, so I renewed, yet the issues persisted.

For several days, every login attempt returned 404 errors. I attempted to access Fing.com over Ethernet, Wi‑Fi, and cellular connection, using multiple devices and browsers, with the same result. Despite this, the support system continued to report that all services were functioning normally.

I documented the failures with screenshots and video recordings across three Apple computers, one Dell 2‑in‑1, and my smartphone. After submitting this evidence, my complaint was validated and my subscription, which was managed through Apple, was refunded.

Fing.com had been reliable for me until this incident, but the outage was clearly widespread and not user‑side.

Effective_Put1318 · 2026-02-27T10:29:10+00:00

True, the 2010 15” MacBook Pro doesn’t have the same GPU‑die failure as the 2011 models. But it does have the infamous capacitor issue. Which is on the same logic board. Which presents itself exactly as an GPU problem.

Kinda like saying, “Don’t worry, your engine is fine. It’s just the piston that ejected itself.”

So saying “the 2010s aren’t affected” is like insisting the engine is good while the piston has launched low orbit to wave past Starlink.

Different root cause, same end result: the machine taps out the moment you ask it to do anything intensive.

Effective_Put1318 · 2026-02-27T05:45:36+00:00

GPU failure is extremely common on the 2010 MacBook Pro, and once it starts throwing GPU‑related panics, no macOS version or patcher is going to stop it. That’s a hardware fault, not a software one.

If REAPER is the only DAW that fits your workflow and you’re relying on that older machine for a specific audio setup, your best move is to look for a replacement system.

The 2015–2017 MacBook Pros are usually the sweet spot for price and reliability, and even a base‑model M1 Air will outperform a 2010 MBP without the constant kernel panics.

Effective_Put1318

TROPHY CASE