Update on the Dreamhack server

Mar. 24th, 2017 03:29 am
sophie: A cartoon-like representation of a girl standing on a hill, with brown hair, blue eyes, a flowery top, and blue skirt. ☀ (Default)
[personal profile] sophie posting in [site community profile] dw_dev
Hi all,

As you may know, about 2-3 weeks ago the Dreamhack server died. Since then, [staff profile] mark and I have been working on getting its replacement going, and updating a few things.

It should be ready to go in a few days, and I wanted to make a few notes for when it comes back up:
  • Firstly and most importantly, you'll need to re-apply for a Dreamhack if you want one, and you'll be set up as if you were a new user. Any changes that you pushed to GitHub will be available, but any other data you may have had will be gone - apologies for that.

  • I do still have email addresses for everybody who had an account when the server went down, and I'll send out a one-time email to everybody when the server is up to point them to this post. After that, the only people who will receive emails about Dreamhacks will be those who have applied for one.

  • The address you need to use to log into the server via SSH will be different from the Web address domain. The email you receive when applying for a Dreamhack will state this clearly.

  • The new server will have an increased quota. The earlier quota of 500MiB was enough at first, but since then the space taken by a base install of Dreamwidth has risen to 270MiB. In light of this, I've raised the quota to 750MiB.

  • You won't need to do a one-off compilation of the stylesheets and JavaScript any more unless you make changes to them - the new-user script will automatically do that for you, and your Dreamhack will have working CSS out of the box.

  • Each user will automatically get a test database called "test_dreamhack_<user>", accessible using the same database user and password as the main database. You'll still need to configure it properly yourself for now, but the installer will at least copy the required files to $LJHOME/ext/local/t for you to configure. Later on I'm hoping that it'll be possible to have it configured automatically.

  • The official email address to contact me has changed - you should now use my Dreamwidth email address (sophie at dreamwidth dot org). Automated emails will come from this address, so if you had the previous email whitelisted you may want to whitelist this new one instead.
Thanks for your patience with this - there's a lot that's been going on, but the new server should be ready to go very soon! Watch this space. :)

If you have any questions, please leave a comment! I'll answer any questions you might have.

Health and Safety gone mad?

Mar. 22nd, 2017 12:52 am
gerald_duck: (Oh really?)
[personal profile] gerald_duck
I was window shopping in IKEA today, and made an impulse purchase of quite a nice looking cordless drill/screwdriver. I do have an ancient Black and Decker cordless screwdriver, but it's not a pistol-grip, it's not a drill and it uses obsolescent VersaPak NiMH batteries which make it pointlessly heavy.

My decades-old mains hammer action power drill is still going strong and I'll continue using it for heavy-duty work, but I'm looking forward to having something cheap and cheerful with which to drill pilot holes, etc.

Anyway, the instructions say "WARNING: RISK OF TRAPPING Do not hold the front sleeve of the chuck with one hand at the same time as you open or close the jaws of the chuck with the help of the drill/driver's motor." Provided you're not an idiot and you use a low speed and torque setting, is this a real problem? Trapping what, where? Are they just covering themselves, or am I being overly blasé about a significant risk?

Of course, I'd already done that several times without incident before I bothered to read the instruction manual…

The key to the conundrum

Mar. 22nd, 2017 12:45 am
gerald_duck: (whoops)
[personal profile] gerald_duck
This morning, I was woken early by a cold-caller. When I heard the doorbell ring, I grabbed my keys out of my jeans pocket, hurriedly donned my dressing gown and headed downstairs.

Once I'd dealt with the unwelcome visitor, I decided to pop to the loo before returning to bed.

Later, I woke up, performed my ablutions, got dressed and went to leave the house. At this point I discovered my keys weren't in my pocket. They weren't in the dressing-gown pocket, either. I wasted a good five minutes retracing my half-asleep meanderings as best I could but, apparently, unless I was somehow so totally confused I posted the keys out my letterbox or flushed them down the loo, they'd apparently vanished into thin air.

Then I had a brainwave: I took the spare set, knowing that if I waited until this evening I ought to be able to find the keys courtesy of the tritium glow-stick fob.

