Testing twitter auto-update

Twitter changed the way that they treat authorising and wrapping external links, and since they did that our auto-update plugin has been fubared.

So, this is a test. To see if I have fixed it (my hopes right now are not high, and this is so not the best time for this to happen).

Feel free to ignore. Or you could use the comments to share your technical woes of any kind, if you’re feeling chatty.



Categories: Meta

Tags:

25 replies

  1. Ooo, I’ve got a fun one! At home over our iinet connection I can’t upload anything – no Flickr, Twitpic, emails with attachments, seeding on torrents. I can download fine and do all other internet type stuff. At work or using the 3G connection everything works perfectly well. As far as he can tell my laptop’s settings are the same as Adam’s identical laptop’s settings and he’s been beating his head against a brick wall tweaking various settings on the router and my lappy to no avail. It’s all rather frustrating.

  2. OK, fine, technical woes.
    1. Dear person whose code I am compiling. this is NOT valid C++ in modern compilers (because the result of getenv is char*)
    wordy = (int)getenv(“SD_WORDY”);
    2. Academics, stop writing your own build systems. Now. autoconf etc are a pain in the neck, but at least they are a somewhat universal pain in the neck.

  3. 3. Don’t use -Wno-deprecate (which means “do not show me deprecation warnings”) with GCC, because those deprecated things? They are deprecated as in will not work with some future version of the compiler.
    That is all.

  4. mimbles: not sure how technical Adam is, but the most obvious cause is MTU settings, my husband also suggests that you may possibly have a broken proxy setting (although I think the latter is far less likely, since torrents and email are also affected).

  5. Thanks Mary, he’s scary technical – I’m easily intimidated 😉 – and yeah, he’s checked both of those. He was half-way through installing Wireshark when I reclaimed my laptop on the weekend, I suppose I’d better give it back to him and let him finish the job at some point.

  6. mimbles: I’ll be interested to hear what the answer ends up being, eventually. Good luck!

  7. @Mary re deprecated code, I’m finding that this is an increasing problem just in blog comments – newer browsers seem to not display deprecated HTML formatting tags such as <i>, <b>, <s>, <q> etc, yet people who are used to the old tags keep on using them. I keep on looking at comments and realising that people meant for them to be formatted and going in to fix them manually so that all of us with newer browsers can see them as intended. It’s tedious, and it’s why I installed the quickformat buttons above the comments input form here, but I guess it’s people who are browsing with javascript turned off who aren’t seeing the formatting buttons and who are using the older tags.
    Grr-vent.

  8. Or just that some people are trained to use b for bold, etc from long term HTML writing (I’ve been doing it for 14 years, for example). Also, people who don’t like to use their mouse, as many people prone to RSI train themselves to avoid, won’t use the tools if they need to use a mouse for them. (On a tangent, does anyone know of disability activist writing around the RSI space? I want to discuss it on Geek Feminism, but don’t have the background: my own tendency to have typing pain is comparatively mild and not disabling.)
    If I am understanding the specs correctly, of the simple formatting tags only s, tt and u are deprecated in HTML4/XHTML1 and will disappear in HTML5. HTML5 will also change i and b’s meaning and wants people to use CSS for the existing behaviour, and q is still good to go: http://dev.w3.org/html5/spec/text-level-semantics.html#the-q-element
    That’s nice about q, because the implementation of q is supposed to allow you to nest quotes and it will generate the different quote marks properly for you (when supported anyway!)

    • I must admit I’m a bit confused as to why <i> in particular just doesn’t seem to work anymore on sites that I’m viewing, anyway. I have to edit those to <em> if the text is to render as italic in my browser. Going by other people’s comments, it’s not just me who’s seeing (or not seeing, as the case may be) this behaviour.
      Google-fu has failed me as to why it’s happening.
      I’ll just test test test and test. That should be two italic tests and two bolded tests.

  9. So, looking at this page in the latest version of Firefox, I’m only seeing the first italic and first boldest test, which used XHTML tags. The two others using old HTML tags don’t display as formatted.

  10. It seems to be due to your CSS.
    File https://hoydenabouttown.com/wp-content/themes/hybrid/library/css/25px.css defines the following:
    b, i, hr, u, center, menu, layer, s, strike, font, xmp{{
    margin-top: 0pt;
    margin-right: 0pt;
    … // blah blah blah
    font-weight: normal;
    font-style: normal;

    // blah blah blah
    }
    So you’re overriding the original definitions of b and i using that CSS.
    Incidentally, I found this out using the Web Developer plugin for Firefox. If you go to Tools -> Web Developer -> CSS -> View Style Information and then click on any part of a page, it will show you the snippets of CSS that are styling that particular bit.

    • Now see, I’d looked at that with Firebug and hadn’t seen anything, especially as it happens across several themes used on different sites. That’s buried deep in the typography libraries that are called by the main stylesheet, so I’ve never touched it. It must have been somebody’s bright idea that somebody else copied and became part of many themes’ core files.

  11. I actually only just discovered that particular feature of the Web Developer plugin (I’ve been using Edit CSS for ages) and I will never look back.

    • How weird for someone to decide that just over-riding the default for those formatting tags was the right thing to do. Are they on a mission to force people to use XHTML instead?

  12. Someone does seem to dislike those tags, don’t they? (Well, I’m not their biggest fan, but not to the point of trying to make sure that no one who uses my theme can get them to work.)
    On a vaguely related note, I’ve repeatedly thought that there would be a market for a “A WordPress Admin’s Rough and Ready Guide to HTML, CSS, PHP, Version Control…” week long training course. So many of these tools and so on are passed around by word of mouth.

    • @16: I’ve finally got around to attempting a stylesheet fix on this stripping out of b and i tags. If it has worked, the following text in brackets {should be bold} and this next bit in brackets {should be italic}.

  13. Y’know, the linkfest plugin coulda just popped up a reproachful message in the admin dashboard about how it had been a while since I used it. It didn’t have to post 75 copies of itself this morning to make sure the point hit home.

  14. 75! Oh dear. I can’t help but laugh a little though. Also I now have visions of the plugin pouting in a corner after having been told off for excessive attention seeking behaviour.

  15. OMG! I uploaded something over our iinet connection for the first time in a month. Adam has been futzing around with the network all this time, we had an iinet tech come out and look at things, we tried a different router which refused to play nice so the old one went back in, all to no avail. Then tonight I was having trouble getting my twitpic email uploads from my phone to work, so I tried on the laptop. And it worked. And we don’t know why. GAH! But good! Assuming it stays fixed.

  16. Congrats! I hope your good fortune is contagious.

  17. Hm. Well the italics fix worked (in Firefox). Semi-yay?

  18. Oh whee! It works now!
    (ObMysteriesOfCSSQuestion: Why did simply reversing the order of the lines in the stylesheet where I stipulated attributes for b and i respectively make the b attributes suddenly work? ‘font-style’ shouldn’t have over-ridden ‘font-weight’ by coming second in the first effot, surely?)

  19. And of course, the italics don’t work now that I’ve got the bold working with the reversal of the stylesheet lines. Argh. Ok, I’m going to switch the lines in the stylesheet around again, because italics seems more crucial AIUI for people using screen-readers, but this is v. annoying.

  20. OK, finally sorted it.

%d bloggers like this: