denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Denise ([staff profile] denise) wrote in [site community profile] dw_news2014-07-14 08:25 am

Dreamwidth news: 14 July 2014

Hello, Dreamwidth! I come with the assistance of our kitten, who likes to help with technical matters, to bring you a quick round of Dreamwidth news.

This is a short update, because I'm sneaking it in under the wire before elbow surgery (which is scheduled for 24 hours or so from now, eep), so I may not be able to respond to all comments and I definitely won't be able to respond past tomorrow -- prognosis is anywhere from 4 to 8 weeks before I'll be typing regularly again, and dictation software doesn't work for me.

Behind the cut:

* Development
* Responsive design: styles changes
* Date/time check removed when posting
* Bugfix for comment import problems
* Mail sending problems
* Tales from the Conference

A reminder: Whenever a news post is posted, all notifications are delayed for a little while as the mail system sends out notifications of the announcement. Comment notifications may be delayed for up to an hour or two. This was posted slightly before 0830 EST (see in your time zone). Please don't worry about missing notifications until at least 1030 EST.


Last night's code push included the fixes and features detailed in the 11 Jun - 12 Jul code tour. Along with the usual backend bugfixes and groundwork to allow for future features (say that 12 times fast), and a few changes that will be detailed later in the update, this code push also includes:

* A fix for the problem of comments deeply nested inside a comment thread not being printed in some cases, and a fix for a problem where deeply-nested comments were causing too many closing </div> tags to be printed, thus occasionally breaking a layout.

* Better, more-explanatory messages when a community admin uses the link to remove accounts that have been deleted and purged from the community.

* Multiple tweaks and bugfixes for the new community admin area based on user feedback.

* A fix for the problem where entries posted by email and entries created through feed accounts would fail if the subject line was too long.

* Adding Flickr as an embedding source (so Flickr widgets can be embedded in your journal entries).

* Converting the all-entries-for-this-month view in journals to use the journal customization system, even when they're being displayed in site skin (and, therefore, creating month views that replicate all the site skins).

* Five new themes by [personal profile] dancing_serpent for the Ciel style.

Responsive design: styles changes

Last time around, I talked a bit about our responsive design project. The aim behind that project is to make the site work better on mobile devices, small screens, and touch screens without worsening the experience for people working on larger screens. (And, as a side benefit to the project, improve the site's accessibility and improve the way it works with assistive technology.)

The project continues apace! This time around, the changes are to journal styles. About half of our styles have been converted to use the new styling. The goal in this part of the project is to make sure things degrade more gracefully on smaller screens, without changing the experience for people on larger screens. It's one of the things people have asked for most frequently over the past year or two. I'm really excited about it, and [personal profile] fu has done an awesome amount of work on things.

The biggest change is that if your journal is set to a 2-column or 3-column layout, it will now gracefully degrade to a 1-column layout (with the sidebar modules beneath the main journal content) when the screen is smaller than a certain range. We picked the size at which the layout flips over to 1-column mode based on the rough size of standard mobile devices, but if you find that the change is triggering when it shouldn't, or not triggering when it should, let us know.

We also changed the navstrip so that it would degrade gracefully on smaller screens, instead of forcing the window to scroll sideways.

If you're using a system layout without any customization, your journal is already updated to take advantage of all these changes. If you've customized your journal and unchecked the "use layout's stylesheet" option in the Custom CSS tab of the Customize Journal Style page, you may need to tweak your journal CSS a little to make the navstrip display the way you'd like it to display.

When a journal collapses into one-column mode, the top of the journal will now have a link to the sidebar modules (to save you having to scroll through all the entries on the page). If you'd like to remove it, go to the Custom CSS tab of the Customize Journal Style page and add the following CSS in the "Use embedded CSS" box:

#module-jump-link { display: none; }

We'll be continuing to tweak the presentation of the already-converted styles (and fix the bugs that people have found) over the next week or so, then move on to converting the remaining styles for the next code push.

You can read more about the conversion, if you'd like!

Date/time check removed when posting

Last time around, I let you know that we'd be removing the date/time check when you post an entry. This is the thing that wouldn't let you post an entry in the 'past' (any entry dated prior to the most recent entry in your journal). It was originally intended to keep people from not being able to find entries in their journal due to a mis-set clock: your journal displays entries sorted by time, not by posting order.

We decided that these days, most devices update their time just fine on their own, so mis-set clocks are way less common. So, from now on, you can make posts dated whenever you'd like, without having to muck around with the "dated out of order" flag.

This does mean that if your computer clock has been set wrong, and you've been posting in the future -- if you have entries in your journal dated with a time that's later than now -- it may appear that your entries aren't being posted. For instance, if you have 20 entries in your journal that are dated 2015-06-10 through 2015-07-10, then you correct your clock and you post entry 21 with the correct date of 2014-07-14, that entry will not appear on the front page of your journal: it will appear behind all the entries dated 2015.

So, if you post an entry and can't find in your journal: double-check your computer clock and the timestamps on your previously-posted entries, or view your journal's Archive page, which will let you find entries by date.

The "date out of order" checkbox, meanwhile, has now been renamed "Don't show on reading pages", since that's the only thing it's good for anymore! Use it when you're posting a lot of entries at once that you don't want to flood your subscribers' reading pages with, such as if you're filling in old journal entries or posting a lot of placeholder entries that you'll fill in later. (The content importer already sets this flag for imported entries.)

Bugfix for comment import problems

If you've had problems with importing your comments from LiveJournal within the last two months or so, try the process again! We made a change that should fix one of the major issues people were having.

If that still doesn't work, open a support request. Be sure to include the text of the error message you're receiving (which can be found in your Inbox). We can't always guarantee we can fix the problems -- the importer is a complex system that relies on data we receive from the site you're importing from, and sometimes that can break in ways we can't fix -- but we'll do our best. (It will probably take a while for you to get a response to your support request, because the importer is a complex system, it takes time to troubleshoot it, and the number of people who can do that troubleshooting is limited, but we will give it our best shot.)

Mail sending problems

If you use a Yahoo email address for your Dreamwidth account, you may have noticed that you're having trouble receiving email from us. Yahoo is one of the email providers that decides to block us from sending mail to them pretty frequently. (AT&T and Bellsouth are the other ones that like to block us a lot.) This is due to a combination of the amount of email we send, and the fact that forwarding email address are often spammed (and the way email works, it often looks like we're the spammers, not just providing a forwarding email address).

