Site/Off-Topic Discussion Thread

Episode IV: A New Boogaloo

Quote# 125041

Let's talk about the site and other things!

Post feedback, issues, random comments, death threats, etc. here like in all the other Site/Off-Topic discussion threads.

Site/Off-Topic Discussion Thread 4, Brought to you by The Power of Triangles 247 Comments [3/1/2017 4:11:18 PM]
Fundie Index: 0
Submitted By: shy
Username:
Comment:



1 2 3 4 5 10 | bottom

Mister Spak

@SpukiKitty


"I have this burning question that I can't find answered anywhere....WHY CAN'T THE DUMB IDIOT MORON BIG OIL BUNCH JUST MAKE THE SWITCH TO GREEN ENERGY?"

Because they're making $zillions just fine with black oily energy.

3/16/2017 8:17:15 AM



-72 hours remain-


You mean the moon is gonna fall and kill everybody? Oh no.

Seriously though MM is the best Zelda because it doesn't use the tired old cliche damsel-in-distress trope. In Majora's Mask you are actually fighting to save the world, not for the prize of an objectified woman/girl. Compare this to the new BotW where Zelda needs a man to save her yet again. And of course the (mostly male) reviewers give it perfect scores despite the blatant sexism.

I think the problem with the series is that it bears Zelda's name. Seriously if it was called the Adventures of Link instead they wouldn't always have to include the distressed damsel cliche. But if they can't find something better for Princess Zelda to do instead of being a damsel-in-distress forever, that series is best left to the dustbin of the 80's.

Sorry, rant off.

3/16/2017 1:13:40 PM

shy

@2031282: I love Majora's Mask, and when SSTDT opens in a couple days, I'm prolly gonna be dancing on the moon as it comes crashing to Earth. MM is still my favorite Zelda game because... everything you just said. I also like Link's Awakening for mostly the same reason. It also had a lot of fun bugs.

TBH, even though that shit is still sexist, Zelda's kidnapping has gotten so bad it honestly doesn't even feel sexist to me anymore. It feels more like she keeps getting kidnapped because she's just a stupid bitch spaced out on drugs. (To me, she acts more and more like she's strung out on sedatives and dissociatives with each game. But it's really, especially bad in Skyward Sword. Seriously.)

3/16/2017 3:13:19 PM

pyro



line-height needs some tweaking on large font sizes.

3/17/2017 6:25:49 AM

dxdydz

Could we get something about post formatting on the FAQ page? As in something that would explain how to embed an image in a post, create a link, etc.

I've seen some quote submissions where it looks like the submitters didn't know how to do these things and I've seen several older comments where people had trouble figuring it out.

3/17/2017 7:58:02 AM

THX 1138

Happy St. Patricks Day, everyone!

3/17/2017 6:48:10 PM

shy

@pyro: Fixed. (I thought I had already fixed it, but I noticed another rule specifying the wonky line spacing. The CSS file is a mess, but it was already like that before I got my hands on it. Still not an excuse for me not fixing the fact it's a mess, though. I'll try to get to that with the next round of updates and hopefully get around to bringing somebody on board to help me out with things like this.)

@dxdydz: That's crossed my mind several times, but I keep forgetting about it. I'll try to add something covering the basics of YsCodes to the FAQ with the SSTDT update, but I can't really cover everything because it'd be a FAQ in itself. There's a ton of little minor 'undocumented' things, or at least 'undocumented' insofar as I haven't mentioned them and nobody seems to have discovered them. For example, you can use [em] and [strong] instead of [b] and [i]. You can also add [aside]s, insert preformatted blocks of text (e.g. for displaying code), and center lines of text. (The name of the tag for that last one should be obvious enough.)

@THX 1138: Back at ya!
_

Sorry for the delay getting SSTDT going. I'm mostly going to take a break from coding today after spending most of yesterday and the better part of my free time the day before working on code for both the SSTDT update and the 'rewrite.' Everything needed for SSTDT itself to function is finished, but there are a few more things I want to polish up, put the finishing touches on, and test. They're a part of FSTDT code update that will accompany the grand opening of SSTDT: there's nothing earth-shattering or ground-breaking, but it actually has quite a few changes and new things you can see and use instead of just the usual backend code changes I usually ramble about!

