Opera’s going to be switching to webkit

fuck the web :(

eccentric-nucleus:

insufficientlyadvanced:

cisadmin:

insufficientlyadvanced:

text post preview doesn’t process markdown at all, instead acts like wysiwyg?? actually posts fine tho

i saw that. total bullshit i-didn’t-test-my-code kinda stuff we should expect by now though.

i found this out by copy+pasting your post about html-less html posts getting wysiwyg’d and totally panicked about markdown being entirely broken. saving as draft and then viewing the draft worked better though. welp. i hope foldingcookie writes a badass third party client……

the most regrettable thing is that this isn’t even new; markdown in preview has been broken for a month or two now (presumably when they started implementing the new dash code)

lesson learned: don’t even try to use markdown on tumblr. it really is not worth the trouble.

so here’s my current plans for the design of the tumblr client library.

it’s going to be written in C, using json-c, libcurl, liboauth, and openssl; the idea is to write a reusable backend that provides an intuitive abstraction of the conceptual entities that tumblr exports, and then write a TUI frontend to that library.

Read More

let me use this super-powerful interface to merge some of these shitposts down into something less abusive of my followers’ attention. sorry, everyone.

https://en.wikipedia.org/wiki/OAuth#Non-interoperability

lol, it’s seriously like a bunch of fucking clowns built all this shit

http://www.tumblr.com/oauth/apps

what does that even mean and why can’t I specify the source url for stuff anymore

what the fuck is an xauth

btw hmu on IRC or something if anyone wants to help

eccentric-nucleus:

frankensokka:

the

<marquee>

tag has been deprecated. instead use

@keyframes marquee {
from { left: -10%; }
to { left: 100%; }
}
@-webkit-keyframes marquee {
from { left: -10%; }
to { left: 100%; }
}
@-moz-keyframes marquee {
from { left: -10%; }
to { left: 100%; }
}
@-ms-keyframes marquee {
from { left: -10%; }
to { left: 100%; }
}
@-o-keyframes marquee {
from { left: -10%; }
to { left: 100%; }
}
.marquee {
overflow: hidden;
position: absolute;

animation: marquee 10s linear infinite;
-webkit-animation: marquee 10s linear infinite;
-moz-animation: marquee 10s linear infinite;
-ms-animation: marquee 10s linear infinite;
-o-animation: marquee 10s linear infinite;
<div class='marquee'></div>

YES

Tested under webkitgtk 1.10.1; works with earlier versions and probably with some other webkit ports as well. Prints via console.log, so open your inspector or whatnot. In essence: elements with identical style data aren’t necessarily identical; also, once an element gets perturbed there’s no easy way to return it to a native (themed) rendering. -webkit-appearance is a read-only (ish) variable: you can set it to none by writing to it /or/ other CSS properties, but you can’t set it to non-none values without a lot of fuckery (or at all in some scenarios).

I want to give a shoutout to anybody, anywhere, that thinks censorship is cool: man, fuck you!

(That’s not to say that this is censorship by google, but to denounce Google’s implicit support of the copyright censorship regime.)

(via hackedy)

the gopher community is gathering itself up like the entfolk to discuss at length how things can be improved without compromising the legacy of gopher’s simplicity

I’m amazed this kind of discussion is actually happening. 2012 will be a big year for the protocol

Javascript is /the/ four-letter word here.

because they added code to prepend anti-phishing js (what the fuck, you should know that can’t possibly work for more than a couple hours) and the html5 doctype to all blog pages.

wtffffff