When that happens, we do try to get them to unblock us, but in the meantime, you may want to switch to using another email provider.

You can help to avoid this problem by not marking email from Dreamwidth or email that was sent to your forwarding address as spam -- a lot of times, these blocks are triggered by too many people flagging mail from us as spam. If you don't want to get comment notification email from us anymore, you can change that in your notification settings.

Tales from the Conference

A few weeks ago, the traveling Dreamwidth circus went to Open Source Bridge, which is one of my favorite tech conferences. It's tradition for folks that DW brought to the conference to write a bit about what they did and what they learned, so I'll turn the floor over!

[personal profile] azurelunatic, who co-presented (with [personal profile] misskat) a talk called "Keeping Your Culture Afloat Through A Tidal Wave of Interest" on lessons learned from the early DW development period on how to maintain cultural continuity in the face of many new contributors to your project:
Before Dreamwidth had a website, it had a user group. Before Dreamwidth had a user group, it had a Diversity Statement. So [personal profile] misskat and I talked about parts of the process of watching the user group start from the concept of Hypothetical Journal and the Diversity Statement and the things we learned from that. It was great fun! I had stage fright, my computer kind of died a little, and I'm already planning the changes I'm going to make to the talk based on what I learned from giving it. 

I was surprised by one thing I learned at Open Source Bridge. The open source world, or at least the bits of it attending Open Source Bridge, has a lot of people at a 101 level for community organization and culture. In addition to a world-class performance engineer ([staff profile] mark) and [personal profile] fu and [staff profile] karzilla and all the other lovely devs, Dreamwidth has people working on making the development community and other official areas pleasant and productive places to be. 

Other things I learned: 

[personal profile] misskat and I got on famously in person. One surefire way to make your travel group laugh is to run slow-motion across the hotel restaurant lobby to embrace each other as violins play in the background. Or maybe it was dubstep. Nobody's quite sure. 

Editing your presentation at the last minute is a time-honored conference hobby, but it helps if your laptop doesn't crash Powerpoint five times in fifteen minutes. 

Having at least one car at the conference makes a lot of things better, including the spur of the moment laptop and soda run to Costco. 

Shortbread is more delicious when it's CAPTAIN AMERICA shortbread. 

And last but certainly not least -- meeting up with Dreamwidth people in person is an amazing bonding experience, and I want to do it again. Next year in Portland! *raises a glass* and ... TO THE ROLEPLAYERS!

