Everade

Why are invisioncommunity devs so blind for webp?

It's not like it requires any other extra work, since the compression of webp is already existant by nature.
Simply allowing webp by default shouldn't be the biggest deal, or is it?
It's already widely accepted by all major browsers, so there's no excuse on that anymore, especially not since you dropped IE support yourselfs.
But still, every request and any conversation about webp have either been put down, or ignored.

Could we please get an explanation why you're so anti-fast-web?
I'm honestly wondering why is that.
 
I'm also wondering if the spacer.png image load implementation is still best practice either.
Wouldn't it make more sense to add native lazy loading instead?
Really keen to live up to todays SEO standards and performance requirements.

Sounds like you're just trying to annoy a handful of people who're not kind by nature, and end up sacrificing the patience of the kind majority.

I'm well aware about plugins delivering better solutions than what IPB does.
Currently using a different one which is outdated and unsupported since quite a while:


But it's simply something that IPB should deliver properly instead of the half-baked function that's been available for the past x years.

Seems like a needed feature for a chat application to actually open the chat. 

I assumed it was implied that it would open a window, without that its useless as a chat integration. How are people supposed to know to open up a chat window? 

Is there a way to make it launch a discord chat window? It does not provide value to me without that. Our users do not generally use discord, so we would want to open a window for them. 

There should be better possibilities to retrieve certain data within an RSS feed for Pages.
Yes, there's now the possibility to generate custom RSS feeds, but it still lacks lots of options as its an extremely basic filter.
What it currently generates:
<item> <title>Topic_Title</title> <link>https://mysite.com/community/announcements/topic_title/</link> <description>Actual text content</description> <enclosure url="https://mysite.com/community/uploads/image.png" length="11111" type="image/png"/> <pubDate>Wed, 09 Jun 2021 01:12:00 +0200</pubDate> </item>  
There's currently no possbility to include any of the additionaly added fields.
I haven't tested all of them, but i'm pretty certain that none of them are included in any feed.

These are just examples, to outline what's not possible with any RSS feed feature given by IPB:
Category [Type: Select Box]      (To define articles in the RSS feed) Summary [Type: Text Area]       (Text field, for proper news summaries) Thumbnail [Type: Upload]        (Additional image upload for smaller image versions) Here's are the example setup fields:

 
It would be great, if we could define which additional fields are included in the RSS feed.
Or at least include all fields by default.
 
So we can achieve something like this:
<item> <title>Topic_Title</title> <link>https://mysite.com/community/announcements/topic_title/</link> <description>Actual text content, lorum ipsum its a lot.</description> <enclosure url="https://mysite.com/community/uploads/image.png" length="11111" type="image/png"/> <pubDate>Wed, 09 Jun 2021 01:12:00 +0200</pubDate> <thumbnail>https://mysite.com/community/uploads/thumbnail.png</thumbnail> <summary>This is a quick summary.</summary> <category>Event</category> </item>  

Long list, but TikTok is missing. Can you add it?

There's currently no option to set icons being maskable or not.
And IPB, by default doesn't set the maskable attribute.

Google Lighthouse Audit as such doesn't rate the PWA setup as optimized.

Would be great to either set it by default in the manifest file, or add an option for us to set the maskable attritbute ourselfs.

https://web.dev/maskable-icon-audit/?utm_source=lighthouse&utm_medium=devtools
 
Of course, this isn't just about Google Lighthouse Rating improvement, but it also allows us to mask the icon 😉

There's currently no option to set icons being maskable or not.
And IPB, by default doesn't set the maskable attribute.

Google Lighthouse Audit as such doesn't rate the PWA setup as optimized.

Would be great to either set it by default in the manifest file, or add an option for us to set the maskable attritbute ourselfs.

https://web.dev/maskable-icon-audit/?utm_source=lighthouse&utm_medium=devtools
 
Of course, this isn't just about Google Lighthouse Rating improvement, but it also allows us to mask the icon 😉

Someone here is fearing to missout on dark theme sales.
This would be a great addition, and has become standard for any great web service these days.
For example right now i'm almost losing my perceptual vision because i'm on this website.

