:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
You should serve ads for placeholder avatars instead of colorful letters!
-
Look at what very important feature is getting implemented now!
I'm sure glad they're spending all of their dev time on the important stuff!
-
Roboto looks like shit. Also :color_variation_infinity:.
-
Disabling all extensions brought the avatars back. I checked the settings for all of them and to the best of my knowledge they shouldn't be blocking anything. Except they are. At least I know it's my browser's fault now.
As a bonus browser issue, when I restarted Firefox to disable and re-enable the add-ons, this happened.
Trying to like the post again gives me the "You are not permitted to view the requested resource" error. Refreshing the page fixed it.
-
Found the culprit. I made the mistake of assuming this topic had loaded avatars the last time I checked.
@riking, if the Discourse devs want to keep using avatars.discourse.org to serve avatars, they should report the blocking issue here so it doesn't cause issues for anybody else. Even so, this is another argument against the current setup.
-
I'm sure glad they're spending all of their dev time on the important stuff!
I don't see the problem. There's only 26 letters which need to be changed to the new font. Should take an intern an hour or so to render them out in the new font. Job done.
-
I have literally never seen so much useless effort
-
I dare you to go to meta.d and tell them that!
-
@mrguyorama said:
I have literally never seen so much useless effort
I dare you to go to meta.d and tell them that!
@mrguyorama has shown that he can identify useless effort so presumably he's not going to do that.
Jeff's moderation technique of stifling all dissenting voices is effective. How many times do you get a constructively critical post disappeared before you decide not to bother?
This is obviously not a useful way to run a business. Ignoring bugs doesn't make them go away. Moaning that older phones can't run your bloatware doesn't make your code any better.
The whole thing of having a third party cottage industry hand-tooling artisanal single letters on a coloured background is typical of his design ethos: I am the best, this is the way I decided to do it therefore it is the best way to do it.
-
Look at what very important feature is getting implemented now!
Changing avatar font to Roboto
What's wrong with you? Can't you see that this is an important thing to spend resources on. Take a look at the evidence...
The old (frankly, hideous) font
Roboto old (an improvement but still lacking a certain something)
New Roboto (AWESOME!)
-
@, post:652, topic:51117 said:
...Roboto font is quite the mallard's testicles...
I assume someone incorrectly heard 'dog's bollocks' as 'duck's bollocks'
-
-
Well, I'll admit you one thing: That third A is the only one that's in the center of it's ball.
-
Well, I'll admit you one thing: That third A is the only one that's in the center of it's ball.
This is actually a beautifully accurate metaphor for the Discourse Development team's modus operandi; they spend all day playing with their balls.
-
I'm sure glad they're spending all of their dev time on the important stuff!
Standard Discodev priority. Multiple bikeshed trips per actual bug fixed.
-
Also,
passes with a hue difference of 508, but
fails with a hue difference of 500. Can you even see a difference in color between them?Yes. The top text is slightly yellower.
I can't.
ยฏ\_(ใ)_/ยฏ
Practice more.
Filed under: Yes, I really can see the difference
-
Standard Discodev priority. Multiple bikeshed trips per actual bug fixed.
That's a lie, bordering on libel in fact. The least you could do is apologise to the guys over at meta.d who are sweating blood to iron out every last bug in the product. It looks as if they've got a couple of devs tracking down an of centre "B".
-
It looks as if they've got a couple of devs tracking down an of centre "B".
The bikeshed has no chance...
-
The bikeshed has no chance...
Especially given that one of the posters analysed the "B" and decided it was centred, but doesn't look like it due to an optical illusion.
Some of the bikeshedding you look at and think that, while unimportant, is actually "a good thing". Some of it you wonder whom it appeals to but can still see the underlying reasoning behind it. But this... does anyone* actually in any small way give a single fuck about these avatars??!?
*Apart from the obvious.
-
Especially given that one of the posters analysed the "B" and decided it was centred, but doesn't look like it due to an optical illusion.
They've got their best people on it.
-
-
Especially given that one of the posters analysed the "B" and decided it was centred, but doesn't look like it due to an optical illusion.
I like to think that some of their devs are trolling them from within. Think about it, if you can keep the team continually spinning their wheels with this rubbish, then there's less time for them to cause harm in other areas.
-
-
fa-spinning avatars?
Can this be made a thing in the WTDWTF stylesheet? Who should I try and bribe to make it happen...
-
I wrote a userscript - pretty easy with jQuery.
-
-
-
A userscript is no good in this case. You need everyone else to "enjoy" them too, by default!
-
Interesting discomagic...
Apply
$(".avatar").addClass("fa-spin");
on a page, the navigate in discourse. Your avatar in the top right keeps spinning...
-
on a page, the navigate in discourse. Your avatar in the top right keeps spinning...
Because simply left-clicking to navigate doesn't actually replace anything in that blue bar at the top.
-
-
I figured that was probably the case. It is just fun to navigate round with my avatar getting dizzy up there though. There should be a preferences option for it...
-
Personally, I like the name Disco Horse. Especially when I imagine how the logo will look like.
Maybe we could get a celebrity endorsement from Sarah Jessica Parker
-
That's homophobic.
-
-
@Lorne_Kates said:
That's homophobic.
Which one is gay? Sarah or the horse?
It's obviously a bash on gay people. Gay people are insulted as being "the same as bestiality", and the you post a picture of that dude giving "fuck me" eyes to a horse.
-
Dogfood ALL THE THINGS!!!
-
Did... did they just reinvent mailing lists? Using Discourse?
-
Discourse: the fully discofunctional CRM that's also coincidentally a forum!
-
avoid confusing the main owner
If jeff would stop doing it wrong he wouldn't be so confused
-
"Do all things, and do them badly".
-
Oh this is brillant!
Additionally, if we automatically create accounts there is are quite a few side effects:
We start sending digests to the users User becomes "part" of the site unwittingly. They can be mentioned, searched and so on.</blockquote>
"As soon as someone emails us for support, we can start spamming them with shit from a forum they never joined. I don't know what the word unwittingly means, so I'll just assume it has a positive connotation. And hey, they can be mentioned, so they can get EVEN MORE SPAM from shitposts on the forum, and people literally spamming them by abusing our software!!!!"
I love how it will auto-generate an account for them. Who wants to bet:
- The email address will somehow be linked to the account
- That email address will be leaked, since the support thread is public, and they are now "part" of Discourse
- This will fuck up miraculously when someone emails in from hasplus+inemail@example.com, or any other airquote "not standard" address.
- It will still fuck up, and start silently creating a new account on each subsequent emailed support request. Or reply.
And then even better, in order to receive the replies-- even though Discourse is spamming them to hell with notifications and mentions-- they'll have to log into Discourse to get their answer. Which leads to
As it stands if you try to register with an "inactive" account we will prompt you with confusing warnings. We will add another flag to users to explain this "inactive" account was in a "staged" state.
Whaaa.... so they are intentionally prompting people with confusing warnings-- and that's a good thing? So let's make it more confusing by calling it "staged". And then not allow them to register? Or will there be some sort of "we'll send you a password reset link" message?
OH and who wants to bet the new accounts will be created with an easily guessed password, and will be hacked in a day?
Staged inactive accounts need to get email notifications for any replies to messages, but nothing else
Contrary to what was mentioned above. I'm sure Discourse will implement this feature perfectly and not accidentally spam support users with a ton of shit. I mean just look at how well they handled Whispers.............
Emails we send usually include various links to Discourse, if clicked by "staged accounts" they should first funnel through an onboarding process, where a user is presented with the sign up form.
So, like, we'll create a SECOND login, signup and email process that you'll have to maintain separately. That way we'll have two processes to fuck up!
Notifications
At the moment the only type of notification a message can generate is a "green bubble" notification. This is the strongest type of notification in the system. The green bubble will not go away until you visit a message.
This behavior is highly undesirable for a support team, only the assigned "supporter" should be disrupted in this way.
Instead we will allow notifications on messages to be standard blue notification IF the user is not in the "topic allowed user" list (and instead has implicit permissions due to group permissions)
We already have too many random numbers and colors all over the place. Let's add more.
And treat them differently, so now when you click on the notification bubble, the actual result will be even more RandomRandom
Support categories will be suppressed from the category selector, if we leave it there it can quickly cause confusion and force us to implement messy migration of messages to non message categories etc.
Even more special handling. Let's do this with a flag rather than some sort of ACL. And hey, even WE don't like Jeffing things. It's "messy".
Search
Message that have a category set should show up in search IF the user has permissions on the category and category is not suppressed from latest. Otherwise they will need to explicitly search in the category to see the messages.
Hey, did someone say our search logic wasn't messy, slow and inaccurate enough? How about MOAR SPECIAL CASES? Yay!
Suggested topics changes for Messages
MOAR MOAR MOAR SPECIAL CASES !
Whisper changes
In the context of a message in a support category, whispers should be visible and usable by all users who have access to the support category. This means that in some cases non-moderators may have access to the whisper feature.
Whisper isn't broken and shitty enough. Let's further complicate it with non-moderator access, to hear whispers from unregistered users, in a secret category, with a special branch in search, and completely customized logic for notifications.
THIS CAN'T POSSIBLY GO WROGN!
And it took less than 48 hours for bikeshedding to begin:
@Sam said:
Perhaps just known as a "staged account" or "provisional account" going forward?
Yeah, I like "staged account" ... the word provisional has a fair amount of loaded meaning around it.Oh, and lol because already the cracks are showing:
Here's a question - what happens when the user with the provisional account replies via email and cc's their coworker(s)?
Would be great if that added the cc'd users to the message (and potentially confusing if it didn't)....
Yes, we're already creating accounts and spamming people-- let's also create accounts and spam people who didn't even request an account. I'm sure that's legal and won't cause any problems.
Okay, so maybe they should treat users who were CC'd on the message as different special accounts "provisional staged included" accounts. Just add yet another branch of logic for them....
:for_fucks_sake:
-
-
-
Did... did they just reinvent mailing lists? Using Discourse?
Not really. They do seem to be wearing the Complicator's Gloves though.@Lorne_Kates said:
As soon as someone emails us for support, we can start spamming them with shit from a forum they never joined.
@Lorne_Kates, you usually make some good points but this post is full of crap. 80% of the stuff you're complaining about is the parts where sam is saying "it would be bad if this happened, so we need to make this list of changes to stop it happening."I agree, the automatic account creation from email is likely to fail in at least one or two amusing ways, and the whispers stuff will probably be as fragile as... well, as whispers are now.
-
"it would be bad if this happened, so we need to make this list of changes to stop it happening."
Yes and we all know how competent they are at actually preventing it from not happening and closing all back doors, loop holes and edge cases.
-
the whispers stuff will probably be as fragile as... well, as whispers are now
whispers are still marked as experimental in settings
-
80% of the stuff you're complaining about is the parts where sam is saying "it would be bad if this happened, so we need to make this list of changes to stop it happening."
And you're assuming:
- Jeff will agree these are bad things
- Sam will actually implement ways of avoiding those bad things
- Someone will QA those checks against bad things
- Someone else will fix all the bugs that are found when QA checks the shitty code
- It won't just be thrown together over a weekend and dumped into production and used wrong
-
-
@Lorne_Kates said:
3) Someone will QA those checks against bad things
Yeeeeeah. Didn't they fire their QA department recently?