(The "to the roleplayers!" was a repeated toast during the week; we love y'all and your big, beautiful, gleeful embracing of the site and everything you can do with it.)

[personal profile] fhocutt, who gave a kickass keynote, and who, while not traveling with the Dreamwidth Traveling Circus per se, was perfectly happy to be swept up in our wake:
Here are some things about Open Source Bridge:

* It is a delightfully inclusive and welcoming conference! Mobility lanes, quiet room, all-veg*n food, great code of conduct.

* I met so many amazing people, at least half of whom were badass technical women. An overlapping subset of said amazing people were familiar from dw-dev and/or #dreamwidth IRC! I continue to get further into open source/"open stuff" largely because of women who are doing such good work there already and want to share it.

* I talked with experienced people about what sorts of things are expected in a technical keynote, wrote at least three outlines, and gave two practice talks. I was very nervous about the talk until those outlines coalesced! Per [personal profile] brainwane's suggestion, I read Obama's "A More Perfect Union" while I was struggling with drafts, as an example of how to blend lived experience with theory and a call to action.

* I gave the Thursday keynote address: "'Whyare these people following me?': Leadership for the introverted,uncertain, and astonished." I talked about my journey through and out of chemistry and into founding a hackerspace, about leadership as a learned skill that is founded in warmth and authenticity (expressing these is also a learned skill!), about ways the open source community denies itself leaders, and about ways we can make leadership easier tolearn for more people.

* Julie Pagano and Lukas Blakk also gave fabulous keynotes! Julie spoke on ways to combat impostor syndrome, and Lukas talked about the Ascend Project, which aims to welcome underrepresented people into open source software development and is kicking off in Portland this summer.

* The Nyan Cat song sounds pretty great on organ.

* There was a thought-provoking discussion on class and classism in technology during the unconference day.

* There was a button maker and excellent paper to use it with! And at no point was it weird for me to be knitting.

* There were talks! My suspicions that the state of web security is appalling were only confirmed, thanks to Terri Oda and [personal profile] mjg59.

TL;DR: would go again, would speak again, and would meet up with #dreamwidth people again!

[personal profile] kareila, whom we will get to give a conference talk one of these days, I swear:
I thought the three presentations that our team did this year were really well done and very well received. My friends continue to inspire me with their amazing awesomeness, and that's a great feeling. [personal profile] misskat and [personal profile] azurelunatic talked about our processes for welcoming newcomers to a project and helping them acclimate to the culture; [personal profile] misskat gave a second talk that addressed the same subject but with more information about in-group and out-group bias, which was super interesting; and [staff profile] denise gave a talk about communication techniques that could be used to (nicely) manipulate people toward a common goal.

I found myself thinking a lot about the creative process and how facilitating the creativity of others feels just as rewarding to me as actually creating something myself. Looking back over the sessions I attended, only two discussed specific open source projects. Everything else I attended focused on process, not product. And by process, I mean tips and tricks to facilitate collaboration, learning, productivity, and outreach. Everyone in attendance that I talked to seemed to share a common goal of improving the experience of contributing to open source, and I believe that goal was what caused the conference to feel so welcoming.  It was an amazing experience, and one I hope to repeat again at the earliest possible opportunity.

And [personal profile] misskat, who, in addition to the talk on cultural continuity she gave with [personal profile] azurelunatic, also gave Hacking In-Group Bias for Fun and Profit, a talk on psychology and how you can take people's tendency to view other people in the framework of in-group and out-group and use it for the purpose of good:
Ah, Portland! I'm a New England girl, born and raised, so theoretically the Improper Coast should be anathema unto my people. Still, breathing in the hippie-laden air of Portland was almost as good as being back in Massachusetts. There was so much AMAZING seafood! Seriously, so good. I live very far away from the ocean now, so having free access to tons of fresh seafood was magical, like Santa, or a bug-free code push.

ANYWAY. The conference, which is the reason I was in Portland in the first place, was super great. I had an awesome time presenting with Azz. Fun fact: we met in person for the first time that week, even though we've been friends since before Open Beta. Our talk went really well. We had the opportunity to chat about some of the social scaling lessons we learned back in Ye Olde Mysts of Tyme when we were inundated with fresh faces who needed to be properly indoctrinated into our culture. We had Storytime with Kat and Azz, and it was glorious. My favorite part was where we were talking about the Welcoming Dance in IRC, and someone from the audience joined our IRC channel... and was promptly welcomed by someone who wasn't even at the conference. Proof of concept: UNLOCKED.

My own talk on hacking in-group bias was pretty cool too. I get really excited about brains, science, and community culture hacking, so being able to smush them all up together was a very squee-inducing moment! The best part was where [ profile] pjf introduced me to Zotero, a browser plug-in which makes collating and citing sources SO NICE. Seriously, it has changed my life, mostly because I hate making works cited pages. I will be happy to babble on at length to anyone who wants to know more about brains, or science, or community culture hacking.

Other highlights included:

--needing to use the terminal to install something on my computer and talking myself into -sudo-ing the command because, as my internal Kat put it, "Paul Fenwick is literally sitting 10 feet away so if you break your computer, he can probably fix it." (Spoiler: I need to have more faith in myself, because the command worked perfectly, and barely anything ended up on fire.)

--Talking one of the other attendees into flying to Minnesota the next week for the scifi con that I help run. Turns out that Gargoyles are kind of a big deal!

--Watching the Dreamwidth crew assimilate a new person by sheer force of awesomeness.

--Did I mention the food? Because food. So many foods. Umph.

--Floating for an hour with Jen in a near-silent pool talking about families, MIT, Dreamwidth, and the future. That was one of the most relaxing hours of the entire conference, and I loved it so much.

So thank you, Dreamwidth. Thank you for giving us the opportunity to invest, not only in our own developers, but in the greater FLOSS community. Thank you. To Dreamwidth! SKOL!

My own talk was called "Slytherin 101: How To Win Friends and Influence People, about techniques you can use to communicate better with people. (And get them to do what you want them to do! For The Greater Good, of course.) Two highlights of my talk: taking a census of the room to see which Harry Potter house everyone identified with and, completely unsurprisingly, having 85% of the room raise their hands for Ravenclaw (and then having everyone in the room who knew me point at me when I asked who identified with Slytherin), and having someone come up to me after the talk and say, "I feel like this is the 'How to Adult' manual I kept expecting someone to hand me that nobody ever did."

The next conference that we're likely to be attending is Linux Conf AU (which is being held in New Zealand this year and is not solely about Linux, so the only purely accurate part of that name is the 'conf'). If you're planning on going, find us and say hello while you're there.


That's it from us for another update! As always, if you're having problems with Dreamwidth, Support can help you; for notices of site problems and downtime, check the Twitter status page; if you've got an idea to make the site better, you can make a suggestion. (I'm still a lot behind on the suggestions queue, though, just as a warning, and it's probably not going to get cleaned up until after I recover from surgery. So don't worry if it doesn't get handled immediately!)

Comment notifications may be delayed for up to an hour or two, due to the high volume of notifications generated after an update is posted to [site community profile] dw_news. This was posted slightly before 0830 EST (see in your time zone). Please don't worry about missing notifications until at least 1000 EST.
juliet316: (DW: TenII cleaning TARDIS)

[personal profile] juliet316 2014-07-14 12:47 pm (UTC)(link)
Very wonderful update as always.
quirkytizzy: (Default)

[personal profile] quirkytizzy 2014-07-14 02:03 pm (UTC)(link)
Agreed! Plus, KITTEH!
feicui: (Default)

[personal profile] feicui 2014-07-14 12:54 pm (UTC)(link)
I can't help but notice that the "New" section of the Select Style page hasn't been updated in a while. I only mention this because I can't actually tell which five themes are the new ones that have been added.

Thanks for the hard work as always! (And good luck with the surgery!)

Copier Cat =^..^=

[personal profile] babysprite 2014-07-14 01:32 pm (UTC)(link)
What's an office without a facsimile feline? =^..^=
siegeofangels: The angel from Guido Reni's "The Angel Appearing To St. Jerome" (Default)

[personal profile] siegeofangels 2014-07-14 01:39 pm (UTC)(link)
Ooh, it looks great on my phone. *___*
headcannon: (* and no one's gonna love you like I do)

[personal profile] headcannon 2014-07-14 02:09 pm (UTC)(link)
a fix for the problem of comments deeply nested inside a comment thread not being printed in some cases, and a fix for a problem where deeply-nested comments were causing too many closing tags to be printed, thus occasionally breaking a layout.

bless you bless you bless you bless you bless you bless you bless you bless you bless you bless you
lollobrigida: (TW = Jack Clueless)

[personal profile] lollobrigida 2014-07-14 02:27 pm (UTC)(link)
Thanks for the update! Good luck with your surgery, I'm sure you'll be in the thoughts of many DW users!

Just a quick question about purging deleted names. I've been tracking a few for over a year now and I'm not sure if these are just being done in batches and I have to be more patient, or if there is just too much of a strain put on servers for this, or if it's just been too busy to do purges, but I'm just curious if there is an ETA or not.
lollobrigida: (Default)

[personal profile] lollobrigida 2014-07-14 04:00 pm (UTC)(link)
Thank you!! I appreciate it.
lollobrigida: (Default)

[personal profile] lollobrigida 2014-10-03 05:39 pm (UTC)(link)
Hi! I'm just checking up on this. I'm not sure if I'm just impatient or if the to-do list is super long, but it's been a few months and I still am waiting on notifications for the purging of accounts that I know were deleted almost a year and a half ago.
soulhollow: (Veils of mist)

[personal profile] soulhollow 2016-10-09 07:46 pm (UTC)(link)
Hey there. I was wondering if there's a purge on the horizon--I've had an interest in a name that's been 'deleted and purged' for quite a while, but it's still hanging out as deleted/unregisterable.

Are we still able to track such names? I think there used to be a way to do it, but now I can't find it.
soulhollow: (Default)

[personal profile] soulhollow 2016-10-15 11:49 pm (UTC)(link)
That link doesn't seem to appear in Chrome or Firefox, for me. (I remember it, but it's definitely gone now.)

Pics or it didn't happen, etc. :)
Edited (Added screencap) 2016-10-15 23:52 (UTC)
groessteunterihnen: (Default)

[personal profile] groessteunterihnen 2014-07-14 02:32 pm (UTC)(link)
Browsing from a mobile device as we speak, and looking at a comm that seems to have been affected by the change ([community profile] amatomnes; I realize it's members-only but the immediately relevant thing doesn't require being a member to see) and for some reason my navbar at the top is all squished weirdly. It looks ALMOST okay if I hold the phone vertically, but when using it horizontally as I normally do as I have a flip open keyboard, the modules are all stacked vertically on the left with random open space on the right. I'd try to take a screencap but my memory card's been on the fritz so alas.

My point is, though, is it possible to redo the navbar itself to make it better accommodate mobile devices? Like having more of it tucked into menus to be tapped on to open instead of on display. As it is when I load the comm either way from my phone almost all I see IS the navbar, and I have to scroll just to see any of the page content, which is more frustrating to me than small text display sizes.

Edit: what I'm saying is, having two versions of the navbar depending on thhe device being used to browse, PC or mobile. Heck, I have a strong preference personally for sites that do that with their content across the board, especially if there's a way to opt out of the mobile version when using a mobile device!
Edited 2014-07-14 14:34 (UTC)
groessteunterihnen: (Default)

[personal profile] groessteunterihnen 2014-07-14 03:03 pm (UTC)(link)
Good to know, as that's definitely a bit of an eyesore right now.

Though again, I might be in the minority of mobile users here, but in general I prefer sites that essentially have an alternate "mobile version" altogether, and that allows for mobile users to opt to browse the regular site if they wish. I've run into several sites where the mobile version is more difficult for me to use than the rtegular one before, so it's something to consider.
owl: text editor with code, captioned "life would be easier if I had the source code" (source code)

[personal profile] owl 2014-07-14 07:58 pm (UTC)(link)
The problem with that is that you have to maintain the codebases for two sites, so every change has to be done twice. This is such a PITA that my employers, who have many, many more resources than DW, are in the middle of spending 3 years and millions of dollars merging their sites.
Also, what "the regular site"? How it looks on a tablet? A Chromebook? Double desktop monitors? an Apple TV?
groessteunterihnen: (Default)

[personal profile] groessteunterihnen 2014-07-14 10:16 pm (UTC)(link)
That actually is honestly my biggest issue with trying to make the site more "mobile-friendly": I'm concerned that in doing so, we'll end up with a site that looks and performs "okay" across most platforms, but fails to excel at any of them. I'd much rather use a site that looks great one a couple, and is a little clunky but still workable on the rest than that. It's also been my experience that when a lot of sites try to make themselves more "mobile-friendly" the end result is a site that's HARDER to use on mobile devices than the original was, which is why I find myself oping out of the mobile versions of sites when browsing on my phone on a semi-regular basis.

Considering that, as of right now, more than one of the comms I'm active in currently look bad or at least worse than before in both a desktop and a mobile browser, I'm definitely concerned about this ending up being a step backward instead of a step forward.
marahmarie: my initials (MM) (Default)

[personal profile] marahmarie 2014-07-16 03:31 am (UTC)(link)
Heck, I have a strong preference personally for sites that do that with their content across the board, especially if there's a way to opt out of the mobile version when using a mobile device!

Though again, I might be in the minority of mobile users here, but in general I prefer sites that essentially have an alternate "mobile version" altogether, and that allows for mobile users to opt to browse the regular site if they wish.

It's also been my experience that when a lot of sites try to make themselves more "mobile-friendly" the end result is a site that's HARDER to use on mobile devices than the original was, which is why I find myself oping out of the mobile versions of sites

Besides just wanting to point out that a) you want a separate mobile site yet b) you find yourself opting out of most of them, which is a steep contradiction in terms, I just want to add that adding/maintaining mobile sites is not generally user-friendly, with "I'd much rather use a site that looks great one a couple, and is a little clunky but still workable on the rest" being a big part of the reason.

