Talk:2881: Bug Thread

No idea what to put in the explanation box, so I just did the incomplete tag.172.69.33.185 05:36, 16 January 2024 (UTC)

I was writing an initial Explanation even as you did that. (I had an almost identical BOT-replacing idea. Which I continued to use as I hit the edit-conflict on yours.)

Not entirely happy with my narrative structure. Tried (too hard?) to not re-use phrasing. Either in there or in the Transcript (tbough currently leaving for someone else), I thought I might remark that either the Cueball-like beach-booker or the WhiteHat-like years-noter could be the half-seen uppermost post's contributor, based upon the visible portrait. But it seemed a bit hard to nicely shoehorn in, especially as it could be neither. Though any of those seen could also easily be up above the scroll-windowing, anyway, nearer where the unstated (to us) issue is actually described. 172.70.90.29 06:18, 16 January 2024 (UTC)

I hate when I have a problem with something, and when I google it either the solution is behind a paywall, too outdated to work, or has no responses. 108.162.216.173 06:43, 16 January 2024 (UTC)

Me, too. Want to rent a beach house and whine about it together? Barmar (talk) 07:45, 16 January 2024 (UTC)

Now that we've become firmly entrenched in the era of software-as-a-service & upgrade cycles that don't fix old bugs (looking at you, Raspberry Pi 2b-4b issues), I'm more likely to find a 15 year old post with workarounds that don't work anymore, than any page with an actual fix, when searching about an issue I'm seeing these days. Most of the time, I find stackexchange discourse detailing exactly what's wrong & everything that's been tried, with the most recent posts noting that prior workarounds are now deprecated by updates that haven't in any way addressed the issue. I don't even remember the last time I had an issue I didn't know how to fix & then found an answer online... The "answer" today is usually that 'that thing you could previously do (often something that was an almost innate or arguably essential feature) is no longer doable with modern service-based software, have you tried coding an entire software stack from scratch to recover this one thing you originally started using the software for? Everyone today just pays for several services, to do what home hardware could do 20 years ago, & don't even question why this accessibility feature went away.'

ProphetZarquon (talk) 15:26, 16 January 2024 (UTC)

Do you think DenverCoder9 made it to the meet-up? --Koveras (talk) 07:53, 16 January 2024 (UTC)

Gone. Reduced to ashes.--162.158.74.68 08:06, 16 January 2024 (UTC)

If, like me, you didn't remember who DenverCoder9 was, here is the link. Rps (talk) 12:51, 16 January 2024 (UTC)

The first time I read the one about "What did you see!?" it felt very biographical... Posting from Denver, here.

ProphetZarquon (talk) 15:26, 16 January 2024 (UTC)

I've added a link to that comic to the explanation. Barmar (talk) 17:16, 16 January 2024 (UTC)

Feels like there's something missing here about the fact that often these threads are actually an aggregation of people with similar-but-different issues, hence some of the 'I've tried all the fixes but they don't work!' responses. Currently beyond my wit to work this nicely in to the explanation though.172.69.194.37 16:26, 16 January 2024 (UTC)

Often there are minor differences, or the user doesn't really apply the fixes correctly. Or the software may have changed so that the old solutions don't work any more. Barmar (talk) 17:16, 16 January 2024 (UTC)