Someone here is fearing to missout on dark theme sales.
This would be a great addition, and has become standard for any great web service these days.
For example right now i'm almost losing my perceptual vision because i'm on this website.

Someone here is fearing to missout on dark theme sales.
This would be a great addition, and has become standard for any great web service these days.
For example right now i'm almost losing my perceptual vision because i'm on this website.

Someone here is fearing to missout on dark theme sales.
This would be a great addition, and has become standard for any great web service these days.
For example right now i'm almost losing my perceptual vision because i'm on this website.

IPS Forum should be able to change the color of the template to a dark - button, not via an additional plug, but only built into ips forum. 

@Marc Stridgen Thanks. Anxiously waiting for this implementation/fix... 🙂
 

There's currently no option to set icons being maskable or not.
And IPB, by default doesn't set the maskable attribute.

Google Lighthouse Audit as such doesn't rate the PWA setup as optimized.

Would be great to either set it by default in the manifest file, or add an option for us to set the maskable attritbute ourselfs.

https://web.dev/maskable-icon-audit/?utm_source=lighthouse&utm_medium=devtools
 
Of course, this isn't just about Google Lighthouse Rating improvement, but it also allows us to mask the icon 😉

Allow HTML posting for admins, then add the appropriate HTML code to post a normal image in the source.
It's a chore but seems to be the only workaround we have.
I wouldn't allow this for normal users though. (Security)
There should be an easy way to post as many images as we want, as easy and quickly as possible with or without light box.

Hi, I liked the idea and had some spare time so this is a very simple plugin (no settings etc.) to remove that line ...

Hope you like 
Hide Redirect Counter 1.0.0.xml

This is something that has been bothering me for some time now. Why E V E R Y image on a post must be thumb nailed and posted with a lightbox link?  WHY?
I know it is like this for long time now but still, it makes no sense to me. That would only make sense if only puts lightbox on images bigger than my upload limits. Not for smaller images like this one:





Someone knows anything that can prevent that? Some configuration that i didn't found it, any plugins, anything?

Thank you.

Hi,
It may be useful to reduce database occupancy to add an option detecting full quotes (when fully quoting the last posted message) and automatically removing it. Some users don't know how to post without just quoting the full previous post they're answering to...
As a bonus it also can enhance the readability of a discussion when such users participate.
Thankyou for your attention,
D

You forgot: "In 5 years from now." 
And yes, i mean it.
 
Maybe they do, but they don't care. There are hundreds of community posts screaming for improvements but they couldn't care less. You're better off preparing for your funeral than waiting for a patch that adresses long standing issues. They simply don't have a big enough team to work on whatever they want + plus community requests.
5.x may address some issues, but you're better off not betting on it. Never take their word, there's still a ~3 years waiting list of other promises.
But what you can expect is another new re-design as usual. Because new looks and marketing sells best. Let's just cross our fingers that at least some of the underlying ancient code gets updated a long the way.
 

You forgot: "In 5 years from now." 
And yes, i mean it.
 
Maybe they do, but they don't care. There are hundreds of community posts screaming for improvements but they couldn't care less. You're better off preparing for your funeral than waiting for a patch that adresses long standing issues. They simply don't have a big enough team to work on whatever they want + plus community requests.
5.x may address some issues, but you're better off not betting on it. Never take their word, there's still a ~3 years waiting list of other promises.
But what you can expect is another new re-design as usual. Because new looks and marketing sells best. Let's just cross our fingers that at least some of the underlying ancient code gets updated a long the way.
 

Yea, why would a 16 years customer complain about a product. Everyone should just keep their mouths shut and look how the company runs its product into the ground.
Hell no, i want to see things get better so i actualy can continue using it. Got a proplem with that?
They've been doing many many bad design decisions in the past, and are most of the time working on content no one ever asked for.
And i'm not saying new features are bad, i'm just saying that they never focus on actual practical customer issues that have been reported years ago.
But they don't, they keep ignoring us but continue taking our money.
It's a great product overall, there's no reason to move.
But at the current state, there's a good reason to stop paying the subscription or at least pause it for a longer period.