People will access a website from a broad range of devices, from feature phones straight on up through smart phones, tablets, PCs, netbooks, and actual TV sets, so as a website owner and/or designer you want to make sure a site looks good and is perfectly usable across as many of those devices as possible, with perhaps even a bit more visual appeal on the most commonly used devices.

You can't do that by building what is usually a stripped-down version of a site, calling it the "mobile" version, then asking/simply expecting anyone who is not on the 1-3 devices the site is well-adapted for to go to the mobile site if the regular site isn't working for them. It's what websites did before responsive design came into play with CSS3 and HTML5 but the severe limitations of mobile design are what responsive design is supposed to address.

I think basically what you're saying despite the contradictions I see is "look and work great across everything but if not, then just look and work great across my top three most-used devices". Which is what any modern website should at a minimum be aiming for, with the caveat that the site should at least work well across all devices even if it doesn't look all that great, without using a separate mobile site that is time and money intensive to create, maintain, and update to achieve that effect.
Edited (clarity) 2014-07-16 03:39 (UTC)
groessteunterihnen: (Default)

[personal profile] groessteunterihnen 2014-07-16 04:53 am (UTC)(link)
That's actually exactly my issue--when you try to make a site work well across multiple platforms, however you do it, in my experience it behaves poorly on whichever it wasn't originally built to serve. In the case of having a separate mobile site, then at least it gives an option as opposed to, well, being stuck with something that's not that great no matter how you slice it.