(Those earlier changes were needed to make the code manageable enough to work with and make 'meaningful' changes to it. And that's why the site's code underwent several rounds of backend code changes before I did anything significant you guys could behold for yourselves. See, I wasn't just sitting on my ass pretending to be productive!! Though I still know most of you don't give a fuck about stuff like doing blah-blah-blah to the database or writing yadda-yadda-yadda to do something that's cool from a technical standpoint but users can't actually appreciate yet, nor do I expect you to care, but if you do, that's awesome.)

Edit: Moved the second part of this comment to a separate Shy Says post because it strayed waayyy too far off-topic.

3/18/2017 2:16:26 AM

shy

Good fucking God, why is the host's database server so SLOW?? I've had more than enough of this. I am definitely moving some of the simple shit to a JSON quasi-database that doesn't require the DB server.

I'll start keeping a running list of things to be done before SSTDT as I complete them. Might be a little vague or cryptic because I don't want it to be too spoilerrific. Much of it is going to be going back and double-checking and testing to make sure everything is in place.

DONE: Updated a stored procedure in the database pertaining to the Top 100.
DONE: Checked stored procedures to ensure that an ArchiveID 0* doesn't make them have a mental breakdown.
DONE: Deleted everything in Archive 19 / MZSTDT used for testing.
DONE: Found and fixed an unrelated bug in the stored procedure for searches. Search page should be a tad faster now.
DONE: Uploaded new old-school front-page header font.
DONE: Updated the CSS file to add a @font-face for the header font.
DONE (..hopefully??): Double-checking other stored database procedures to make extra sure they are SSTDT-ready.
DONE: Clean VS solutions for a recompile.
DONE: Release build recompile: DataAccess.vb
STOP: Release build recompile: ctlQuote.vb, ctlComment.vb. CtlQuote.vb is not compiling.
DONE: Flagged ctlQuote.vb. Identified problem: shamefully forgetting to finish half the changes to it and look into why something I wanted to try wasn't working.
DONE: Tested not-working thing in ctlQuote.vb in a nonce project. Error. Error. Error. Error. Still error... Completely different error. A ha!!
WHAT: I can do that ??? lol not if I want to maintain what little sanity I have
UNEXPECTED SWERVE: Major unplanned additions and changes to the custom templating engine to work with the completely, uniquely stupid way Distind did the quote control's rendering with 50 jillion Response.Output.Write() calls. See here for updates and progress on that and "watch" me make something live.
DONE: Put placeholder code and comments in the PreRender and Render events of the master page. UNDONE
DONE: Quick-and-dirty hack in the form of yet another Response.Ouput.Write() to ctlQuote.vb's rendering output that inserts a Chr(7) (the ASCII "bell" control code, appropriately enough) to act as a sentinel signalling the presence of unparsed templating parts. UNDONE
PAUSED: Work on the Unexpected Swerve Unexpected Double Swerve
DONE: Implemented dynamically generated search links in quote information using ParseToOutput() + template fragments to
IN PROGRESS: Finishing ctlQuote.vb

*Where the misc stuff like these S/OT threads are going and the old Shy/Distind Says posts are going to be archived for the time being.

3/18/2017 11:29:16 AM

dxdydz

Glad to see that things are chugging along on the site. Also, I'm building a new toy.

3/18/2017 12:24:30 PM

shy

Okay, round one of testing on my part is done.

Unfortunately, there is absolutely nothing interesting to see this time, just testing the stuff to make that possible right now. The site will probably be running a little slower than usual because this is a Debug build compiled with all the debug symbols and such bells and whistles. Errors should now tell which source code files, variables, classes, functions, etc. are involved and also include more offending source code than the basic stack trace normally in place does. Also worth noting is that I've given several variable and function names outrageously long / specific names. I get 'vibes' about them and suspect they are likely a potential source of problems. I don't normally use ridiculous identifier names like ParamsRecentPostsFromIPAndUserAgent, and those will be changed back to something reasonable like Params when I'm done testing. (Params isn't very useful when you have 20 or 30 functions / methods with variables using that name.)

Please be on the look out for bugs! If you get an error, and the message mentions a file as described below, please email me a full copy of it at admin@fstdt.org:

Anything that ends in .vb as opposed to .original.vb: Seeing the latter is an indication I've rolled something back, most likely to test something else. I'm not really concerned if the .original.vb files cause problems. It's to be expected with mixing new and old code. Anything ending in .cs or containing code that looks like, well, C# is a double rollback.

References to compiled binary files to be on the look out for

