Interferon

Great, so the "free" solution costs more than any other provider, and they can't even keep a website up.

A lot of times someone will send me a private message. I open it, and it turns into something much more detailed than I want to deal with right now. I can't answer right away, but if I leave the window I am likely to forget about the message completely. In situations like this it would be helpful to be able to mark the message as "unread" or some equivalent state, so I still have a little red notification reminding me to deal with it later.

Another solution could be an option to just hide the categories widget altogether. I have fluid and traditional views enabled, and I switch back and forth based on what I am doing. If I want to drill down into categories, it's easier just to switch to traditional view.

I like the fluid forum view for staying on top of the forum contents, but the categories list takes up a lot of valuable real estate on a page we are trying to make the most of. I suggest making the categories box collapsed by default, and then allow the user to expand it when desired. Maybe this can be done in a drop-down box like the compact view does it.

We have a side bar filled with other stuff, and its a little awkward that the fluid and traditional views result in a side bar with a much different height.

Gallery image notifications appear to link to the category an image is in, not the image. If the categories default sort mode isn't "most recent first" the image is unlikely to even appear on the page.

In that process, you have to state your primary place of business, and the US is not supported. Americans are likely to have problems with taxes if they lie on the application.

Binance has banned Americans from creating accounts. Does this plugin work with binance.us?

Shouldn't the application do something? I did not see anything different at all about the messenger system.

Tried this out with IPB 4.7, did not seem to do anything at all. Nothing was different with it installed.

Yes.

Read this blog to understand what Google is doing:
https://www.joelonsoftware.com/2002/01/06/fire-and-motion/

I have found webp to be only marginally better, or in some cases worse then JPEG.

There's no way this format would have caught on unless it was being forced by Google. I know an image format that is (really, not Google's BS numbers) 30% smaller than JPEG and it isn't supported by any browser.

In my view, the only reason to use webp is if Google is giving ranking preference to sites that use the format (based on the format, not the file size). I think their approach has been to introduce constant change to web standards in order to make sites that can't afford to keep up obsolete. It's just a way to coursely rank content and tell which sites are being actively maintained and have the resources to keep up with constant changes. Microsoft use to do the same thing to desktop application development.

However, I can't find anything conclusive on whether they actually use the format itself as a ranking factor.

Member group color is a surprisingly effective way to stratify your membership levels. If I see a gold-colored user name I easily perceive that member to be more valuable than the default white color free users have (we use a dark theme). It very quickly conveys importance in a subtle way and makes the paid members stand out.

However, member group colors are not displayed consistently across IPB. The recent users online block does not show colors. The forum index page does not show the user name for each topic in colors. On mobile, in the topic view, when the member group is hidden, the user name is shown using the member group color.

I suggest applying the following rules:

• When the member group is shown, display it in color and use the default color (black, or in our case white) for the user name.
• When the member group is not shown, display the user name with the member group color.

When you select Share > More sharing options > Copy link, the copied URL does not include the referral ID. Other methods do include this.

FYI, the user who reported this initially confirmed they are using Brave browser.

Chrome seems to work as well.

--Edit--

Push notifications are working correctly in Edge. I replied from another account to a topic I am following

I disabled all add-on applications and plugins and switch to the default theme. Same behavior:

If I go to the notification settings using Edge browser, I am able to enable them:

But with Brave browser it hangs:

After upgrading from IPB 4.5.4.2 to the latest, and upgrading PHP from 7.4 to 8.0, I received a message in the notifications options saying that PHP GMP was not installed.

I installed the missing extension and phpinfo() now shows it is active:

The push notifications options are again available in the admin panel.

When a notification is received, there is a message saying a request will be sent to the browser to enable push notifications, but nothing happens after that:

This happens for me (using Brave, shields down) and also for the customer who reported the initial problem. I don't know what browser they are using.

But renewals will continue to be charged automatically, unless the user cancels? The user won't have to continue manually renewing their subscription?

This is strange. I have a subscription product (regular product with a renewal term) that is expired. When I click to renew it, a box appears asking how many months I want to renew it for? I want the customer to be charged month after month unless they cancel their plan.

I definitely don't want the default to just charge them one month.

I set the term to three months and pressed continue:

Will the customer be automatically charge on March 11, and every month after?

I am getting a null response when I try to use this end point with an OATH client. Does this one only work with an API key?

/core/members/{id}/achievements/{badge}/awardbadge

https://invisioncommunity.com/developers/rest-api?endpoint=core/members/POSTitem_achievements_awardbadge

Yeah, I am trying to also enforce license validation, so the user cannot set up fake responses to trick the software into thinking their subscription plan is active when its not. I used an intermediate script on our server with a list of pre-determined encryption keys both the server and application have, as well a question / answer scheme, which makes the whole thing pretty secure.

Wow, that's actually a lot better. It's self-hosted so there is no intermediary at all.

Web API responses can be easily spoofed. For license management, what do you think is the best approach to encrypt the Web API response so that it's impossible to create a fake response? Is there any built-in functionality for this in IPB or should I use an intermediate script that fetches the data from IPB and then encrypts it?