The other thing is that, generally speaking, I find that most sites are geared towards an either-or when it comes to computers versus mobile. Where here I use "mobile" primarily to mean smartphones and similarly teeny devices; most tablets have a screen as big if not bigger than my laptop (which is teeny, yes, and I LIKE it that way) in which case you start running into a delightfully gray area of whether or not a "mobile" version truly is any better than the PC version anyway. But that digression aside, if I'm browsing a site that's obviously geared towards quick, mobile-based use on my computer, navigation tends to be clunky. Not because it's poorly made or anything, but the very FUNCTION of the site is not really the kind of site you use on a desktop computer. On the flip side, I've found myself frustrated when browsing mobile versions of websites on my phone, when the original website was serving a function that really is better suited to sitting at a computer to use anyway.

And for a blogging site, where posts are likely to be lengthy and contain all kinds of formatting, images, and other fun things (not to mention custom journal styles!) well... that's just not a thing that comes naturally on a tiny little mobile device like a smartphone. And I say this as someone who browses and posts comments here from my phone on a pretty much daily basis.

I mean... really, what's the point of doing custom styles and layouts and such if you're just going to effectively ignore it half the time? This isn't twitter where everything you post is always going to be short and sweet; posts and comments are often lengthy affairs, which inherently doesn't lend itself to small mobile devices by nature. Making it a little bit easier to handle, if possible without breaking things, is a great idea, but making the site look worse on both counts in the process? Noooot so much.
marahmarie: my initials (MM) (Default)

[personal profile] marahmarie 2014-07-17 02:33 am (UTC)(link)
most tablets have a screen as big if not bigger than my laptop (which is teeny, yes, and I LIKE it that way)

No shame in that! My current "laptop" is a Lenevo netbook, a very teeny-tiny little production, but confusingly enough it has 16:9 aspect ratio and a 1600 x 900 display. I practically need a magnifying glass just to clearly pick out what's on it (and in truth, I wear reading glasses to use it most of the time).

And for a blogging site, where posts are likely to be lengthy and contain all kinds of formatting, images, and other fun things (not to mention custom journal styles!) well... that's just not a thing that comes naturally on a tiny little mobile device like a smartphone. And I say this as someone who browses and posts comments here from my phone on a pretty much daily basis.

I mean... really, what's the point of doing custom styles and layouts and such if you're just going to effectively ignore it half the time?

OK, while I'm always 'rah-rah responsive design' on the face of things (simply because I absolutely hate the skeletal little imitations that mobile sites usually work out to be) your comment reminds me why I still don't like responsive design as much as I could - because you have to sacrifice a lot to use it. Once you get down to the size of the screen on my smart phone (it's like 320 by something and displays at 800 x 600 res) you lose context. Overview is so teeny-tiny, it's useless even if it does preserve design, navigation and tells you where you are; zooming in gives more clarity (but not enough: again, I need my reading glasses just to see even a zoomed-in web page) but zooming in also means, on something that little, that something must be zoomed out since it can't all fit on the same screen at once. So sidebars have to collapse beneath entries, nav menus beneath the sidebar, and many extraneous design elements have to go take a permanent hike. And yeah, it's frustrating to do a custom design like I do for my own DW, let's say, then see it either break on mobile screens or else to have to write slews of @media queries (my current solution to the problem) that take the design down to just bare-bones and changes font sizes and navigation elements to somewhat compensate.

Basically it's a physics problem where the screen can be so small only so much will fit on it. If you try to fit it all in as you normally would on the desktop or on a traditionally-sized laptop, you can't actually see any of it. If you try to fit in just some of it, you lose or have to rearrange other parts of your content to compensate. There really is no One Best Answer to all the dilemmas caused by this.
silver_trails: (Default)

[personal profile] silver_trails 2014-07-15 01:34 am (UTC)(link)
Is there a way to restore the side bar if you want it back?
spes_unica: (hobbits-schoko)

[personal profile] spes_unica 2014-07-14 03:45 pm (UTC)(link)
Best wishes for your surgery and get well soon!!!
brainwane: spinner rack of books, small table, and cushy brown chair beside a window in my living room (living room)

[personal profile] brainwane 2014-07-14 03:47 pm (UTC)(link)
Thank you for the post, and thank you especially for the conference reports!
denyamenti: (we were violent vicious)

[personal profile] denyamenti 2014-07-14 03:49 pm (UTC)(link)
You were helping run CONvergence?? I WANTED TO BE THERE FOR GARGOYLES but sadly could not. GOOD LUCK HAVE FUN DON'T STAY OUT PAST SUNRISE. I say this as the con has already passed but still

(Also the roleplayer's toast is the best :D)
Edited 2014-07-14 15:51 (UTC)
denyamenti: (Default)

[personal profile] denyamenti 2014-07-14 04:11 pm (UTC)(link)
I'd rather you stayed unholey, if it's all the same to you! :P
misskat: Picture of Kat with black plastic frames (Kat at CONvergence)

[personal profile] misskat 2014-07-14 04:03 pm (UTC)(link)
I was one of the subheads of Operations this convention cycle!

Funny you should mention sunrise, actually. One of the Wandering Hosts and I were heading out to the parking lot to investigate a report of someone being creepy in the parking lot, and I saw that the sky was starting to lighten. I was very, very upset about this, having been awake for 20 hours at that point!
denyamenti: (Default)

[personal profile] denyamenti 2014-07-14 04:13 pm (UTC)(link)
Someone being creepy in the parking lot just before sunrise sounds like a perfect setup for a fanfic, idk! But I hope you had a fantastic time, cons always come with jet lag but I've always found them worth it. It's just awesome to know there are still active Gargoyles fans around!

(PS sorry to hijack the news post!)
Edited 2014-07-14 16:14 (UTC)
amber: ⌠ ART ⊹ Panda&Girl ⌡ (Default)

[personal profile] amber 2014-07-14 04:24 pm (UTC)(link)
(The "to the roleplayers!" was a repeated toast during the week; we love y'all and your big, beautiful, gleeful embracing of the site and everything you can do with it.)

You guys are just the best. ♥ We love you too, Dreamwidth!
wytchcroft: heavent sent (cat)

[personal profile] wytchcroft 2014-07-14 05:10 pm (UTC)(link)
good luck with the surgery! :-)
sophia_sol: drawing of Combeferre, smiling and holding up a finger like he's about to explain something (Default)

[personal profile] sophia_sol 2014-07-14 05:46 pm (UTC)(link)
With respect to the new handling of multi-column layouts on mobile, is it possible to opt out? I understand that this change is helpful for many people but I prefer to always see my journal style in the three-column layout. If it is possible for me to continue seeing my journal on my mobile device in its original three-column layout I would appreciate it.
devilbear: (SPN: Dean knows you love him)

[personal profile] devilbear 2014-07-16 02:48 am (UTC)(link)
This is exactly what I came here to ask. My only mobile device is a tablet, and in general I hate responsive design... especially in the case of custom layouts. It's kind of messy, and not something I personally want on my blog. Please give us a way to opt our blogs out of this.
marahmarie: my initials (MM) (Default)

[personal profile] marahmarie 2014-07-16 03:58 am (UTC)(link)
It's just CSS adapted using @media queries to make the changes. Basically: open the CSS up in your browser's built-in CSS live editor (if your browser has one - I don't use the one included with my browser; instead I use the Web Dev for Firefox add-on) and erase the (in your case: four - all but the jump-link CSS) @media directives (including the opening and closing brackets they entail), copy the CSS that's left after removing the @media stuff and ensuing brackets from them into the custom CSS box on DW's Customize Style page, and add !important where needed until it all works again as it used to. I really ought to write up better directions than this (but the problem with that is there are dozens, if not hundreds of separate layouts on DW and at least four column choices to choose from with many of those, so it's really not possible for one person to show all of DW how to do the CSS-only version of overriding this).

ETA: they did your style wrong; I would open a Support Request for it. When I do what I told you to do with the CSS it converts your layout to one column. I'm pretty sure you were set at (and want it as) two-column so something is wrong that I think you might need Support to help you get fixed.

Addendum: my steps for removing the responsiveness via CSS work on [profile] sophia_sols layout (from what I can tell from within Web Dev) but not yours.
Edited (more info! because ah, wow, that's not working at all) 2014-07-16 04:20 (UTC)
devilbear: eleventh Doctor (Doctor Who) wearing a fez, profile view; text, "Don't Mess with the Fez" (Doctor Who: Eleven - Fez)

[personal profile] devilbear 2014-07-16 04:40 am (UTC)(link)
Thanks for the insight! I didn't even realize my browser had live css editing, so you've definitely pointed me toward an awesome, useful tool either way. :)

Unfortunately, I encountered the same issue which you did, so I've followed your advice and opened up a support request.
marahmarie: my initials (MM) (Default)

[personal profile] marahmarie 2014-07-16 04:45 am (UTC)(link)
Actually, you forgot to remove a bracket somewhere because I just learned this minute that that's what made it one-column for me as well. But yes, you do need to open a support request regardless because removing the @media language and all the corresponding brackets still leaves your layout exactly the same - completely broken with your sidebar overlapping your entries (in my case, I'm on 1280 x 1024 seeing that, if that helps you or helps Support any).

I've been fiddling with your custom CSS to see if there's a bad interaction between that and DW's base CSS (which is also quite possible, in hindsight) but I think the people in Support can probably figure that out much quicker than I can. Good luck. :)
devilbear: (SPN: Sam & Dean)

[personal profile] devilbear 2014-07-16 04:55 am (UTC)(link)
Hmm, I've triple and quadruple checked for brackets, but unfortunately it's staying one-column for me no matter what. I do have a slightly smaller (roughly 1100px width) window open for my browser, but even at full 1440 x 900 maximized it shows as one-column. I was able to toy with adding !important in a few places, but even that left me with huge margins and the 'modules' link etc. that should only be on one-column.

I do appreciate all the assistance, though! :) And hopefully support will be able to suss out what's going on. It's set to two-column, sidebar on left, so I haven't the slightest clue why my sidebar has migrated to live on top of my entries on the far right.
marahmarie: my initials (MM) (Default)

