Imports (Was: {brace yourselves} the import is coming {Spoiler Alert: Not all of it} [i.e. blakeyrat was not utterly wrong for the first time ever] Filed under: append-only titles.)
-
it takes 72 bytes!
That's odd, as I calculate 27 bytes only…it only takes 4 bytes
…and that's only valid if you lose the metadata to say that you're screwing around with non-standard digits. Adding that in bulks things out.
-
OSes should support generic APIs for converting a file to/from text, which programs can then implement for their file formats don't get me started on extensions. Then, text editors can use these APIs and open arbitrary super-compressed log files or whatever you want. The APIs can be sufficiently smart to support opening (small part of) an arbitrarily large file, etc.
So... you propose a system where we have a standard text <=> binary conversion that everyone will use and the world will be a sunny place?
sorry, couldn't keep a straight face.
Oh, oh! Maybe... maybe we could use a widely known standard that you can use any number of programs to open if our editor cant? Also, for convenience, we could keep the latest log file, which is usually what the user wants, in plain text and pack them into a binary format when it's time to start writing into a new logfile. Yeah! I'm a genius! I'll propose this to eve...
Oh. Well... I still can't just double click thin...
Huh. I guess I'll go find my gloves now...
-
You literally did not read my post (or else had some brain aneurism during, perhaps related to new ideas fighting their way in)
Under the proposed scheme, you can double click on the gz files and have them opened in your favorite editor (probably vim or something equally torturous) just as if it were a text file.
Saving works transparently as well.
-
-
And yes, I am in full-on trolling mode. (Some people would call it rant/rage mode? Some people...)
The trick to trolling, though, I find, is not to take an idea too dumb and try to push it, but to take an idea too smart and try to push it.
It's like a joke - not really that funny if it's not true.
-
Under the proposed scheme, you can double click on the gz files and have them opened in your favorite editor (probably vim or something equally torturous) just as if it were a text file.
Proposed scheme? vim can already edit gzipped text natively.
-
Yes, I read it. And I wouldn't mind having a way to do that reliably. But that gets us back into the whole extensions and standards debate all over again.
Besides, the way you described it is creating a grand new standard that will do magic stuff. Or, you know, a plugin and, lacking better options at this time, stick a
.gzl
(for gzipped log, see?) extension on it. There. Realistic, could work, you get a vote from me.And yes, I am in full-on trolling mode.
Damn it! Don't admit it, now we can't have our flamewar! I was looking forward to it too. Made popcorn and everything!
Proposed scheme? vim can already edit gzipped text natively.
Another party pooper. Get your logic out of my forums!
-
stick a
.gzl
(for gzipped log, see?) extension on it.I like it, but I want to it have a
.4shzl
extension.
-
Is it safe to monkey patch Guardian to make it allow everything during the import script, or would that somehow leak into the live forum?
It will not leak, but background jobs will not pick up on it (which should be ok)
-
The "Onyx' board of standards that will never be implemented" is always open to suggestions.
-
Besides, the way you described it is creating a grand new standard that
will do magic stuff. Or, you know, a plugin and, lacking better options
at this time, stick a .gzl (for gzipped log, see?) extension on it. There. Realistic, could work, you get a vote from me.I'm not here to solve you people's goddamn problems realistically.
If I'm going to solve any problems here at all, they'll be grand solutions - too beneficial and majestic for this wretched earth.
And obviously, by solve, I just mean describe the solutions while yelling at people too entrenched to understand them. The solutions' implementation is left as an exercise to the reader. (The technical part isn't hard - the hard part's getting all the Unix ents, Windows gangsters and Mac paedophiles to agree to this.)Damn it! Don't admit it, now we can't have our flamewar! I was looking forward to it too. Made popcorn and everything!
Sorry, I'm just too naturally good-hearted, I can't insult people without explaining the context of the insult. A personal flaw of mine.
And if you bothered to read my troll-admitting post a bit more intently, you would realize I'm still behind my idea, just acknowledging it's too good rather than just good.
I mean, I didn't expect you to bother.
("Unix ents, Windows gangsters and Mac paedophiles". See? It's all about being too true)
Also, my good-heartedness obviously doesn't extend towards groups of people. Also, towards paedophiles.
-
Sorry, I'm just too naturally good-hearted, I can't insult people without explaining the context of the insult. A personal flaw of mine.
You seem to be under the impression that you managed to rankle me.
And if you bothered to read my troll-admitting post a bit more intently, you would realize I'm still behind my idea, just acknowledging it's too good rather than just good.
And if you read my post you'd realize that I laughed at the notion of the standard interface that every editor on Earth will wholehartedly accept and just use, not at the notion of compressing the logs. I also showed you that this is being done by some degree and that all that is required is a plugin for the text editor that can read gzipped files. Or, you know, two extra clicks. pick your poison.
I mean, I didn't expect you to bother.
Clearly, since you didn't bother to understand where my complaints were and went straight for accusing me of not reading your. "Never expect people to do something you yourself wouldn't" is fair principle in my book.
-
You seem to be under the impression that you managed to rankle me.
Wait, I'm confused, is this an argument or not?
-
You seem to be under the impression that you managed to rankle me.
Nope, just explaining why I explained that I was trolling.
Tune in next post, where I'll explain why I explained why I explained that I was trolling. It will happen.And if you read my post you'd realize that <...>
True enough. Reading is hard work.
...I laughed at the notion of the standard interface that every editor on Earth will wholehartedly accept and just use
I'd worry about placing the interface in all (popular) OSes first. Having the popular editors used would be a walk in the political park in comparison.
-
I'd worry about placing the interface in all (popular) OSes first. Having the popular editors used would be a walk in the political park in comparison.
If we could just get systemd on Debian, it would all be easy after that...
Wait, I'm confused, is this an argument or not?
Yes? No? ARGUMENT_NOT_FOUND?
-
Note, @sam created a plugin with a user pref for this.
http://what.thedailywtf.com/t/stop-spamming-my-browser-history-setting/770
Discourse just told me the above post was unread.... lolwut? Is it coming apart at the seams?
-
And me.
-
Same here, as well as 2 other older posts I'd already read.
-
-
We're not out of the woods yet though...
-
-
@if I have some random junk instead of a proper cite it still works... said:
https://www.youtube.com/watch?v=3HOMeMKANaQ&t=72
And if I copy paste into a new reply it also works:
@dhromed said:too short
So why are
<blockquote>
s broken in the imported topics? What's going on there.Also, I found a quoting bug*: that @morbiuswilters post I just quoted here has a
</blockquote>
tag which was somehow mysteriously converted into a[quote]
tag when it was rendered over here.
-
And now I had marked "unread" posts from one of the original imported topics, 3 posts dated May and June 2006.
-
Discourse just told me the above post was unread.... lolwut? Is it coming apart at the seams?
You think that's bad? I'm getting unread notifications for posts I wrote last summer.
-
Like this? <p> tags seem to break stuff.
But only at the very start of a post? (Everything below this is copied verbatim).
<asdf>
-
@Buddy said:
But only at the very start of a post? (Everything below this is copied verbatim).
<asdf>
Yeah, I think you're probably right.
<p>
at the start of a post ruins everything!
-
-
Hey is this topic:
showing up on the main page for you? It doesn't appear to have any posts in it newer than 2007.
-
I'm gonna go with "no". The only thing which I saw which seemed 'new' was this...
-
Found it, trolling through /categories... But it has no date, how odd!
-
Ok, and if you go to http://what.thedailywtf.com/c/contest-discussion it doesn't say 1h in the Activity column?
-
Yeah, it does say 1h, but I can't see why it would, the last post was some time in '07...
-
Maybe the date hasn't been imported yet.
-
I guess...
-
Maybe its using the "updated at" field
-
Imported topics seem to be in an odd sort of limbo state, not new, not read, not tracked. It's rather confusing when someone makes a new post in one.
An imported topic showed up for me near the top of latest because somebody made a post in it a few minutes ago. However, there was no blue (or gray) circle indicating unread posts, and clicking the topic took me to post 1. Ordinarily, the topic would be new, because I haven't read it, but
Any topics created before you last pressed "Dismiss New" are never new.
And discourse didn't indicate the new post because I wasn't tracking the topic, because I had never viewed it. Post 1 because individual posts weren't marked as read.This is all technically correct, I guess, but unexpected. I have my options set to always tell me about new topics and new posts in any topic (except the handful I have muted). However, this doesn't work for new topics in imported posts. It makes it easy to miss necroposts to imported topics, since they're neither new nor unread.
-
I guess...
-
This is all technically correct, I guess, but unexpected. I have my options set to always tell me about new topics and new posts in any topic (except the handful I have muted). However, this doesn't work for new topics in imported posts. It makes it easy to miss necroposts to imported topics, since they're neither new nor unread.
I guess Discourse wasn't designed to handle a sudden large influx of 5-10 year old posts...
-
Well... that's nice. Also, are we in read-only? Posts are not being marked read... I guess I'll see now.
Edit: Ah, stuff is getting marked read now, albeit slowed down it seems.
-
Some old stuff seems to be importing as 'readonly' topics, some of it can be necroed in strange ways. Haven't been able to discern a pattern as of yet. (but there's always Reply as linked Topic...)
-
Why don't we just employ a bunch of $DISADVANTAGED_MINORITY people to rewrite the forums? Would've gone faster...
Filed under: who apparently can't be replaced by a simple shell script
-
I'd rather not cause the forumpocalypse if it can be avoided.
Since there was talk of doing the import at "a quiet time because the forum is as slow as molasses" when the import is happening....
(Aka: "you can vi/tail/head/ass text files" is not a valid advantage since you can do that for binary files just as easily under my scheme)
This presumes that the API which you dreamt up actually exists and is infallible. Such a thing doesn't exist.
And it presumes that every text manipulation program out there can magically start using it. By default.
This is that instance.
I thought it was the older one...
Oh. Well... I still can't just double click thin...
It's almost as if there aren't programs called
zcat
,zgrep
,z..
Oh, wait...
-
@ben_lubar - what's going on here with asterisks? Seen it a few times:
Original:
Being as the signature of sprintf is "int sprintf(char *s, const char *format, ...)" it is good practice to be in the habit of writing for instance:
Imported:
http://what.thedailywtf.com/t/one-day-looking-through-code/14506/5?u=pjh
Being as the signature of sprintf is "int sprintf(char \1s, const char \1format, ...)" it is good practice to be in the habit of writing for instance:
Also, some quoting is broken (seems to be the inserted
<p>
at the start causing this one):http://what.thedailywtf.com/t/one-day-looking-through-code/14506/14?u=pjh
-
\1
? Looks like a failed regex replace. Guessing\1
is the backreference syntax in Ruby?Googles
No, it's
$1
it seems. Maybe a typo / confusion due to other languages? It would make sense to me that it's tying to replace them with either\*
or*
to prevent italics.
-
Another one here - it's totally fucked up the link; underbar's this time:
Original:
@Daid said:
Imported:unless I miss the fact that there is some whitespace compiler?
http://en.wikipedia.org/wiki/Whitespace_(programming_language)http://what.thedailywtf.com/t/speed-challenge-33-something-that-does-nothing/15396/4?u=pjh
@Daid said:
unless I miss the fact that there is some whitespace compiler?
http://en.wikipedia.org/wiki/Whitespace\1(programming\1language)
And C# -> C\1 in this post:
http://what.thedailywtf.com/t/speed-challenge-33-something-that-does-nothing/15396/6?u=pjh
-
Yup, looks like it's trying to remove anything that would cause Markdown dickery and completely failing at it
Though underscores are a bit confusing. Future-proofing in case Discourse adds
_underline_
?Oh, never mind, undersores are
_italic_
too!
-
Or __bold__
-
Let me remove my glasses...
I know, this comment added no value to the conversation. But I felt it had to be made.
-
Yikes...308.3K posts now.
-
wtf is 'The Import'? Some super kalody sizy thing that blows everything up?