GeekMan
@GeekMan@sh.itjust.works
- Comment on Requests for all:* page 2 timeout. 2 days ago:
No worries! Thanks for the fix, and running the instance.
- Comment on Requests for all:* page 2 timeout. 4 days ago:
I’m so sorry for my delay. Just had a hell of a weekend at work and only just resurfaced.
To give you some more detail (it might not be good enough for QA but I’ll try)…
Blorp 1.9.4, Pixel 7, Android 16.
I mentioned in the title of the OP that the issue occurs when browsing All/* (New/Hot/Active).
For Blorp, the issue presents after I load All/anything, then scroll through the feed until it stops, I assume it should have infinite scroll, I keep gesturing ‘up’ (to scroll down more), but no more posts appear.
I can scroll back up to the top and gesture ‘down’ to make it refresh and it does, but just the initial 50 posts then no more
I assume 50 posts is the first-page fetch.
My initial post was also triggered by my experience in Boost, which actually shows a ‘timeout’ error popup, about 30-60s after scrolling to the end of the first page-feed.
Lemme know if you need more details.
- Comment on Requests for all:* page 2 timeout. 1 week ago:
I’m not sure if that, sorry. That’s just my primary (?) instance, and I’ve seen it happen before and saw another post thinking it was the instance, too.
It might not be just the instance, since it only happens when aggregating ‘all’, and not local or subbed.
Bear with me. I’m a relative newbie to Lemmy & federation.
- Submitted 1 week ago to main@sh.itjust.works | 17 comments
- Comment on Second Page of Posts Failing to Load? 1 week ago:
Same (via Boost & Blorp for Android, last few days)
- Comment on [deleted] 7 months ago:
Heh yeah they’re getting better.
One day working in I.T. at a bank, I received an email that was formatted and written really convincingly that someone has referred me for a bigger role with a salary bump, with light/abstract details that could ‘be inferred as’ relevant to my country, sector & role. It just asked to click-through to see the opportunity-
-which popped-up a warning from the company’s I.T. security that this was a phishing testing/training email, and I’d failed.
I usually evade a phish, but this slightly-targeted one got me good.
After that I had to ritualistically double-check potentially legitimate emails from external domains, for sketchy domains/short URLs/links/tracking cookies etc, because they included vendors & 3rd party consultants or contractors we were working with.
At least (the) God(s) know scammers are bad people.
Heh.