[personal profile] marahmarie 2014-07-16 05:09 am (UTC)(link)
OK, in my instance (1280 by 1024) it displays as two-column (with the sidebar overlapping entries from the right, not the left) at any size or screen res, unless I remove all the @media language but forget to take out an associated @media bracket - then it changes (of course, because I made a mistake by leaving an extra, unclosed bracket in) to one-column. Sorry for the confusion on that. As for fixing it on my end, I was able to do that just now by simply changing:

@media only screen and (min-width: 30em) {
.multiple-columns #primary {
float: left;


@media only screen and (min-width: 30em) {
.multiple-columns #primary {
float: auto;

And everything was fine again. If your layout is displaying one-column no matter what then you have a more serious problem than I can see from my end (which is "just" sidebar overlap - from the wrong direction, no less) since your custom CSS is designed to display as two-column-left. Hope they get it all sorted for you. :)

PS: as to why changing .multiple-columns #primary works, I have no idea, so I checked your HTML for column settings and one of the main body classes is actually .multiple-columns .two-columns-left which is like, whoah, why are they calling it by both classes? I would think two columns left is .two-columns-left and .multiple-columns should be reserved for three column layouts only, but on my end the screw-up is somewhere within those classes, regardless.

PSS: So I thought the .multiple-columns code was strictly a Tabula Rasa thing because I've never seen it before but it looks like they've freshly added it to all layouts. Huh. Yuck. I don't think anything under three column should be .multiple-columns; it just adds another layer of complexity/confusion (but it's probably been added just to carry off exactly the kind of @media query your layout is now bungling on, fwiw).
Edited (because I just cannot get enough of your layout) 2014-07-16 05:30 (UTC)
devilbear: (Boys Winchester)

[personal profile] devilbear 2014-07-16 06:14 am (UTC)(link)
I think I figured out what was wrong, though it baffles me why in the world it's proving so problematic. When I tried what you mentioned here, I ended up with this: which I noticed had ridiculously large entries, that managed to somehow get even larger when I maximized my browser window.

That led to me poking at widths in the custom css, which I never had realized weren't fixed pixel widths on their own. (I always use the same size browser window, and only rarely visit dreamwidth on my tablet.) Eventually, I came across this section:

#canvas {
width: 85%;
margin: 0 auto;
padding: 0;

#primary {
float: right;
margin: -2.25em 0 0 0;
padding: 0;

And with some poking, I was able to fix it by changing that to:

