@boomzilla, Congrats on your "Gives Back" badge!
And you seem to be Appreciated and Respected
@boomzilla, Congrats on your "Gives Back" badge!
And you seem to be Appreciated and Respected
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
I look forward to those shipping, so we can read here about how they randomly publically expose Whispers.
I have no idea exactly what type of themes are being built, so yes, it is possible to do that. I'd bet more on pieces of those themes constantly breaking due to rewrites of the topic listings, post output, widgetizing items, etc. But, that shouldn't come to be too much of a surprise. It took several months before someone realized the "solved" class is no longer on the post that was marked as solving the topic.
Mission Accomplished! They are adding it to core again.
https://meta.discourse.org/t/logout-menu-item/32731/28?u=cpradio
Since Jeff closed the prior conversation, I only made the plugin to help them realize how many actually wanted it.
I'm not paid... lol, this is only going to get worse for me from you guys now isn't it...
Interesting. I'm sure whatever platform you "formally" choose, will likely be put to a wonderful stress test that will show glorious failure. I just hope they are more open to your testing styles than your former platform of choice (no one chooses Discourse, Discourse forces you to choose it and then laughs)
And a touched by an angel badge here at home.@cpradio DO IT!
Oh, I already knew that (that it affected Meta). I had an eerie feeling it was a bug. In fact, I had to warn SP not to upgrade anytime soon as there are too many issues right now with upgrading (way too risky). (yeah, I know, you all already are aware of that)
I only had two goals, 1) express why it needed to be added back, when that quickly failed and got closed/archived before I could return to add any more info, I went with 2), produce a plugin that gained a lot of attention and traction that hopefully lead it to being introduced into core (again).
Granted, I'm sure it is off by default, but nonetheless, it is a small victory.
sigh Core's functionality actually doesn't work, PR submitted (I'm glad someone tests these things... lol)
Merged, all better now
@JBert said in How can this be so wrong??? (AKA the Discopocalypse thread):
Cheers to @cpradio for making issue tracking more "social" and "community-oriented" (my words, not his)!
Eh. I'm sure someone out there has a reason for its existance, isn't and wasn't my place to figure that part out. I was simply asked to design, architect and build it. So I did :)
What do you get out of it?What even is "site point?" It points at sites, I guess?
Free access to their books, content, their Learnable System (which is now called Sitepoint Premium). I could also write articles (and get paid for them) with little obstruction, if I had any desire to.
You're a fucking mug, is what you are. Sitepoint are a commercial outfit. You're spending your personal time making their product better, making them more profitable, with no benefit other than "making the rest of the personal time you're sinking into their business less hellish". Jeffco are a commercial outfit. Again, you're spending your personal time making their product better.Giving time to open source projects I can understand, even if (for example) fixing a driver for linux indirectly benefits RedHat. But directly sinking your time and effort into someone else's business is just plain stupid.
Walk the fuck away, man.
^ See above, I do get things out of it, including random swag from time to time, it would be similar to providing a site with stories of unbelievable situations that happened to them in the technological workforce, or screenshots of crazy error messages, that the site will run with ads to profit from.
I know it is far fetched, but right now the time I put in, to the items I get in return, are still worth it, when that balance changes, that's when I'll have to reconsider my involvement.
Plus, it doesn't even impact my full time job and I can do these things at my full time job (it is encouraged... so win on both -- since I still get free access to a library of books, videos, free swag, etc.).
@Lorne-Kates said in Oh, Discourse …:
You may want to check again.
And again in a few minutes after that.
And hey, maybe, since you'll have to keep checking over and over again, you might as well set up something like Server Cooties to know exactly when it goes down.
Not if. When. And how often.
Nah, experience so far is it takes a lot to kill a Node.js server. I put it through the paces, it is built to handle internal failures when communicating with GitHub and Discourse. When I went to launch, GitHub unexpectantly went down for several hours, which made things a bit interesting.
@Jaloopa said in Oh, Discourse …:
@accalia yeah, but servercooties isn't integrating with Discourse. I predict this service will break roughly every couple of weeks as Discourse randomly changes database schemas, output format and API endpoints.
Yeah, that is probably the best and biggest concern. The Node.js code is pretty solid, but its integration with GitHub and Discourse quickly became overly complex and should those endpoints stop working or cease existence, it won't be easy to resolve.
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
I look forward to those shipping, so we can read here about how they randomly publically expose Whispers.
I have no idea exactly what type of themes are being built, so yes, it is possible to do that. I'd bet more on pieces of those themes constantly breaking due to rewrites of the topic listings, post output, widgetizing items, etc. But, that shouldn't come to be too much of a surprise. It took several months before someone realized the "solved" class is no longer on the post that was marked as solving the topic.
@aliceif said in How can this be so wrong??? (AKA the Discopocalypse thread):
@cpradio You work for Big Discourse now?
Yes and No? I'm not "staff" more like a consultant hired to fulfill projects a customer wants or desires that the team itself does not have immediately availability for (hopefully that makes sense).
It is my understanding, there are a few of us that are doing these odd and end jobs, another is one that I know of is creating multiple themes that can be shipped out of the box.
@HardwareGeek said in Oh, Discourse …:
So you're saying we should blame you, not Jeff?
I guess you can... I was simply told they needed a system that did X, and when I asked all of the general questions I would for gathering requirements, they pretty well let me choose my own route. It runs on Node.js, for those interested.
@Lorne-Kates said in Oh, Discourse …:
Or if it worked.
Fairly certain you are poking fun, but last time I checked, it still worked...
@JBert said in How can this be so wrong??? (AKA the Discopocalypse thread):
Cheers to @cpradio for making issue tracking more "social" and "community-oriented" (my words, not his)!
Eh. I'm sure someone out there has a reason for its existance, isn't and wasn't my place to figure that part out. I was simply asked to design, architect and build it. So I did :)
Eh. What do I care? It was a job, I don't ask why so long as the money clears :)
I do have to say that the Discourse Team was pretty laid back with the project. They didn't really care what language it was in or how it worked, so I got to architect the whole workflow in the language of my choice.
@boomzilla, Congrats on your "Gives Back" badge!
And you seem to be Appreciated and Respected
NodeBB remembers your unread posts across different devices.Â(I don't mean to pick on you specifically, @Mikael_Svahnberg, but I'm tired of having to say this).
I whole-heartedly endorse this statement (so long as you enter the topic at the beginning).
Yeah, I see how it works now. And it carried over to my tablet too, so it isn't per device either, once I knew what to look for and how to invoke it (which was by far the more confusing aspect).
I think you are wrong here. I've been testing it and I can tell you for a fact NodeBB does not maintain the post I last read in a topic. So if I join a topic with 20 posts, and I read the first 5, when I return, even using the same session, I can go back to the beginning or to the end, I can't got to post 6.
Okay, so I've been playing with this for the past hour and now finally it starts to show a popup (bottom right corner) saying I can jump to the last unread post after I enter a topic at the beginning again. But I have to enter it at the beginning again for it to popup versus it just taking me to my last unread post immediately.