Anyways, is there anything we can do aside from finishing what we plan to do with the gravatar plugin?
@psychobunny said:
There will be a seamless path as I first mentioned, and it will be officially supported ex markdown, composer etc
@julian and I were discussing and he was unsure how seamless it would be. And since it would be unofficial - what's the plan? Even if it is seamless today, will it keep working and keep being supported? If so, what's the reason for going to a plugin since it was explained to me that plugins would not get support and would not necessarily be reliable (which we've seen as we have to keep switching or dropping plugins.)
What we want is to not lose functionality that we have today. Is that definitely coming someday? What is the commitment to keeping it around?
Whats the problem with gravatar? Whoever is interested in your forum will have time to upload some custom avatar...
@julian said:
This change came about due to repeated requests to remove Gravatar integration due to some privacy and security issues.
It needs to be understood that while there might have been some requests for this, there were also requests to specifically not take this action as well. I feel that there was a reasonable middle ground that only involved changing defaults and not changing functionality. This is where the true concern stems from. The security fix did not require putting functionality into a plugin to satisfy both the security concern customers as well as the Gravatar using / continuous functionality customers.
@exodo said:
Whats the problem with gravatar? Whoever is interested in your forum will have time to upload some custom avatar...
The problem is removing it.
And we have found the latter sentiment to not be true at all. Even very active forum users will do nothing to upload an avatar. Using Gravatar was an important part of that functionality for us.
Also, Gravatar acts as a CDN for many of these forums. Remember that we can't use services like CloudFlare because of Websockets. So having the avatars at a third party was pretty important.
You'll notice, for example, that I have no avatar here even though I took the time to set one up. So the same loss of functionality has happened here. So the theory that people will go back and fix them after having done it one and having them "Just disappear" doesn't hold up even in this conversation.
Also, I thought that Gravatar images were going to be converted to local. But my avatar just vanished?
Okay let's just back up a bit.
and it will be officially supported ex markdown, composer etc
Officially supported, seamless transition. You don't have to upgrade until the plugin is ready. I'm not 100% sure what the problem is? As I said earlier, aside from actually getting this done which we plan to do soon, what else is the problem that we should look into?
Actually I did exactly that
Post GH issues, I'll be happy to reopen if they were unjustly closed and have a second look
@psychobunny said:
Okay let's just back up a bit.
and it will be officially supported ex markdown, composer etc
What's official supported versus not officially supported in plugins? When I asked long ago about this specific process it was made clear to me that any plugin functionality was "use at my own risk." Any, specifically coming up in response to things that "had been core and used to work" and were "now in a plugin that didn't get updated to work with the current version."
@psychobunny said:
Officially supported, seamless transition. You don't have to upgrade until the plugin is ready. I'm not 100% sure what the problem is? As I said earlier, aside from actually getting this done which we plan to do soon, what else is the problem that we should look into?
I'm happy to wait, that's not a big deal. Although I think there should be heavy visibility into loss of core functionality changes - I'd have had no idea that things were expected to break had Julian not IM'd me to stop me from upgrading voluntarily (he knew that we relied on the Gravatars from the previous conversation where I had requested that this functionality not be removed.)
What we have today is that users sign up and get Gravatars automatically. No extra work. We have local avatars disabled as we do not want a mix of things and we do not want to be serving out images from our NodeBB servers. In a seamless transition we would like it if the users do not lose access to the Gravatars that they have now and that new users continue to have Gravatars by default without having any idea that they need to disable them, upload anything, etc.
There are some simple upgrades that we'd love to see... like removing the interface to upload an avatar when the functionality is removed (currently they are confused because they click it and it doesn't work) and instead having a link that takes them to Gravatar instead. But that is all extra and pretty trivial.
What we don't want to see is current working Gravatars lost and/or new users not having Gravatar work transparently without needing to do anything special.
What's official supported versus not officially supported in plugins?
Anything we have removed from core and moved into a plugin (which allows anybody to build their own solution) is officially supported
One example: https://github.com/NodeBB/nodebb-plugin-composer-default
Removing the composer from core allowed us to have the redactor WYSIWYG composer as an option. The idea is that building hooks and making things modular so people can build their own solutions.
As I said on twitter, I understand the frustration, but we're trying to build a solution that makes everybody happy, and we are working on one that makes you happy too. Just keep your thoughts on GH and we will try our hardest.
@scottalanmiller said:
@exodo said:
Whats the problem with gravatar? Whoever is interested in your forum will have time to upload some custom avatar...
The problem is removing it.
And we have found the latter sentiment to not be true at all. Even very active forum users will do nothing to upload an avatar. Using Gravatar was an important part of that functionality for us.
Also, Gravatar acts as a CDN for many of these forums. Remember that we can't use services like CloudFlare because of Websockets. So having the avatars at a third party was pretty important.
You can use cf and websockets. Just set another subdomain with grey cloud only for websockets, its not ideal but it will work fine.
Gravatar cdn is slow++
Removing functions is always bas but i,m sure there will be a plugin for it.
dont need to hurry
@exodo said:
Gravatar cdn is slow++
I'm not saying it is my first choice, just that we don't want to be the ones supplying the images!
Give me Gravatar as an option but an automatic system for plopping them on S3 and I'm all for it.
@scottalanmiller said:
@exodo said:
Gravatar cdn is slow++
I'm not saying it is my first choice, just that we don't want to be the ones supplying the images!
Give me Gravatar as an option but an automatic system for plopping them on S3 and I'm all for it.
We use imgur, speed is similar
Using imgur for your avatars?
You can use Imgur to allow users to upload avatars, effectively using Imgur as your cdn
Okay anyways, moral of the story is:
@psychobunny said:
Okay anyways, moral of the story is:
- If you have an issue, post it on GH so the community can discuss and most often than not we do fix or address it.
On GH and not on the NodeBB community? This is where we've always posted as it is the community. Never understood that you were wanting issues elsewhere.
Here is what avatars look like after an update to 0.9.0 on Gamrhaus which is, more or less, a test community for us..
What theme are you using?