Sure enough, this evening I found the keys… in the back pocket of my jeans. I'm sure I checked there at least twice this morning. Grr.

In other news, I now understand why my car's seat didn't feel quite as comfy as usual today.

Announcing the Shim review process

Mar. 21st, 2017 01:29 pm
[personal profile] mjg59
Shim has been hugely successful, to the point of being used by the majority of significant Linux distributions and many other third party products (even, apparently, Solaris). The aim was to ensure that it would remain possible to install free operating systems on UEFI Secure Boot platforms while still allowing machine owners to replace their bootloaders and kernels, and it's achieved this goal.

However, a legitimate criticism has been that there's very little transparency in Microsoft's signing process. Some people have waited for significant periods of time before being receiving a response. A large part of this is simply that demand has been greater than expected, and Microsoft aren't in the best position to review code that they didn't write in the first place.

To that end, we're adopting a new model. A mailing list has been created at shim-review@lists.freedesktop.org, and members of this list will review submissions and provide a recommendation to Microsoft on whether these should be signed or not. The current set of expectations around binaries to be signed documented here and the current process here - it is expected that this will evolve slightly as we get used to the process, and we'll provide a more formal set of documentation once things have settled down.

This is a new initiative and one that will probably take a little while to get working smoothly, but we hope it'll make it much easier to get signed releases of Shim out without compromising security in the process.

Buying a Utah teapot

Mar. 20th, 2017 01:38 pm
[personal profile] mjg59
The Utah teapot was one of the early 3D reference objects. It's canonically a Melitta but hasn't been part of their range in a long time, so I'd been watching Ebay in the hope of one turning up. Until last week, when I discovered that a company called Friesland had apparently bought a chunk of Melitta's range some years ago and sell the original teapot[1]. I've just ordered one, and am utterly unreasonably excited about this.

[1] They have them in 0.35, 0.85 and 1.4 litre sizes. I believe (based on the measurements here) that the 1.4 litre one matches the Utah teapot.
kaberett: Overlaid Mars & Venus symbols, with Swiss Army knife tools at other positions around the central circle. (Default)
[personal profile] kaberett
... presented as a series of e-mails, sent/received over the past week or so.

Read more... )

ANTHONY NOLAN. AREN'T THEY GOOD.

Sociable weekend

Mar. 19th, 2017 03:01 pm
azurelunatic: (Pacifica)
[personal profile] azurelunatic
Friday: I woke up at a sensible hour, and did housework. Purple emailed me about the afternoon's beer bash, and I collected myself to go to that. I was running a little late, but made it at last, just before Purple arrived himself. I ran into a few people, and saw people from my old team sitting around the fire pit.

I collected with them there, and Purple soon joined me.

One of my old team had been going through some significant personal changes; she talked a little about that. I gave her reciprocal information, and my card with my real name, and the information to join the tech-slack. (Later, I would ping a former colleague who had done some pioneering work on that process in this workplace, and thank her, since it sounded like my old teammate had gone through a much better experience with the workplace bureaucracy than the former colleague had.)

She and Purple proceeded to talk synthesizer projects until she left to catch her train.

I will need to email my old manager about when to visit in the next few weeks.

The food offerings were surprisingly edible for the context. It was corned beef and cabbage sandwiches with slightly inexplicably rubbery rolls, some under-fried potato-and-cabbage fried things (tasty, but with the consistency of glue), various very green vegetables (cucumber, peas, broccoli, asparagus, and possibly more), cheese soup, and ... green hummus. No green beer, though.

It was a gorgeous evening, not quite too warm. We were joined by the Scruffy Canadian briefly. Someone who I thought might be the Cute Receptionist wandered by. Since I'd missed connecting with her the last time I thought I saw her, when she got close enough I called the name. In case it was her.

It was her. We caught up a bit. Purple teased me.

We hailed lb as he was headed out of the office with his deep dish pizza leftovers. There was a good chat, including some wtf-ery over a github thread that a new arrival in channel had shared (and participated in). There are some statements, such as "An SJW's work is never done", which have radically different meanings based on the context of the person who said it, and since we don't know them that well yet, we are uncertain whether this person is working for the greater good, or complaining about people working for the greater good.

