I finally decided to post a thread here, and I have friends who want to see it, so after I posted it, I sent them a link. I soon heard back that they couldn't find the thread. Checking here on my laptop, it's here, and has had a bunch of views. Looking for it with my cell phone, though, the mobile site tells me the thread doesn't exist. It's been up six hours, according to the forum I can view on my laptop, but is still a no-show on the mobile site. Any ideas why the two sites/access options aren't sharing the same complete database?
Hi Robert, thanks for reporting it! I'm not the technical wizard but I'm guessing it might have something to do with mobile view. We do occasionally find a glitch on that platform. But now that you've mentioned it, hopefully our experts will dig in. Or it will resolve itself, that often happens too. For better or worse.....
"Hundreds of years from now it will not matter what my bank account was, the sort of house I lived in or the type of car I drove... But the world may be different because I did something so bafflingly crazy that it becomes a tourist destination"
paul wheaton wrote:I went to my cell and typed in permies.com/t/143172 - and it showed up fine.
Can I get some more details on how it is not working?
It's working now, at 06:00 my time, but when I wrote the post last evening, it had been available on my laptop for over six hours, but neither I nor my friends had been able to get it on a cell phone. A later check I made in the evening still couldn't find it. I'm thinking there must be two databases for the two sites, and one wasn't updating in a timely fashion. S'all good now. I appreciate your checking into it.
Your consent is at the root of most every problem you ever had, outside of figuring out your permaculture projects.
I wonder if it's that self-repairing bug that has been in the system for years.
Sometimes a post won't index or some sort of technical word for a few min or even hours. While this happens, it shows up on some computers but not others. But it then suddenly works just fine.
It's been really hard to reproduce this with any consistency, and since the bug is self-repairing, fixing it has been a pretty low priority.