Linux-Is-Best

To me, the problem is not in delivering webp images.  It's in posting webp images.  
My users re-post webp images from around the web.  It works when they post to Facebook, to twitter, to tumblr, to their blog, but then it doesn't work when they post to my site. 

I cannot presume to speak for everyone, but it has been my personal experience whenever seeking out photos to share; all the website's I pull from as a casual user are already using WEBP. That is to say, my members, when posting images, are already frustrated that all the cool photos they wish to share seem to be incompatible with the site. To put that into context, imagine visiting a forum that was incompatible with JPEG. At this point, general web compliance and practiced user engagement should be enough to justify adaptation, in my opinion.
From a technical standing point, I recently updated a static website, which was heavily image-related. One of the last modification was converting my PNG's to WEBP. I noticed a full 4-second speed difference as a notable improvement. 

Thanks for sharing that. 
I know there are a bunch of cache updates slated for our next release. Glad to see in that topic you posted above there was an answer 🙏 

Another vote for .webp image files to be shown inline in IPS.
I've started seeing this format crop up on web sites and both Safari and Chrome support it.
Thank you.

Never.

You never bothered to read the main thread, obviously.
I've never asked for png to webp conversion with double savings for backwards compatibility, but for webp upload possibility and being actualy recognized as an image.
What you're talking about is an entirely different story.

This was never supposed to be nor become a debate, you're just offtopic.
Learn to read, accept the future.

Might be rare case for you. For me it isn't. It really isn't.
Just because cloudflare is the perfect solution for your personal project doesn't mean that it fits everyone.
Is it great overall? Absolutely. But it's not perfect.

Cloudflare might be great at optimization, but it doesn't KNOW nor SEE how the image looks like.
As such i prefer personal compression for optimal results. A machine doesn't understand images nor art. At least not for now.
In my case, Cloudflare only catches those pieces i haven't optimized myself.
I can save more space with personal optimizations where i want, and i can have the best qualitiy where i want.
Cloudflare is an image optimization fallback for me, not a solution.
 
Safari isn't an up to date browser, it's heavily outdated just like IE. I don't support that.
You do, others do, great, why not. I don't.
For me: double upload is at no point ever required. I save lots of space with webp.

And i repeat:
Cloudflare has nothing to do with the fact that we cannot upload webp as images to invision, anywhere at all.
-> Cloudflare doesn't fix the problem discussed in this topic.

Yes Cloudflare is glorious, i love it and use it too.
But it does not fix the very core of this topic and as such, shouldn't be discussed here.
It's a great hint for people who don't know about it.
But again:
It doesn't fix the problem discussed in this topic.

I understand that you don't need webp image upload support.
But others might. At least i do.

me: Alright?
you: Alright

k, thx, bye.

Cloudflare isn't capable of xxx to webp conversion in a dynamic website environment.  For example javascript.
Accessing the image directly might work, but Cloudflare has lots of issues when it comes to dynamic content.
This has nothing to do with the fact that not all images are optimized, but because Cloudflare isn't capable of handling certain cases.
CDN is always a great addition to automation and optimizations.
But it doesn't allow for much flexibility.
And how exactly do you think i'm saving processing power or storage, when i'm uploading a 10mb png vs a 5mb webp?
What has any of this to do with processing power?
webp is widely supported so double uploads are not really required. I'm not wasting space, i'm saving space with webp support.

Is Cloudflare flexible enough to optimize the webp compression per image? No.
Does it allow us to upload webp to invision? No 😉
I'm pretty certain that i'm at the InvisionCommunity here, and not at Cloudflare.
So please let it rest so we finally get the much needed webp support.
Thank you.

It doesn't work flawlessly for all image types in every situation. There are lots of cases where it simply doesn't work.
Been actively using it since quite a while and it doesn't solve the main issue, which is that invision doesn't allow upload of specific image types as an actual image.
It also doesn't allow us to optimize the compression, not globaly nor per image.
First step should always be to fix the actual problem, and not look for the quickest workaround.
AV1 (AVIF) is just another great format that's not supported by invision, however it's a younger format.
Originaly a video coding format with its final image specifications just finalized back in february 2019 if i'm not mistaken.

Please note that webp is out there in the wild since >10 years by now.
And there are people out there who're itching for invision's implementation since several years.

And now we have AVIF!
https://blog.cloudflare.com/generate-avif-images-with-image-resizing/

Yes, absolutely. Directly linking it within the editor works just fine, just like with webp.
Also uploading into the editor works just fine, that's great.

But you're missing out that we can not upload it as an "image".

How about webm as:
- Profile picture
- Bug Report "image" upload on your custom PAGES
- Cover Photo
- Forum Icon
- Grid Card Image

That's what you get:

 
 
What i'm asking for is, enabling mp4, webm uploads in all IMAGE locations and simply generate fake GIFs using:
Just like Twitter, Giphy, Instagram and all the other big players do.
<video autoplay loop muted playsinline> <source src="fakegif.webm" type="video/webm"> </video>  