There were dinner plans. I nearly accidentally left my phone in Purple's office until it tweeted.

Dinner was nice. We really should go to the Thai restaurant near the Trader Joe's more often, since it's delicious, close, and reasonably priced. Despite the bell peppers, prawns, and peanuts in nearly everything. (I am attempting to figure out whether peanuts take the surface of my mouth off the way walnuts do, because that would just be ... perfect.)

The Signal app has resolved some of its issues for voice calls, and my partner and I were able to talk nearly all the way home. It only cut out at the place that still gets me a lot on regular network calls, where 35 joins 280 by San Andreas Lake.

It's lovely to say a sleepy goodnight to my partner as we both settle into our beds, and go to sleep with the connection open, knowing that the other is there. I swapped my old Douchebag Headphone (the around-the-neck model with the earbuds) for one that purportedly connects to two devices automatically (it did not, but it wasn't a downgrade) and thus my partner got my old one. (It so happens that I'm the one who digs leading-edge tech, and they like to squeeze every last drop of usefulness out of old tech, so we are an excellent pair there.) They are enjoying it. I was delighted when I saw them in it, because the colors are accidentally representative of both of our favorites.


Saturday started out quietly, with various audio and video chat. One of the video chat things was marred by no helpful audio coming through from the other end; I should have reset when I noticed that it wasn't doing so well.

A friend just had some technically-minor surgery, and I had made plans to go over and say hello and congratulate this weekend. There was a little bit of plan-changing, but in the end I went over there in the afternoon and said hello and such. My aunt had stopped by with some fabric for me and some cashew butter for them. Due to the placement of the surgery, we kept ourselves to heartfelt arm-clasps and some back-patting.

When I got back down to the street, I discovered that a Very Large Pickup Truck had pulled up alongside me with its hazard lights on. Unfortunately, the driver was nowhere in sight, and I wasn't sure if I had enough room to pull out. (I was parallel parked, with a sedan nearly touching my bumper in the back, and a Prius a good distance in front of me, and less than a car length of space on the diagonal to get out.) I decided that I would make one try at it, and if I didn't have clearance that I was comfortable with, I would stop and wait for the driver to return.

It turned out that even though I think there was only one foot of clearance on each side, I was able to get out. (My partner cheered me on.)

I wound up picking up dinner on my way home. They did manage to get my order wrong, although in a different way to what I thought: I thought they'd gotten the wrong thing to the right receipt entry; they had in fact gotten the order entirely wrong from the receipt on down. The replacement was also subtly wrong, but I was not going to argue at that point. (My partner, who had been on the phone the entire time, heard my order and was able to verify that if it was a hallucination that I'd said that, it was a shared hallucination.)


The calendar sharing is going well so far.

There had been an incident. (My partner and I arranged a date; it hadn't gone in their calendar because they thought they'd remember it. Unfortunately, three people managed to step square in each other's complicated traumas, and it took a while to recover. With a lot of communication and crying.) After that, I shared my social calendar with my partner (not the full-on calendar with the specifics on the doctor appointments and such). I also shared the "shadow calendar" I'd made for them, the one that has their work schedule and all the stuff that they tell me about when we're planning our weeks. It's not yet time for us to share a single social calendar.

My partner has shared that calendar on with the friends they're staying with until the situation with the ex gets cleared up. They're not quite comfortable sharing it with others ... just yet. That may change, as the weeks go on.

Today, I'm setting up the week to come, and doing the various communication that goes with it. It's not sexy or glamorous, but it's the little bits of caring contact that helps sustain a relationship. I have to remember to translate the four to five calendar entries that make up one doctor-type appointment into a single block in the social time, ideally when entering it, but at minimum when setting up the week to come.

My attention deficit disorder was diagnosed in the fall of 2015. For a while, I'm not sure exactly how long, I've had to start with the actual time of the actual event I'm going to, and schedule backwards and forwards from that, in order to make sure I have a fair chance of getting there on time and in good order.

First I enter the event, with its actual duration.

Then I figure out where I'm going to be before the event, and figure out how long it takes me to get to that place from the place I am going to be before that. (It usually takes me an hour or so to get from home to any given place in the city of San Francisco; 45 minutes to get to old-work; an hour to get further down-peninsula; anywhere from 30 minutes to over an hour to get across the Bay.) I make a separate calendar entry for the transit time, with a little wiggle room.

I figure out where the next place I need to be is, and I do the same thing for that side.

I then give myself an hour's notice to start getting ready, even if I'm scheduled for something else at that time.

If it looks like it's close to my likely sleep time, I count back an hour further and allocate that as wake-up time. (If I haven't slept enough, I will use the wake-up time for an extra hour of sleep, and try to do any complicated prep the night before. Using a checklist, if possible. Sometimes this warrants an entry of its own.)

