Rikki

The 'grid' idea is interesting. Know of any other product that does localization with that method?

I just wanted to note that we've improved the error message for this error in 4.5, so users at least won't see a mysterious "-200" message when it happens.

We aren't planning to update FA in this release, no. We don't consider the cost/benefit to be worthwhile at the moment, given that it'd impact backwards compatibility with themes (unless the javascript swap technique is used, which is less than ideal). We'll consider the available options at the time of the next major release.

No need to hold your breath - it's already fixed and merged into the next release 👍

I've logged an issue for this and we'll look at getting it changed for 4.5 🙂

A fix for this was actually merged this past week. It should be included in the next major release (not the next 4.4 point release, since it's a higher impact change).

Platforms that use reverse order do so to show feeds - individual items not related to each other. We do that for the topic listing and for streams. I can’t think of any platforms that actually show conversations in reverse order. Twitter replies, iMessage, WhatsApp, Facebook and Instagram comments - they’re all in regular chronological order (aside from when ‘intelligent’ ordering is employed, such as Facebook showing 'relevant' messages or Reddit sorting by most-upvoted). In fact, the only medium I can think of that uses reverse order is, ironically, good old-fashioned email (and even that depends on your client).

The only app being tested right now is a 'white-label' app for this community. The multi-community test will come later. We're gradually expanding the number of testers, so sit tight 🙂

Whoops, you're right. Text isn't a 'child' in CSS, so actually I don't think there'd be a way to do this with CSS alone. Sorry for the confusion!

You could actually do this already - add this to your custom.css theme file: .ipsType_richText span.ipsEmoji:only-child { font-size: 48px; }

We anticipate it'll be available with v4.5, or shortly afterwards 🙂

Luckily, thanks to our work on the native app, we now have a services infrastructure that can register user devices and send notifications - when we feel the time is right. That's an example of the work we're doing on the app feeding back into the main product. You are obviously welcome to voice an opinion, but I feel like we're going in circles a bit. We've explained why we're going this route and why we don't feel PWA should be a sole focus right now, so repeating "but why?" in every reply won't get a different answer at this point.

My personal recommendation is use a password manager, preferably one that stores the encrypted passwords on your own storage (e.g. your own cloud account) rather than a central server. That way you can generate extremely good passwords and maintain a different one for every site without any hassle.

This part alone is enough reason for us to provide an app, I think. Many admins that offer TapaTalk have been itching for a first-party (or even a third-party) alternative. They view TapaTalk as a necessary evil, not something they're legitimately pleased to offer their users. We hope to be different in that regard. Regarding web vs. not web. If web apps on their own were perfect, there'd be no market for TapaTalk, for example - but as you say yourself, there clearly is. The lines are blurring though; the codebase we have for the native app can be transformed into a web app with a little effort. It is, after all, built on a framework originally designed for the web. We will be able to take what we learn from building a new native app, and apply that to the regular web view. Probably not in the 4.x line at this stage, but certainly in the 5.x+ lines. Some of the work may even be directly beneficial. For example, with the new API, we or third-party developers could build entirely new ways of using the Invision Community platform on the web. Finally, we know the app won't appeal to all communities, for various reasons. That's OK. The app won't stifle any potential PWA work (and as I said, it'll actually make it better), so those that don't want to use the app won't lose anything. Those that do will gain a new way of offering their community to users.

We have a fix ready and it should be in the next release 😊