DataAccess.dll : the changes to this are nearly or equally as extreme as those I made last time when I gutted unused crud from the database. this time, extreme change is almost entirely from using the next library to very drastically reduce the amount of boilerplate code (its filesize is now seriously less than half of what it previously was—and that's with debugging symbols enabled which beef up the size of binary files quite a bit.)
DataUtils.dll : new
ForumObjects.dll
MainPageObjects.dll
STDT Rebuild.dll (If you see just STDT.dll, that means I rolled back the parts of the new build I've rolled out in the main code file. Again, because it had to be updated to work with changes to the other files, I'm not very concerned if I do a roll back and STDT.dll crashes. Hell, I'd be surprised if it didn't.)

I'm not really concerned about any of the other compiled binary files yet, because they aren't affected by the changes I have rolled out so far.

I will really, really, really appreciate your help!!

One more thing: Lights will probably be out again for about an hour or so around 3:00 PM EST. This time you'll see at least a couple of differences when the site comes back up.

3/19/2017 7:04:21 AM

shy



SSTDT IS HERE!!!!

I decided to go ahead and throw it up early before the rest of the stuff. Let me now if you find any bugs with it. Still going to finish the other work I had in mind before opening SSTDT, probably faster too now that I've actually gotten SSTDT off the ground.

3/19/2017 12:23:37 PM

JeanP

@shy:
SSTDT IS HERE!!!!


Thanks you.

Already submitted a quote.

But where is the former SSTDT (for Shy Says the Darndest Things!)?

3/19/2017 12:25:46 PM

shy

@JeanP: It'll be popping up again as a blog in the next week or so, and since it's a proper blog, I'll probably do quite a bit more posting there. I was already planning on doing that, so I gave the old section for Shy Says to SSTDT.

Also, on another note, I got an error for the first time in a while, one with a ridiculously unhelpful message too:

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type 'STDT.Top250'.

Source Error:
Line 1: <%@ Page Language="C#" MasterPageFile="~/FSTDT.Master" AutoEventWireup="true"" CodeBehind="Top250.aspx.cs" Inherits="STDT.Top100" Title="The FSTDT Top 250" %>
Line 2: <%@ Register TagPrefix="Controls" Assembly="MainPageControls" Namespace="MainPageControls" %>
Line 3: <asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">

Source File: /Top250.aspx Line: 1


Change C# to VB and all the .cs files to .vb files, and it works perfectly again. Can anyone here seriously tell me you would have guessed that's the problem by looking at that error information and code? I immediately knew what was most likely happening, but only because FSTDT is all VB all the time now. This in all likelihood managed to happen because I somehow accidentally updated an old copy of the Top100.aspx when I gave it a level up. But that's still not something I would have guessed from that message.

3/19/2017 1:03:53 PM

Pharaoh Bastethotep

So the Top 100s are now one shared Top 250 collection.
I have just finished going through it and moving them to SSTDT where applicable,

3/20/2017 5:16:04 AM

shy

@Pharaoh Bastethotep: The outcome of that was every quote on it being from FSTDT, so I'm probably going to split them again but leave it as a Top 250 and fix the confusing issue dxdydz described in an earlier comment: if you went to, for example, the CSTDT archive and clicked Top 100, you would see the Top 100 CSTDT quotes. But if you were on the page for an individual CSTDT quote and clicked Top 100, you would see the Top 100 FSTDT quotes. There are several ways to fix this, and I'm not sure which one I want to do. Not all of them are mutually exclusive:

1. Split the Top 250 link into four links. This is the easiest but ugliest / clunkiest from an aesthetic and design viewpoint.

2. Make the Top 250 link a dropdown menu you can click, tap, or hover over for links to each section's Top 250 quotes.

3. Simply make the Top 250 link for the page for an individual quote go to the Top 250 page for that quote's section. For this to make much sense in terms of usability, what section a quote is filed under should be put somewhere toward the top of that quote's page. (From a coding point of view, there's actually nothing "simply" about implementing any of this, even though something like it being laborious and confusing sounds more like there's something wrong with the programmer than the platform/framework they're programming on. But a lot of things about ASP.NET WebForms doesn't make any sense, though I do still think there's also a lot of good things that are majorly underappreciated because it's pretty damn old—and definitely out of style in any case.)

4. Change the Top 250 page so it contains links to each section's Top 250 quotes. This is just as easy as the first option and much less offensive from a design standpoint. (Determining what section to display by default is an entirely different can of worms.)

I'll have one or more of these implemented soon.

3/20/2017 9:03:22 AM



Is there any chance of the quote from Femitheist Divine about International Castration Day being restored? I think the previous admin, Distind, removed it because of its ability to attract trolls and because FD said it was "satire." Personally I thought the satire explanation was just an excuse. Just a lame "Oh, I didn't believe that. It was a joke. Really!" kind of thing. Regarding trolls, with the increased moderation the pro-castration trolls, if they return, shouldn't be too much of a problem.

Anyway, the quote's number was #87815. Please restore, as I think it would be the crown-jewel of SSTDT.

3/21/2017 11:56:31 AM

shy

Okay, guys, I'm filing email bankruptcy for all of my email accounts except my faculty email account at work, but that one doesn't concern you.

The email bankruptcy applies to my FSTDT admin email (admin@fstdt.com, admin@fstdt.net, admin@fstdt.org), and since a lot of you know at least one of my personal email addresses, I need to give a heads up that I'm also filing bankruptcy on them too, both my online-stuff email (spikedee@openmailbox.org) and my IRL-stuff email (d***********y@openmailbox.org : replace the asterisks with the rest of my full name). I think I should also probably let it be known that I am not completely batshit insane. My FSTDT admin email addresses are actually just one inbox that has three addresses — not three separate email accounts — all email sent to any of them goes to the same inbox and is accessed from the same account on the host's mail server.

I didn't declare email bankruptcy because I got overwhelmed by the number of emails I had, even if Wikipedia gives that as the only reason for it, so don't hesitate to resend anything if you didn't get a response to it! My FSTDT email gets about 5-6 legit emails a day, and that's well within the limits of what I can handle. (I also get 20-30 of the standard-fare webmaster spam that admin@everydomain.ever gets, and virtually all of it automagically finds itself in my Junk folder where it belongs.) My other accounts get considerably more because I do one-on-one French tutoring and Web development consulting, and my calling broke is actually a much bigger deal for that. If you sent me something and didn't get a reply, then I either didn't get it or the problem that made me start over kept me from seeing it. I always read and reply to every email I receive, even if it's just an acknowledgement that I got your message and read it. Feel more than free to send anything again if I didn't reply the first time. I didn't reply to again, and you'll get a reply within a few hours at the most (well, maybe eight or nine hours now, since it's getting late and I'm about to go to bed).

Anyway, what happened was that I made the mistake of reading and replying to email using the IMAP protocol with three different email clients, two webmail interfaces, and four different devices. The result was that my email was strewn everywhere. None of the devices were anything remotely resembling "in sync" despite that allegedly being one of IMAP's advantages. I can't keep track of what I've read, what I've replied to, what I need to read and reply to, which device a message wound up on, etc. I tried to keep on trucking until I got everything organized, under control again, and with all my ducks in a row. But these ducks are fucking stupid and even don't understand what the concept of a row is. They need to be slapped. And words fail to describe know how close I driving myself completely insane trying not to resort to this.

Moral of the story: Using IMAP with one email client on one device works fine and isn't really any different than POP. Using IMAP with two or three email clients on several devices shows that IMAP does virtually nothing it touts that is supposed to make it superior to POP. Everything would have stayed in sync, and all my devices would have all my email on it if I had used POP.

3/21/2017 8:28:48 PM

shy

@2033315: I'm off to bed now, but I made a note to check and see if it's still in the database in the morning. If it is, I'm totally throwing that shit up on SSTDT. She definitely was not a Poe, or at least not one in the ordinary sense. She was using her primary online identity and everything she said indicated she sincerely believed at least a good chunk of the crazy-ass shit she said.

Edit: ...and now SSTDT Top 250 now has a new crown jewel. actually moved all of Femitheist Divine's standing quotes over to SSTDT. I also noticed that only 3 of her quotes were actually ever "deleted."



3/21/2017 8:37:11 PM

Pharaoh Bastethotep

@shy:
@Pharaoh Bastethotep: The outcome of that was every quote on it being from FSTDT, so I'm probably going to split them again but leave it as a Top 250 and fix the confusing issue dxdydz described in an earlier comment: if you went to, for example, the CSTDT archive and clicked Top 100, you would see the Top 100 CSTDT quotes. But if you were on the page for an individual CSTDT quote and clicked Top 100, you would see the Top 100 FSTDT quotes. There are several ways to fix this, and I'm not sure which one I want to do. Not all of them are mutually exclusive:

1. Split the Top 250 link into four links. This is the easiest but ugliest / clunkiest from an aesthetic and design viewpoint.

2. Make the Top 250 link a dropdown menu you can click, tap, or hover over for links to each section's Top 250 quotes.

3. Simply make the Top 250 link for the page for an individual quote go to the Top 250 page for that quote's section. For this to make much sense in terms of usability, what section a quote is filed under should be put somewhere toward the top of that quote's page. (From a coding point of view, there's actually nothing "simply" about implementing any of this, even though something like it being laborious and confusing sounds more like there's something wrong with the programmer than the platform/framework they're programming on. But a lot of things about ASP.NET WebForms doesn't make any sense, though I do still think there's also a lot of good things that are majorly underappreciated because it's pretty damn old—and definitely out of style in any case.)

4. Change the Top 250 page so it contains links to each section's Top 250 quotes. This is just as easy as the first option and much less offensive from a design standpoint. (Determining what section to display by default is an entirely different can of worms.)

I'll have one or more of these implemented soon.


Could the same also be done for Latest Comments?

3/22/2017 4:14:29 AM

pyro

It doesn't preserve my indentation, shy.

http://fstdt.com/QuoteComment.aspx?QID=125613&Page=1#2033792

3/22/2017 9:26:20 AM

pyro

Two questions:

1. Is the new FSTDT code going to be OSS? If so, then an issue tracker like GitHub would be way nicer than this one thread for suggestions. If not, can we move the issue tracking into the forums? I like the idea of having a separate thread for each issue.

2. In addition to a top-posts-of-all-time, a "Trending 250" section that orders things by combining the Fundie Index and the Recency would be awesome.

3/22/2017 9:31:30 AM

dxdydz

I'm very excited to have this done, so I want to share it with comp-sci peoples. It's an 8 bit computer! Besides the obvious hex displays, it has 16 RAM addresses (each 8 bits wide) and an ALU capable of addition, bitwise or, &, and xor, as well as their inversions. The ALU also supports bitshifting and storage for two constants. The program counter is capable of conditional branching based on how the values in the A and B registers are related.

ROM is organized as follows: rrrrrr|wwwwww|jjj. Where the rs are read address bits, ws are write address bits, and the js control jumping conditions and turning off the machine. When any j bit is a 1 r becomes the ROM address to go to when false and w becomes the ROM address to go to when true. As an example here is the first program I wrote for it which does input1+input2 → display1.

0: 010011|000001|000

1: 010100|000010|000
2: 000001|010001|000
3: 000010|010010|000
4: 011000|000011|000
5: 000011|010011|000
6: 000000|000000|111


The code reads:


0: save input1 to RAM1
1: save input2 to RAM2
2: save RAM1 to regA
3: save RAM2 to regB
4: save A+B to RAM3
5: save RAM3 to dsp1
6: shutdown


Edit: Something is super wrong with the timing controls and I don't have the patience to fix it today. The program I posted here works, but it stops working when it's modified to save A+B to a RAM addressed by a number >3.* And the computer derps up really bad with jumping for some reason.

*Sadly, this may be an issue with the game itself and not an issue with my construction...

Edit 2: How hard would it be to implement something like typing Ctrl+q makes [quote?][/quote?] appear in the text entry box? Same with Ctrl+i → img, Ctrl+s → strikethrough, etc.

3/22/2017 9:47:49 AM

shy

Some car questions from Yahoo! Answers that are so fail I almost wish they had a place here:

Why is the Autobahn still there if Hitler built it?


I don't even know what to say to this.

Why is the speed limit in Canada so high


I foresee a nice mountie pulling you over sometime in the near future and kindly explaining why. Canadians are just that nice.

3/22/2017 10:45:04 AM

KingOfRhye

@shy

Speed limits? They aren't really much higher there than in the U.S....unless someone's actually enough of an airhead to not realize they're not in miles per hour. Wait, that's it, isn't it?

3/22/2017 11:15:38 AM

shy

@KingofRhye: Dude, this is Yahoo! Answers. I'm automatically gonna assume the absolute worst, stupidest, and/or weirdest possibility by default.

3/22/2017 11:34:18 AM

1 2 3 4 5 10 | top: comments page