If it's early enough, I will count back eight hours from the wake time, and schedule that as sleep.
When it's a scheduled sleep time, I will have to schedule myself a bedtime reminder, which is an hour before sleep.

Sometimes, there's a chance that events will run long. In the case of my regular dentist, they've been known to run an hour late. So for them, I schedule in that buffer time. Just in case.

If it's a doctor appointment, the actual appointment goes in my bright red non-negotiable deadlines calendar, and all the ancillary things get in my main calendar. If it's not a doctor or similar, the main event goes directly in my personal calendar.

When it's something that's going to affect my social calendar, the fore and aft transit times and the event itself get globbed into one block of time that I'm unavailable for other events. Since my social calendar can be shared with people who don't need any personal details, unless it's a public(-ish) event, it gets described in vague terms. Dr. X at this address on this floor for this purpose gets vague-ed into "Doctor Appointment."

Stuff in my partner's shadow calendar get vague-ed up the same way. Why yes, my partner is going to X event at Y venue, there is a topic, and they're going with Z. That is "With Z at [vague description]." Or "Date with Z." Before my partner shared the calendar with their hosts, I scrubbed back through and edited a few items that I'd put on there, which had a little too much detail for general consumption. Even so, their hosts were clearly reading through past events, because I overheard Ms. Documentation read out the title of one (with some questions), and I promptly collapsed in giggles. Oh, dear.


There are two current crocheting projects, one of them started a while back. The older one is the penis-based sex ed hat, a sequel to the vagina-based one. So far I have urethra, bladder, glans, some ductwork, and I need to stuff the first testicle before I can close it up. (The testicle is blue, naturally.) I will probably put a drawstring or something on the scrotum so the testes can be examined easily.

The other one is a lace nightgown out of black #10 crochet-cotton thread. I'm putting #6 clear blue-green iris beads on it here and there. We'll see how long I take to finish that one. The beads are in a narrow prescription bottle that fits nicely inside the ball of thread.

I have been going back to paper to-do lists for daily use, and attempting to scan them into my image archives. I've started dating them so I have a better idea of how things went. It's been a fairly reasonable system for reminding me of what I need to get done, and I can move things forward in a helpful way. Sometimes I start pages ahead of time for stuff that needs to be done on a specific date.


After a week and a half of the new meds, I am encouraged at what they're doing with my sleep. That may wind up being a separate entry.

Photobucket

Mar. 17th, 2017 02:41 pm
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla posting in [site community profile] dw_maintenance
Thanks to everyone who let us know that Photobucket images were not loading properly on some pages. The problem seemed to be mostly limited to HTTPS requests; Dreamwidth maintains a list of known high-traffic image sites that support HTTPS, so that our secure content proxy service doesn't cache them unnecessarily. Unfortunately Photobucket seems to have recently changed their site configuration such that HTTPS requests aren't being served as expected, and we've now taken it out of our list of "proxy-exempt" sites.

If you continue to have issues, make sure you're not using HTTPS Photobucket links. It's a bit counterintuitive, but if you use HTTP instead, it will be automatically transformed on our end to an HTTPS link that uses p.dreamwidth.org.

Hope that clears everything up for now! Let us know if it doesn't...

Opticians

Mar. 15th, 2017 05:02 pm
damerell: NetHack. (normal)
[personal profile] damerell
Dear Lazyweb, if you live in Cambridge and go to an optician, who is it and are they annoying? Thanks.