It is recommended to output webp files in a <picture> tag instead of an <img> tag, which supports specifying multiple versions. That's something we'd have to take into account.
Also, ios14 added support apparently: https://css-tricks.com/webp-image-support-coming-to-ios-14/
I found that we have an open internal suggestion discussing this already so I've updated it. Thanks!

1.) Display webp as image instead of attachment (handle them just like all other image types)
2.) Allow webp as image upload option in all areas (Profile Picture, Cover Photo, Forum Icon, Grid Card Image, Pages when posting content and anywhere else that i've missed)


 
Repeat the steps for .WEBM (would be lovely since video compression is in most cases superior to animated images such as GIF and WEBP)
Would be really great to be able to be able to upload video format types in all the mentioned areas (Profile Pictures, Cover Photo, but especialy Pages)
 
3.) Add an option to swap all png images (profile content and/or uploads and forum core pictures) to webp instead with a conversion job that processes all images. (That's the bigger work i guess, but would be amazing to have.)
This would ultimately reduce the data usage by tremendous bounds, save bandwith and improve performance.
 

What things are you looking for support for specifically? Are you just meaning to display webp images as images, instead of attachments?
Obviously this is something we can look into too, but if you have a list of areas/problems specifically it might be a good starting point.
(For the record, recent releases of GD do support webp, as does ImageMagick, so server-side technology is not a hindrance)

I like the idea, on principle, of having the ability to turn off registration for a given handler, yet continue to allow login via that handler.

Interesting points! But what's stopping an anonymous troll / banned member from creating a new Twitter/Gmail account just to join? 😇  The skeptic in me fears that bots and spammers will find new ways to abuse the system regardless 🤦🏼‍♂️ 

I was humbly going to suggest that disabling the generic signup was potentially a bad idea. I was going to argue that further incorporating social media as the default requirement to join only further empowers people to use them.  But the more I thought about your concept, the more I could see a potential advantage.
First, it is not too far of a stretch to assume most people today already use Google, Twitter, Facebook, and alike. There is no helping it. Second, one of the biggest drawbacks to forums, especially small communities, is not having the human resources and infrastructure to root out many of the spammers and bots that social media does.  However, by disabling the general e-mail and requiring social media to join your community, you better ensure interested people join, as social media, at least in theory, have already rooted out the fifth.
Additionally, the more I think about your proposed concept, it could be a further deterrent when banning undesirables. Right now, if I ban someone, they can easily pick up a disposable e-mail and hop right back on. However, for example, for places such as Facebook, I need a verified e-mail, verified phone number, and upload a clear photo just to be validated. Banning a Facebook log-in can go along way in keeping more difficult people off your community when a simple e-mail is no longer an option.
Your proposal has caused me to think differently. I like it. 👍

Hello,
There should be more flexibility in the registration settings, with local depending on the service (Apple, Google, Microsoft) or global as currently.
In this context I would like to be able to deactivate the "standard" registration without deactivating "standard" the login, and allow only by Apple, Google, Microsoft registration and login.

Just for future reference. mysqldump --default-character-set=utf8mb4 -h [host] -u [username] -p [database_name] --set-gtid-purged=OFF --port=3306 --protocol=tcp --skip-triggers -r dump.sql  
It turns out, using > is not always a safe way of exporting. Using -r dump.sql instead of > dump.sql does the trick.

This can happen when you export a database with the wrong character set, i.e. if moving server etc. You would need to specify --default-character-set=utf8mb4 when running mysqldump.
It is irreversible, you cannot restore the now corrupt emoji data.

Love this! 
I do tend like the idea that we could send someone a friendly reminder to finish their purchase if they abandoned it. But maybe as a PM versus an email. 
I also can see why we wouldn't necessarily want to create an invoice if the user has not finished the purchase process. 
👆 I tend to agree. 

I would recommend blocking unwanted traffic at the server level. By the time the request makes it to PHP, a lot of unnecessary overhead has already occurred if your intention is to block the traffic. You can already ban by IP address if you wish, and most legitimate spiders will advertise the IP address ranges used by their bots if you wish to do that, but again...this is better served at the server/firewall level.

Solved. I just must add to curl request CURLOPT_USERAGENT option....
and @Linux-Is-Bestthanks for your time

Hello again, @Zdeněk Tůma
I regret to inform you that I and perhaps others here are not seeing the full picture. It could be a good indicator of why no one else has chimed in.   When I originally took it upon myself to provide you with some peer to peer assistance, you had written that your IP might have been blocked.
 
I see you have edited your post to correct that, but the other half of your post continues how you used different IP addresses, which I presume you would not do unless you had good reason to suspect an issue with your initial IP address.
You said you use Cloud IPB?  To answer the original inquire, 'what should you do?'  I advise you strongly to continue to work with support in resolving this issue.  And in the future, when asking your peers to help you, please be as forthcoming as possible.

Your CDN (content delivery network), Amazon Cloudfront, should have a simple method to purge your stale (old) content. You may wish to double-check that you have not banned or otherwise blacklisted any IP addresses via your server. If you are using managed hosting, you may want to check with your hosting provider. If you are using a proxy DNS service, such as Cloudflare, you may wish to double-check this too (I know you have not stated that you do, but I figure I toss that one out there just in case).
Failing all this, I would suggest you hire a system administrator.