:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
@Deadfast said in How can this be so wrong??? (AKA the Discopocalypse thread):
this is perfectly adequate!
3.5MB in 10 seconds? I'm impressed, I tell you!
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
@Onyx If a user emails a reply to a topic but the email address doesn't match any registered users so it creates a Staged user, I think?
EDIT: from the DiscoDocs.
Staged
A special placeholder account which is created automatically by the system for email integrationNo email digests are ever sent
Automatically watches all messages it participates in and receives notifications of replies
May reply via email to notifications
Username and Name are automatically picked
Account may still register with the same email and “take over” the staged account.
Forgot password will do nothing …when you attempt to send a password reset to a staged account
Storage: staged field in users tableNothing in there indicates a very important note that explains in response to this bug report:
And for reference in case this goes the way of most Discourse bug reports (or to avoid "infecting" your browser history with meta.D).
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
Over/under on posts until "that's different": 14.5
https://meta.discourse.org/t/how-is-your-experience-with-discourse-mobile/94355
perhaps related: Experience from slow hotel connection
"
We areI am teh awsum for choosing JavaScript forourmy web service. By the way, I can't reproduce your error, so you must be on a really bad connection‡ (or maybe you're lying)."
‡ Like the OP clearly mentioned in his report.Now, correct me if I'm wrong, but aren't modern web browsers able to cache various web page assets to reuse so they don't have to re-download them on refresh or on other pages? So JS would make little to no difference there, right? Or even a negative difference if the JS forces re-downloads every time?
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
with the WTDWTF level support!
https://meta.discourse.org/t/badges-triggered-by-user-post-count/22740
Edit: GODDAMMIT FBSYSTEMNECROMAC
Oops! That page doesn’t exist or is private.
-
@djls45
Yeah, that's been their standard response to threads when the auto-bump unanswered supportthreadstickets feature activates. Because the settings on meta.d are to wait for 4 years after last reply to auto-bump threads that aren't marked as answered.INB4 was trying to program it to do the next month, but rolled his own date implementation and wound up doing a leap year version of next month instead
-
@DoctorJones said in How can this be so wrong??? (AKA the Discopocalypse thread):
@DoctorJones said in How can this be so wrong??? (AKA the Discopocalypse thread):
Here's the best part:
This topic will be automatically deleted in a day.
So nobody else will be able to find this question, see that it's already been asked, and see the non-answer. Let the echo chamber continue!
Wheeeeeeeee!So people can see the actual conversation, here it is for postherity, before it gets deleted.
Note how the question, of how can I disable this (mis)feature?, gets completely ignored, twice.
And the referenced topic:
-
@Zecc said in How can this be so wrong??? (AKA the Discopocalypse thread):
I thought the modern translation of that was "people who live in glass houses shouldn't throw orgies"?
-
@djls45 said in How can this be so wrong??? (AKA the Discopocalypse thread):
Now, correct me if I'm wrong, but aren't modern web browsers able to cache various web page assets to reuse so they don't have to re-download them on refresh or on other pages?
REST is difficult. Lets use Ruby!
-
-
@ben_lubar Ass Weasel! Ass Weasel! Ass Weasel!
-
@CHUDbert Bone Smuggler.
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
We'd have needed to say "ass weasel" more times than Discourse allows. They'd have probably added an Ass Weasel rate limit as a result.
-
@loopback0 Of all the things they could rate limit, that seems to be probably both the most unnecessary and least likely to interfere with any actual use.
-
@loopback0
Ass weasel
-
@Luhmann
You have reached the ass weasel limit
Users are limited to 1 ass weasel per topic
Instead of adding another ass weasel, please consider editing your previous ass weasels.
-
@loopback0 ain't no toaster like an ass weasel toaster.
-
-
@djls45 said in How can this be so wrong??? (AKA the Discopocalypse thread):
"We areI am teh awsum for choosing JavaScript for ourmy web service.
we don't send whole pages over the wire just some JSON... after first sending 2MB of javascript... and also that JSON is the same size as a web page, but unlike a web page, you can't partially render a JSON chunk its all or nothing, so you wait until it's ALL downloaded
-
@Luhmann said in How can this be so wrong??? (AKA the Discopocalypse thread):
@loopback0
Ass weaselYou have earned the trophy
First Ass weasel
-
I noticed this in RuneScape. Same buttons, different contexts.
Seems familiar
-
The DiscoFeature lifecycle:
Hey, us lazy Frenchies get bad search results because we don't always type our diacritics
Oh, yeah, that's an easy feature, we'll flip some database bits and be great. IIIIINNNNNTERN!!!!
The change will be live for 2.1
Uh, so, it turns out that there are LOTS of languages out there, and for some it really really matters if you leave the diacritics out. This change has been reverted, and it's gonna be such a major endeavor to fix this that only a Super Awesome Core Discourser will be able to fix it. Maybe. If we feel like it.
-
@anonymous234 said in How can this be so wrong??? (AKA the Discopocalypse thread):
I noticed this in RuneScape. Same buttons, different contexts.
Seems familiar
Guild Wars 2 has a button to dump crafting materials from your inventory into specialized crafting material storage.
It also reverses the "put all your crap in the bank" vs "put all your crap in your inventory" mechanic that RuneScape has.
People who don't play GW2: how many of those items can you identify without looking them up?
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
People who don't play GW2: how many of those items can you identify without looking them up?
They're all dildos.
-
@blakeyrat said in How can this be so wrong??? (AKA the Discopocalypse thread):
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
People who don't play GW2: how many of those items can you identify without looking them up?
They're all dildos.
Even the battery, the crab, the sword, the spiky stars, and Mawdrey II?
-
@izzion The timeframe is changing LIVE!
We'd rather have this like it was, we're not updating
We'll redo it in 3-4 Discoweeks. For now, give up and get security updates.
We'd rather keep it broken, especially because people are expecting this to just work
We can add it back in 1.5 Discoweeks. With a setting.
It's better incomplete than not at all
If you want it now we can add a setting
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
@blakeyrat said in How can this be so wrong??? (AKA the Discopocalypse thread):
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
People who don't play GW2: how many of those items can you identify without looking them up?
They're all dildos.
Even the battery, the crab, the sword, the spiky stars, and Mawdrey II?
Especially Mawdrey II.
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
The timeframe is changing LIVE!
Disco-gotiation!
-
Can the 404 page use Discosearch not Google?
Google is better than Discosearch
3 YEARS LATER
Discosearch is finally good enough
-
@ben_lubar I see a (spell?) book, a weird cube which is hopefully not from Hell Raiser, and a golden snitch from Picasso's Cubism period.
That's all I got.
-
@topspin said in How can this be so wrong??? (AKA the Discopocalypse thread):
@ben_lubar I see a (spell?) book, a weird cube which is hopefully not from Hell Raiser, and a golden snitch from Picasso's Cubism period.
That's all I got.Icon Notes This book currently has 3 portal scrolls in it that take me to various parts of the desert. This box contains an infinite amount of preserved food and blueprints for siege equipment, but you need to give it badges of honor to get them out. This appears to be a stack of coins with wings holding out a coin in its... hand? Anyway, you use it to summon a temporary merchant.
-
@blakeyrat said in How can this be so wrong??? (AKA the Discopocalypse thread):
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
People who don't play GW2: how many of those items can you identify without looking them up?
They're all dildos.
-
@loopback0 said in [ How can this be so wrong??? (AKA the Discopocalypse thread)](/post
Google is better than Discosearch
3 YEARS LATER
Discosearch is finally good enough
-
@topspin said in How can this be so wrong??? (AKA the Discopocalypse thread):
@loopback0 said in [ How can this be so wrong??? (AKA the Discopocalypse thread)](/post
Google is better than Discosearch
3 YEARS LATER
Discosearch is finally good enough
It's not true for Discourse either.
-
@DoctorJones Discourse search, unlike NodeBB search, actually turns up what I want to see. With a reliability about as good as Google. Not to mention that complex search is done with certain escapes and the search results appear as a drop-down, minimizing the number of times you actually need to navigate to a completely separate page to search, which NodeBB seems to thumb its nose at.
-
@pie_flavor said in How can this be so wrong??? (AKA the Discopocalypse thread):
actually turns up what I want to see.
Pull requests accepted.
-
@Tsaukpaetra said in How can this be so wrong??? (AKA the Discopocalypse thread):
@pie_flavor said in How can this be so wrong??? (AKA the Discopocalypse thread):
actually turns up what I want to see.
Pull requests accepted.
I'm working on getting rid of nodebb-plugin-dbsearch in favor of actual database with non-manually-maintained indexes.
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
I'm working on getting rid of nodebb-plugin-dbsearch in favor of actual database with non-manually-maintained indexes
Poor Ben, straining sewage with his teeth.
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
actual database with non-manually-maintained indexes
Doesn't sound very webscale. It'll never catch on.
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
actual database with non-manually-maintained indexes
Doesn't sound very webscale. It'll never catch on.
The query analyzer thinks we have 3092878113439288612870797836676403532242027679745868562432 posts.
Insert on classify.posts (cost=1165056.13..2727504268273544339764163894701115624938532721346167701504.00 rows=3092878113439288612870797836676403532242027679745868562432 width=229) -> Nested Loop Left Join (cost=1165056.13..2727504268273544339764163894701115624938532721346167701504.00 rows=3092878113439288612870797836676403532242027679745868562432 width=229) Output: (pid.unique_string)::bigint, (NULLIF(NULLIF(topid.value_string, ''::text), '0'::text))::bigint, to_timestamp(((("timestamp".value_string)::numeric / '1000'::numeric))::double precision), COALESCE(content.value_string, ''::text), (tid.value_string)::bigint, (NULLIF(NULLIF(uid.value_string, ''::text), '0'::text))::bigint, NULLIF(handle.value_string, ''::text), (split_part(NULLIF(ip.value_string, ''::text), ','::text, 1))::inet, (COALESCE(NULLIF(bookmarks.value_string, ''::text), '0'::text))::bigint, (COALESCE(NULLIF(replies.value_string, ''::text), '0'::text))::bigint, (COALESCE(NULLIF(upvotes.value_string, ''::text), '0'::text))::bigint, (COALESCE(NULLIF(downvotes.value_string, ''::text), '0'::text))::bigint, (COALESCE(NULLIF(deleted.value_string, ''::text), '0'::text) = '1'::text), (NULLIF(NULLIF(deleteruid.value_string, ''::text), '0'::text))::bigint, to_timestamp((((NULLIF(NULLIF(edited.value_string, ''::text), '0'::text))::numeric / '1000'::numeric))::double precision), (NULLIF(NULLIF(editor.value_string, ''::text), '0'::text))::bigint, to_tsvector(classify.nodebb_default_search_language(), COALESCE(content.value_string, ''::text)), classify.nodebb_default_search_language() -> Nested Loop Left Join (cost=1165055.57..2506360499514048447602759978568718009448537889177600.00 rows=578470278293751915037149459567669160211744652752060416 width=821) Output: pid.unique_string, topid.value_string, "timestamp".value_string, content.value_string, tid.value_string, uid.value_string, handle.value_string, ip.value_string, bookmarks.value_string, replies.value_string, upvotes.value_string, downvotes.value_string, deleted.value_string, deleteruid.value_string, edited.value_string -> Nested Loop Left Join (cost=1165055.00..365866714782288754474286443159961161947360002048.00 rows=81033454218824244642151458714323889325589848391680 width=763) Output: pid.unique_string, topid.value_string, "timestamp".value_string, content.value_string, tid.value_string, uid.value_string, handle.value_string, ip.value_string, bookmarks.value_string, replies.value_string, upvotes.value_string, downvotes.value_string, deleteruid.value_string, edited.value_string -> Nested Loop Left Join (cost=1165054.44..75434449138972992432114969088803141419270144.00 rows=15672615137716871687144905811486835401098788864 width=705) Output: pid.unique_string, topid.value_string, "timestamp".value_string, content.value_string, tid.value_string, uid.value_string, handle.value_string, ip.value_string, bookmarks.value_string, replies.value_string, upvotes.value_string, downvotes.value_string, deleteruid.value_string -> Nested Loop Left Join (cost=1165053.87..31696335788034820522606353910666568400896.00 rows=6304236302125211232581170392267430006095872 width=647) Output: pid.unique_string, topid.value_string, "timestamp".value_string, content.value_string, tid.value_string, uid.value_string, handle.value_string, ip.value_string, bookmarks.value_string, replies.value_string, upvotes.value_string, deleteruid.value_string -> Nested Loop Left Join (cost=1165053.31..8931653578848341381528421998180433920.00 rows=1621124304799343380934187421678406991872 width=589) Output: pid.unique_string, topid.value_string, "timestamp".value_string, content.value_string, tid.value_string, uid.value_string, handle.value_string, ip.value_string, bookmarks.value_string, replies.value_string, deleteruid.value_string -> Merge Left Join (cost=1165052.74..8062522191717699055335936607911936.00 rows=456529991748548558292958146522513408 width=531) Output: pid.unique_string, topid.value_string, "timestamp".value_string, content.value_string, tid.value_string, uid.value_string, handle.value_string, ip.value_string, bookmarks.value_string, deleteruid.value_string Merge Cond: (('post:'::text || pid.unique_string) = deleteruid._key) -> Merge Left Join (cost=1165052.17..57016889881305000188942393278464.00 rows=3246089247358848933594797849968640 width=473) Output: pid.unique_string, topid.value_string, "timestamp".value_string, content.value_string, tid.value_string, uid.value_string, handle.value_string, ip.value_string, bookmarks.value_string Merge Cond: (('post:'::text || pid.unique_string) = bookmarks._key) -> Nested Loop Left Join (cost=1165051.60..94923855733381078216855257088.00 rows=23080839358353589969016959533056 width=415) Output: pid.unique_string, topid.value_string, "timestamp".value_string, content.value_string, tid.value_string, uid.value_string, handle.value_string, ip.value_string -> Nested Loop Left Join (cost=1165051.03..12776095086276525667909632.00 rows=3069029967609273157301567488 width=357) Output: pid.unique_string, topid.value_string, content.value_string, tid.value_string, uid.value_string, handle.value_string, ip.value_string -> Nested Loop Left Join (cost=1165050.47..992275469854612652032.00 rows=237972205645779760578560 width=299) Output: pid.unique_string, topid.value_string, tid.value_string, uid.value_string, handle.value_string, ip.value_string -> Nested Loop Left Join (cost=1165049.90..141954342687451824.00 rows=32081475656790278144 width=241) Output: pid.unique_string, topid.value_string, uid.value_string, handle.value_string, ip.value_string -> Nested Loop Left Join (cost=1165049.34..19521491057370.11 rows=4088174042279840 width=183) Output: pid.unique_string, topid.value_string, handle.value_string, ip.value_string -> Nested Loop Left Join (cost=1165048.77..4867722585.94 rows=998468423017 width=125) Output: pid.unique_string, topid.value_string, handle.value_string -> Merge Left Join (cost=1165048.21..4822368.02 rows=208354785 width=67) Output: pid.unique_string, handle.value_string Merge Cond: ((('post:'::text || pid.unique_string)) = handle._key) -> Sort (cost=512697.09..516400.78 rows=1481476 width=9) Output: pid.unique_string, (('post:'::text || pid.unique_string)) Sort Key: (('post:'::text || pid.unique_string)) COLLATE "C" -> Result (cost=74126.00..335537.14 rows=1481476 width=9) Output: pid.unique_string, ('post:'::text || pid.unique_string) -> Append (cost=74126.00..335537.14 rows=1481476 width=9) -> Bitmap Heap Scan on classify.unclassified_zset pid (cost=74126.00..335537.14 rows=1481476 width=9) Output: pid.unique_string Recheck Cond: (pid._key = 'posts:pid'::text) Filter: (pid.type = 'zset'::legacy_object_type) -> Bitmap Index Scan on unclassified_zset_pkey (cost=0.00..73755.63 rows=1481476 width=0) Index Cond: (pid._key = 'posts:pid'::text) -> Sort (cost=652351.12..652421.44 rows=28128 width=71) Output: handle.value_string, handle._key Sort Key: handle._key COLLATE "C" -> Append (cost=0.00..650272.50 rows=28128 width=71) -> Seq Scan on classify.unclassified_hash handle (cost=0.00..650272.50 rows=28128 width=71) Output: handle.value_string, handle._key Filter: ((handle.type = 'hash'::legacy_object_type) AND (handle.unique_string = 'handle'::text)) -> Append (cost=0.56..23.29 rows=5 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash topid (cost=0.56..23.29 rows=5 width=71) Output: topid.value_string, topid._key Index Cond: ((topid._key = ('post:'::text || pid.unique_string)) AND (topid.unique_string = 'toPid'::text)) Filter: (topid.type = 'hash'::legacy_object_type) -> Append (cost=0.56..19.51 rows=4 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash ip (cost=0.56..19.51 rows=4 width=71) Output: ip.value_string, ip._key Index Cond: ((ip._key = ('post:'::text || pid.unique_string)) AND (ip.unique_string = 'ip'::text)) Filter: (ip.type = 'hash'::legacy_object_type) -> Append (cost=0.56..34.64 rows=8 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash uid (cost=0.56..34.64 rows=8 width=71) Output: uid.value_string, uid._key Index Cond: ((uid._key = ('post:'::text || pid.unique_string)) AND (uid.unique_string = 'uid'::text)) Filter: (uid.type = 'hash'::legacy_object_type) -> Append (cost=0.56..30.86 rows=7 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash tid (cost=0.56..30.86 rows=7 width=71) Output: tid.value_string, tid._key Index Cond: ((tid._key = ('post:'::text || pid.unique_string)) AND (tid.unique_string = 'tid'::text)) Filter: (tid.type = 'hash'::legacy_object_type) -> Append (cost=0.56..53.55 rows=13 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash content (cost=0.56..53.55 rows=13 width=71) Output: content.value_string, content._key Index Cond: ((content._key = ('post:'::text || pid.unique_string)) AND (content.unique_string = 'content'::text)) Filter: (content.type = 'hash'::legacy_object_type) -> Append (cost=0.56..30.86 rows=7 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash "timestamp" (cost=0.56..30.86 rows=7 width=71) Output: "timestamp".value_string, "timestamp"._key Index Cond: (("timestamp"._key = ('post:'::text || pid.unique_string)) AND ("timestamp".unique_string = 'timestamp'::text)) Filter: ("timestamp".type = 'hash'::legacy_object_type) -> Materialize (cost=0.57..1033404.06 rows=28128 width=71) Output: bookmarks.value_string, bookmarks._key -> Merge Append (cost=0.57..1033333.74 rows=28128 width=71) Sort Key: bookmarks._key COLLATE "C" -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash bookmarks (cost=0.56..1033122.77 rows=28128 width=71) Output: bookmarks.value_string, bookmarks._key Index Cond: (bookmarks.unique_string = 'bookmarks'::text) Filter: (bookmarks.type = 'hash'::legacy_object_type) -> Materialize (cost=0.57..1033404.06 rows=28128 width=71) Output: deleteruid.value_string, deleteruid._key -> Merge Append (cost=0.57..1033333.74 rows=28128 width=71) Sort Key: deleteruid._key COLLATE "C" -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash deleteruid (cost=0.56..1033122.77 rows=28128 width=71) Output: deleteruid.value_string, deleteruid._key Index Cond: (deleteruid.unique_string = 'deleterUid'::text) Filter: (deleteruid.type = 'hash'::legacy_object_type) -> Append (cost=0.56..19.51 rows=4 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash replies (cost=0.56..19.51 rows=4 width=71) Output: replies.value_string, replies._key Index Cond: ((replies._key = ('post:'::text || pid.unique_string)) AND (replies.unique_string = 'replies'::text)) Filter: (replies.type = 'hash'::legacy_object_type) -> Append (cost=0.56..19.51 rows=4 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash upvotes (cost=0.56..19.51 rows=4 width=71) Output: upvotes.value_string, upvotes._key Index Cond: ((upvotes._key = ('post:'::text || pid.unique_string)) AND (upvotes.unique_string = 'upvotes'::text)) Filter: (upvotes.type = 'hash'::legacy_object_type) -> Append (cost=0.56..11.94 rows=2 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash downvotes (cost=0.56..11.94 rows=2 width=71) Output: downvotes.value_string, downvotes._key Index Cond: ((downvotes._key = ('post:'::text || pid.unique_string)) AND (downvotes.unique_string = 'downvotes'::text)) Filter: (downvotes.type = 'hash'::legacy_object_type) -> Append (cost=0.56..23.29 rows=5 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash edited (cost=0.56..23.29 rows=5 width=71) Output: edited.value_string, edited._key Index Cond: ((edited._key = ('post:'::text || pid.unique_string)) AND (edited.unique_string = 'edited'::text)) Filter: (edited.type = 'hash'::legacy_object_type) -> Append (cost=0.56..30.86 rows=7 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash deleted (cost=0.56..30.86 rows=7 width=71) Output: deleted.value_string, deleted._key Index Cond: ((deleted._key = ('post:'::text || pid.unique_string)) AND (deleted.unique_string = 'deleted'::text)) Filter: (deleted.type = 'hash'::legacy_object_type) -> Append (cost=0.56..23.29 rows=5 width=71) -> Index Scan using unclassified_hash_pkey on classify.unclassified_hash editor (cost=0.56..23.29 rows=5 width=71) Output: editor.value_string, editor._key Index Cond: ((editor._key = ('post:'::text || pid.unique_string)) AND (editor.unique_string = 'editor'::text)) Filter: (editor.type = 'hash'::legacy_object_type)
-
Mmmmm, queries with multiple self joins.
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
Mmmmm, queries with multiple self joins.
I managed to get it down to 6326220377491 posts, which is a reasonable estimate if the Likes Thread had never died down.
-
@ben_lubar
Only 2 or 3 self joins left to eliminate!
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
@ben_lubar
Only 2 or 3 self joins left to eliminate!I didn't eliminate any of them!
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
we'll flip some database bits and be great
Isn't language/locale independent searching a feature of all modern, mature, stable databases?
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
actual database with non-manually-maintained indexes.
jfc, you must be at your keyboard all the time!
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
The query analyzer thinks we have 3092878113439288612870797836676403532242027679745868562432 posts.
We did before fbmac happened.
-
oh god why did I do this to myself
Here's some actual data from the database:
/uid/141534 is banned until 29395-08-10 15:39:06.306 (UTC)
/uid/140925 is banned until 2739923-07-19 15:38:41.98 (UTC)
-
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
actual database with non-manually-maintained indexes.
jfc, you must be at your keyboard all the time!
Obviously not, the search barely works!
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
Mmmmm, queries with multiple self joins.
For the benefit of people from the future, here's @izzion's current avatar:
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
/uid/141534 is banned until 29395-08-10 15:39:06.306 (UTC)
/uid/140925 is banned until 2739923-07-19 15:38:41.98 (UTC)No longer welcome here.