#canvas {
max-width: 85%;
margin: 0 auto;
padding: 0;

#primary {
float: right !important;
margin: -2.25em 0 0 0 !important;
padding: 0;

And that fixed it without having to remove the @media rules, or anything of that sort. I may just let it be, since that was such a pain and it took so much trial and error to figure out what would fix it, just with the @media rules in tact and whatnot.

I'm still not entirely certain why that was necessary to fix it, or how that was the fix, unless something about percentages no longer plays well with the default style. Either way, looks like your guess was right that it could be something in the custom css not getting along well with the updated theme. (Using !important on the width of #canvas didn't work; I had to switch it to max-width.)

Again, thank you for everything! If it hadn't been for your experience with this, and discussing it with you, I wouldn't have tried the things which led to figuring out the fix. ♥
marahmarie: my initials (MM) (Default)

[personal profile] marahmarie 2014-07-16 09:30 am (UTC)(link)
You're welcome! Glad to see you got it sorted. :)

It's neat to know either one of our fixes works (well, my fix worked on my end but not on yours, so maybe not); as to you having to add !important in so many times, in testing your edits on my end just now !important was only needed to make "margin: -2.25em 0 0 0" work right (maybe that wasn't working in the first place without !important added in, which in turn broke something else once DW added in the new @media CSS?).

