:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
-
-
-
said:
Based on your previous topic, it looks like you are not running a docker based install and are thus using an unsupported install, and trying to hide that fact from us?
I've missed Jeff's special brand of customer service
said:
@codinghorror - trivial outputs were dismissed as I’ve confirmed all these points (plenty of diskspace using a 16GB disk, swapfile of 2G enabled).
FYI, im not hiding anything.
Steps taken to install ? ubuntu 16.04 aws small instance (as tiny was failing due to 1g ram).
1- git cloned project - https://github.com/discourse/discourse
2- created and updated app.yml to meet my install needs- using local redis (docker)
- using remote DB (RDS)
3- ./launcher build app
4- ./launcher rebuild app (several weeks later)>This all works with a running docker instance build from launcher script. The only point that the processes add up to 1 GB RAM consumed.
That's a swing and a miss then Jeff
-
@doctorjones said in How can this be so wrong??? (AKA the Discopocalypse thread):
aws small instance
Not digital ocean, therefore not supported
CLOSED
-
@doctorjones said in How can this be so wrong??? (AKA the Discopocalypse thread):
said:
Based on your previous topic, it looks like you are not running a docker based install and are thus using an unsupported install, and trying to hide that fact from us?
I've missed Jeff's special brand of customer service
said:
@codinghorror - trivial outputs were dismissed as I’ve confirmed all these points (plenty of diskspace using a 16GB disk, swapfile of 2G enabled).
FYI, im not hiding anything.
Steps taken to install ? ubuntu 16.04 aws small instance (as tiny was failing due to 1g ram).
1- git cloned project - https://github.com/discourse/discourse
2- created and updated app.yml to meet my install needs- using local redis (docker)
- using remote DB (RDS)
3- ./launcher build app
4- ./launcher rebuild app (several weeks later)>This all works with a running docker instance build from launcher script. The only point that the processes add up to 1 GB RAM consumed.
That's a swing and a miss then Jeff
I've dealt with people like what Jeff suspects here. I think they've been on the front page too. Until you've actually verified relevant command output, you can't take what they say for certain. Especially if they refuse to give output "because they checked it".
-
@pleegwat But there's a difference between the correct way to go about it, and the way.
-
@raceprouk
I'm not convinced the way isn't the right way, when you're dealing with self-appointed "Tech Geniuses" who are ignoring your requests for the information you need in order to help them.
-
@izzion That depends on whether you're giving off signals to paying customers.
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
@raceprouk
I'm not convinced the way isn't the right way, when you're dealing with self-appointed "Tech Geniuses" who are ignoring your requests for the information you need in order to help them.It's possible that this guy has been a PITA elsewhere on meta.d. There was a mention by the OP about some other thread. But except in extreme circumstances, "do this or GTFO" is just wrong, period.
I've made comments like, "You need to do that stuff before I can answer anything else." As several people did, though I also winced when one of the discodevs pulled a when the guy asked what else he needed to answer and he said, basically, "It's up there, I'm not going to repeat it." Because I read it as the guy having good faith believed that he'd answered the questions.
Of course, OP's communication was not great, because his answers were sometimes of the "It's not relevant because $x." But without making it clear what he was attempting to answer. In particular I'm thinking of when he talked about the DB being on a different machine.
-
@izzion If we were talking about some random GitHub project with about six users, that may be the case. However, Atwood is the head of a business, and his actions reflect on that business. As such, he should be holding himself to a much higher standard than he actually is.
-
@pleegwat
True. Though I would put forth that 's target paying customers are business decision makers, most of whom are (1) not going to be visiting Discourse's technical forum and (2) are used to the tech geek that stands athwart the business shouting NO! over some asinine technical BS. So even if they do get pointed to that thread, they're going to empathize with Jeff's approach anyway.
-
http://thedailywtf.com/articles/open-sources
Here's another way open-source works: A group creates a product. They decide to avoid the above PR disaster by using some off-site bug tracker. Someone files a bug. Then another bug. Then 5 or 10 more. The creator goes on a rampage, insisting that everyone is using it wrong, and deletes all the bug reports, banning the users who submitted them. The product continues to gain success, and more and more people file bugs, only to find the bug reports summarily closed. Sometimes people get lucky and their reports will be closed, then re-opened when another dev decides to fix the problem.
-
-
Announcing Discourse-Math, for when you need 2+2 to be 5!
All of your calculations will be 500OK! :-D
-
@doctorjones Wonder how long that will last?
https://what.thedailywtf.com/post/639868
Maybe they made better decisions than this guy, though:
-
Check this out, they made a new Emoji picker for
The interesting bit for me is the now closed "open issues"
Clicks are be re-bound causing a single click to add multiple emojis (filter to a word, clear filter, filter again, click emoji)**
This one sounds like a lot of fun, how the fuck did that not get caught in testing?
Recently used emojis logic is too fancy, is should just push recently used to the first in the list
I want to know what the fuck it was doing instead of putting the most recently used one to the top of the list.
Clicking inside picker but not on an emoji closes the picker
It's nice to see the devs never change
I wouldn't be surprised if there was a new fa-spin bug in there somewhere ;-)
-
What do you guys think about removing some borders on the search area?
Too much contrast and visual cues. Remove it all!
-
@doctorjones said in How can this be so wrong??? (AKA the Discopocalypse thread):
This one sounds like a lot of fun, how the fuck did that not get caught in testing?
It's on testing, they actually take a long time to put things on their stable branch.
-
@wharrgarbl said in How can this be so wrong??? (AKA the Discopocalypse thread):
they actually take a long time to put things on their stable branch.
I see what you did there ;-) (because )
-
I love that they are debating whether or not to load 1500+ emoji images at the same time, or to do it in batches.
I am wondering why they don't use an image map or sprite to render them. 1500 emoji will take some time to load, even when on HTTP/2.
-
@alexmedia Guess how NodeBB does it
-
@hungrier Absolute rubbish.
-
@doctorjones said in How can this be so wrong??? (AKA the Discopocalypse thread):
testing?
: Testing? What is this testing thing you speak of?
-
@hungrier said in How can this be so wrong??? (AKA the Discopocalypse thread):
@alexmedia Guess how NodeBB does it
Those are OUR emojis.
-
@alexmedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
I love that they are debating whether or not to load 1500+ emoji images at the same time, or to do it in batches.
I am wondering why they don't use an image map or sprite to render them. 1500 emoji will take some time to load, even when on HTTP/2.
Yeah. For some reason it seems almost everyone does it via individual image. NFC why.
-
@alexmedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
even when on HTTP/2
For those who haven't seen the demo:
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
@hungrier said in How can this be so wrong??? (AKA the Discopocalypse thread):
@alexmedia Guess how NodeBB does it
Those are OUR emojis.
I can scroll to a different part of the network tab if you like. It's still 3500 requests for emojicons, all individual images.
-
@hungrier And here I thought emojis were part of the installed fonts and therefore already on the computer, except for the special forum-specific non-standard ones.
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
For those who haven't seen the demo:
HTTP/1.1
HTTP/2You fuckin' kids with your http2 nonsense, just use sprites like your father before you and his father before him!
-
@atazhaia said in How can this be so wrong??? (AKA the Discopocalypse thread):
@hungrier And here I thought emojis were part of the installed fonts and therefore already on the computer, except for the special forum-specific non-standard ones.
Unicode ones (🐶🕴️✴️) are, and those ones depend on the OS + browser + fonts, but forum ones that you type with colons () are images.
-
@alexmedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
I see that the DiscoDevs have found more things to bikeshed, such as the contents of posts themselves...
Ooh, that's special (yes, I know, late to the party, potentially d). What it says before clicking "Show Full Post":
As of today*, it’s been four years of Discourse! It feels like only only yesterday that we launched Discourse as an open source project. We’ve certainly been busy for the last four years: 1 official non-beta release of Discourse 7 total releases of Discourse, currently on 1.8 beta ~600 hosted customers ~8000 public installations of…
What it says after:
As of today*, it’s been four years of Discourse!
It feels like only only yesterday that we launched Discourse as an open source project. We’ve certainly been busy for the last four years:
I’m happy to announce that in our fourth year, we’ve just added two team members:
@falco aka Rafael dos Santos Silva from Brazil
@oblakeerickson aka wait for it.. O. Blake Erickson from Idaho, USA
This brings the total Discourse team size up from 9 to 11 souls.
Where do we go from here? Everywhere! Can’t stop. Won’t stop.
More Discourses, more features, more plugins, more integrations. Maybe throw a few new Emoji in there for good measure while we’re at it. And all of it, always, 100% free and open source for you, forever.
* OK technically yesterday but come on that was a Sunday!
This is a companion discussion topic for the original entry at https://blog.discourse.org/2017/02/discourses-fourth-birthday/46Much of the abbreviated text doesn't even appear in the full post! I'm guessing that little link at the bottom is where it comes from, instead.
-
@hungrier said in How can this be so wrong??? (AKA the Discopocalypse thread):
Unicode ones (🐶🕴️✴️) are, and those ones depend on the OS + browser + fonts, but forum ones that you type with colons () are images.
Feels a bit redundant. Why not just insert the correct unicode character for the ones where there is one?
-
@atazhaia said in How can this be so wrong??? (AKA the Discopocalypse thread):
@hungrier said in How can this be so wrong??? (AKA the Discopocalypse thread):
Unicode ones (🐶🕴️✴️) are, and those ones depend on the OS + browser + fonts, but forum ones that you type with colons () are images.
Feels a bit redundant. Why not just insert the correct unicode character for the ones where there is one?
Some devices may not support those code points. People would shit tricks in the emoji story thread.
-
@atazhaia Lots of reasons:
- more work to implement and maintain two separate processing paths for emoji
- some devices may not support all the unicode emoji
- they would look different depending on the device
- the unicode ones look like shit (subjective, device dependent)
- you wouldn't be able to hover and see the caption
-
I can't shake the feeling that it's a bit stupid, but ok then. I guessed it was some sort of support/compability thing.
-
@hungrier
The last issue can be fixed by rendering a tag around the emoji with a title attribute. That doesn't solve the difference in looks, some emoji look horrible on one platform and look perfectly cromulent on others.Take the drool emoji for example:
On some platforms it looks like someone who has just smelled a fresh apple pie. On others it looks like emoji guy has taken an overdose.
That's why it's better to have a consistent set of emoji.
-
@alexmedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
some emoji look horrible on one platform and look perfectly cromulent on others.
I've yet to see an emoji that looks cromulent on any platform
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
@Lorne-Kates if you're going to use a rainbow flag to represent a gay person, is probably better than "man wearing turban" to represent a jew.
Semitic isn't synonymous with Jewish. It includes Arabs, and many Arabs wear turbans of some type.
-
-
-
@hungrier Spot on.
-
@hungrier said in How can this be so wrong??? (AKA the Discopocalypse thread):
I'm not searching for the post where I chopped your avatar in response to this.
-
Came across this in a random ass-place:
I am amused by the 10 years duration of the curse.
-
reads the small text
So, they've visited the Garage then
-
@raceprouk Worse. It came from tumblr.
-
@boomzilla
So, you found the tumblr account of one of your alts?
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
@boomzilla
So, you found the tumblr account of one of your alts?You'd think a man like @boomzilla would keep track of such things. But ever since he threw them off his lawn...
-
@sloosecannon said in How can this be so wrong??? (AKA the Discopocalypse thread):
keep track of such things
Maybe a nice Excel file could help ...
-
@hungrier said in How can this be so wrong??? (AKA the Discopocalypse thread):
you like. It's still 3500 requests for emojicons, all individual images.
Also, it crashes since browsers. I've suggested only loading the visible ones, but I'm not Web Three Point Oh enough.