Recent content by Tamer

I understand both points, and I agree that this isn’t a battle that can realistically be won or something that can simply be switched off. AI is already here and will only become more common across all media. I’m just suggesting that as the ecosystem grows, some level of transparency helps keep...

What’s changed isn’t the existence of overlap, but the scale and speed at which it now occurs. AI-assisted development makes it much easier to reproduce existing ideas with minimal differentiation, which is why I believe some level of transparency is now necessary to protect long-term resource...

The XenForo Resources section is increasingly facing an originality problem that did not exist at this scale before the rise of AI-assisted development. In recent months, the number of add-ons that closely mirror existing functionality, appear shortly after original releases, or rely on...

Exactly. The premise was flawed from the start, which is why the entire conversation kept drifting further from reality.

Some of these complaints have drifted so far from reality they’re basically in lunar orbit. 😌

Much of this debate seems to come from applying the logic of fast-moving consumer software to a platform whose job is fundamentally different. Forum infrastructure isn’t judged by how quickly version numbers climb but by how reliably it supports years of accumulated content, countless...

You’ll never find statues built for critics. 😄

Tamer updated XenForo Emoji Performance Optimization with a new update entry: Optional robots.txt rule for bot emoji crawling Read the rest of this update entry...

Hi, It works on any XenForo version where you can set a custom emoji “Host from location” / base URL (including XF 2.2). The logic is entirely outside XenForo. Just make sure the JoyPixels asset path used in the Worker matches the emoji set/version your installation expects.

Tamer submitted a new resource: XenForo Emoji Performance Optimization - Eliminates JoyPixels CDN latency by serving emojis from your own domain via Cloudflare Workers. Read more about this resource...

This seems related to the Chromium 142 regressions we’re seeing on Android. Chrome, WebView and Edge share the same engine, so navigation/first-paint issues tend to appear across all of them. Since it also happens on XF Community, it’s almost certainly a Chromium-side bug rather than anything...

You can adjust the font size directly from the style properties. If you want to offer a separate option for elderly users, you can create a child style and configure the font settings there. @Xon also had an add-on called Font Resizer. You can consider using that add-on.

These behaviors only appeared while testing the LSCache add-on on XF. If you mean LSWS, it’s unrelated. @RichDevman

That sounds like another regression in the latest Chrome/WebView builds. It’s different from the loading bar issue I’m seeing, but it does point to broader instability on Android right now. Hopefully Google patches these problems soon.

Thanks, I hadn’t seen that thread earlier. I’ll follow the discussion there as well.