(Using !important on the width of #canvas didn't work; I had to switch it to max-width.)

So to test I removed max- from max-width just now but it made no difference at all. Why we've had different experiences both in what we've seen - up until now that it thankfully looks the same - and what happens when we edit the same CSS is another question for the DW ages, I suppose.
Edited (clarity) 2014-07-16 09:32 (UTC)
devilbear: eleventh Doctor (Doctor Who) wearing a fez, profile view; text, "Don't Mess with the Fez" (Doctor Who: Eleven - Fez)

[personal profile] devilbear 2014-07-16 09:36 am (UTC)(link)
What gets even stranger is that I just tried again now for curiosity's sake, and at least with the live css editor removing the max- actually didn't break it. The only thing I can think of is that I altered that part first then added the !important declarations when it was still acting a little buggy. So maybe the !important declarations were actually all it needed? I never thought to go backward and check to see if the max- was still necessary.
marahmarie: my initials (MM) (Default)

[personal profile] marahmarie 2014-07-17 02:55 am (UTC)(link)
Yeah, I used to just add !important to everything that didn't work immediately in live editing, then rinse and repeat. It's an awful habit. Same with min-width, max-width, etc. I finally broke myself of those bad habits about 3-4 months ago by forcing myself to rewrite my design from scratch and test every edit I had ever made to see if it actually worked or not (result: most of the !importants were completely useless; some of my code was so not-doing-anything I was truly like, 'Wow, wtf I was thinking?' at times as I went through line after line of it).

Which finally taught me the best way to write or edit CSS is also the best way to write or edit s2 (which I learned from carriep63 over on LJ): write one line of code, compile, then check the result immediately before you move on to the next line. We don't use a compiler for CSS, of course, so with live editing it's even easier: just take the !important out that you've put in (or min- or max-on height or width, or whatever) and see what still works without it; if everything's OK, proceed to your next line of code. If not, there you go, put back in what you took out, then you can move on.

It's always better to double-check your code as you go than to have spaghetti code that you can't even barely untangle in the long run (it took me almost three months to get through my style sheet rewrite, if that gives you any idea how tangled-up my own spaghetti was).
Edited (typos) 2014-07-17 02:58 (UTC)
bybell: (Default)

[personal profile] bybell 2014-07-14 05:56 pm (UTC)(link)
Ah, that explains why the nav bar was looking squished!

Great to know, and good luck with your surgery. Hope it goes well and that your recovery is quick.
jenett: Big and Little Dipper constellations on a blue watercolor background (Default)

[personal profile] jenett 2014-07-14 06:07 pm (UTC)(link)
Finally playing with the mobile version: using an iPhone 5s (though I am still running 7.1.1 and have not done the upgrade to 7.1.2 yet, and using Five AM as a theme where the only modifications are colour.)

When I have the orientation lock on, and have it in portrait and look at my reading list, I get a weird thing where there's the column of text, but then there's a column of white to the right side (like where the sidebar would be, only there's no content: it's about 3/4 the width of the screen in portrait mode). If I turn the orientation lock *off*, that goes away.
I mention so that people can play with their locks in case of similar issues.

(Also, on the reading list but not on individual entries, I get the icon on the left side, and no text beneath it, and a half-screen-width column on the right with the text. In my dream world, there would be a way to display the icon at the top, and the full width of text in the entries below, but moving through to the actual entry gets me full-width text, so not that dire. Also Light mode works nicely.)
andrewducker: (Default)

[personal profile] andrewducker 2014-07-14 07:55 pm (UTC)(link)
Your talk sounds fascinating. Is there a video, or slidedeck?
misskat: Picture of Kat with black plastic frames (Default)

[personal profile] misskat 2014-07-14 07:58 pm (UTC)(link)
All the slides from all the talks are on the Dreamwidth SlideShare account.
andrewducker: (Default)

[personal profile] andrewducker 2014-07-14 07:59 pm (UTC)(link)
Thank you!

Edit: Slide 5 is garbled for me (Windows/Firefox and Windows/Chrome) - the text is layered over itself.
Edited 2014-07-14 20:01 (UTC)
misskat: Picture of Kat with black plastic frames (Default)

[personal profile] misskat 2014-07-14 08:10 pm (UTC)(link)

Unfortunately, I suspect that is a side effect of the platform and not something easily controlled. Which talk were you looking at?

andrewducker: (Default)

[personal profile] andrewducker 2014-07-14 08:16 pm (UTC)(link)
The Slytherin one.

(Just in case it was something easily fixed - it's not like it's a massive deal, and all the pages with content on them are just fine.)
marahmarie: my initials (MM) (Default)

[personal profile] marahmarie 2014-07-16 04:02 am (UTC)(link)
Saw that, too (using Fx 27 on Win XP).
maruniichimonji: (Default)

[personal profile] maruniichimonji 2014-07-14 08:04 pm (UTC)(link)
Totally irrelevant but OMG KITTY! Also, that is an amazing rug.

Keep up the awesome work, you guys!
styxiedust: I'm having me time. I'm eating cake (Pensive ✿ I'm trying to be celibate)

[personal profile] styxiedust 2014-07-14 08:30 pm (UTC)(link)
I went to my reading page and had this greet me: Linked now because I realized it stretched out the page, sorry.

It's not supposed to show the gray bar at all and this just started up today. Is there a way to fix this? My layout is set to two columns if that matters.
Edited 2014-07-14 20:31 (UTC)
momijizukamori: Green icon with white text - 'I do believe in phosphorylation! I do!' with a string of DNA basepairs on the bottom (Default)

[personal profile] momijizukamori 2014-07-14 08:57 pm (UTC)(link)
I suspect it's because we made changes to the navstrip, and your custom layout used to override it and now doesn't. Try going to the Custom CSS section of the style customizer and adding this:

#lj_controlstrip {
background-color: #FCE2F3 !important;
background-image: none !important;

Which should hopefully make the gray background the same pink as the rest of the navbar!
styxiedust: I feel the water would start boiling around you (Cheer ✿ if we tried baptizing you)

[personal profile] styxiedust 2014-07-14 09:01 pm (UTC)(link)
That worked, thank you!
momijizukamori: Green icon with white text - 'I do believe in phosphorylation! I do!' with a string of DNA basepairs on the bottom (Default)

[personal profile] momijizukamori 2014-07-14 09:02 pm (UTC)(link)

No problem!

incede: (vingt-huit.)

[personal profile] incede 2014-07-14 08:36 pm (UTC)(link)
Is that... is that a rug made out of jean pockets because that is amazing.
azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)

[personal profile] azurelunatic 2014-07-15 06:57 am (UTC)(link)
It is! D got it at Home Depot.
susanreads: my avatar, a white woman with brown hair and glasses (Default)

[personal profile] susanreads 2014-07-14 08:41 pm (UTC)(link)
Good luck with the surgery!

In the ocmmunity admin area, with the purple site scheme, I see the colours have been changed again. Now it's hard to tell visited and unvisited links apart, though not quite so hard as here in the news post. Please do some more tweaking! Everything else is looking fine so far.
gloriouscurse: (Default)

[personal profile] gloriouscurse 2014-07-14 11:03 pm (UTC)(link)
Thank you so much for all the info, and good luck!

[personal profile] jazzyjj 2014-07-14 11:37 pm (UTC)(link)
Thanks for the update. The site is still very easy for me to navigate with VoiceOver, which is nice to know. I say that because some sites tend to break accessibility when doing upgrades of this or that. But apparently not DW, so thanks for that. Regarding deleted accounts, the one I attempted to delete has totally vanished from cyberspace it seems so it looks like that functionality is working as it should. I was just sifting through previous news posts on here, and it seems as though there's tons of good stuff. When I have more time I'll certainly at least read these to get a better feel for the whole DW culture. But I absolutely love it on here thus far. Oh and thank you so much to those of you who have labeled your graphics with alt text. That helps out bunches! All righty then, I'm off to supper and then do other things which have been waiting. Best of luck once again on the surgery and recovery.
lannamichaels: Astronaut Dale Gardner holds up For Sale sign after EVA. (Default)

[personal profile] lannamichaels 2014-07-15 12:56 am (UTC)(link)
Thanks for the update! This is not a big problem, but it's a little annoying. I've had this problem on my desktop flist for a while, but it wasn't an issue on my phone (firefox app) until this new style and now it's suddenly there, too.

Basically, when I see a AO3 feed, there's something off with the backgrounds on the tags, so it overlaps, like so: (screenshot from my computer, not phone)

I don't know what causes this, it's perfectly fine when viewing things in the entry style, it's just on the flist style, it overlaps.

Do you know how I can fix this?
ninetydegrees: "Support Team, Mobilize!" & DW logo ala Batman (mobilize)

[personal profile] ninetydegrees 2014-07-15 06:03 pm (UTC)(link)
Hi Lanna!

This happens because the style you're using and AO3 feeds use the same CSS class so some styling applies here and it doesn't fit the way AO3 display tags in their feeds.

I think if you go to and add the following code to the big box ('Use embedded CSS) it should fix it:

.page-read .journal-type-Y .entry li .tag {
padding: 0;
Edited 2014-07-15 18:04 (UTC)
lannamichaels: Astronaut Dale Gardner holds up For Sale sign after EVA. (Default)

[personal profile] lannamichaels 2014-07-15 09:21 pm (UTC)(link)

Yay, thank you! CSS continues to be magic. :D

fyreharper: (Default)

[personal profile] fyreharper 2014-07-15 01:03 am (UTC)(link)
Ahh, so that's probably why I'm now having trouble reading DW on my phone :p

Going to (journal-skinned) individual entry pages - specifically, [personal profile] ysabetwordsmith's poetry - results in a one-column display with rather large text... large enough that extra linebreaks are getting added to the poem and I have trouble parsing. Switching to site-skin gives me lovely tiny font again, so thankfully there's that option for individual-entry pages at least.

Same issue on my reading page; the font is too large for the column width. It's like reading way down in a comment thread, except that everything is like that.

Actually, having played with resizing the screen... it looks like only one column is displayed, but that column is using slightly less than half of the page width (the right side is background-colored blank space). The header bar also only displays across that same half of the page width. And zoomed out so that phone width = page width (instead of column width) gives the font size that I am used to seeing.

[iphone 4S, still using iOS 6.1.3]

[personal profile] ratfan 2014-07-15 01:04 am (UTC)(link)
Good luck with the surgery. Re kitten, I have young pet rats who once achieved a screen capture with their feet and have found many shortcuts unknown to me. Couldn't manage without them.

rose_cat: (Default)

[personal profile] rose_cat 2014-07-15 06:57 am (UTC)(link)
They sound more talented than my cat with her big klutzy feet :)
misskat: Picture of Kat with black plastic frames (Default)

[personal profile] misskat 2014-07-15 12:42 pm (UTC)(link)
My friend's cat once managed to completely uninstall Cinnamon, my computer's desktop environment, by walking across the keyboard a few times.

Cats: seriously.

Page 1 of 2

<< [1] [2] >>