Twitter: @ewenmcneill -- November 2019

Fri Nov 01 05:49:55 +0000 2019 (#)

Replying to @theunfocused and @BR3NDA

It took me ages (many years) to figure out I do react to the gluten type in oats as well. My reaction to oats was sufficiently lower that I only figured it after an extended break from oats.

But yes, a different gluten form, and an oats gluten reaction seems to be less common.


Sun Nov 03 04:16:57 +0000 2019 (#)

Replying to @nturley47, @mithro and @tomu_im

For anyone else wondering, this is the original tweet about the animated logo, and the build code. (Looks like the compiled demo SVG isn’t online at the original location any more.)

https://mobile.twitter.com/nturley47/status/1169769145292021760 https://mobile.twitter.com/nturley47/status/1190272062629302273 https://github.com/nturley/tomu-animation https://logs.timvideos.us/%23tomu/%23tomu.2019-09-06.log.html


Sun Nov 03 04:45:50 +0000 2019 (#)

Replying to @nturley47 and @mithro

FTR I was able to rebuild it on Ubuntu 18.04 with:

git clone https://github.com/nturley/tomu-animation.git cd tomu-animation sudo apt-get install nodejs npm npm install npm build

Output in dist/character-anim.svg (and prebuilt version is in gh-pages branch).

Still looks very cute animated 💚❤️💙


Sun Nov 03 22:05:41 +0000 2019 (#)

Replying to @__fincham

“Were in the grander central city, and our service is apartments” 😃

Seems very much like a “search term” named business, which I always consider a warning sign.

Hope the rest of the trip was good!


Sun Nov 03 22:10:14 +0000 2019 (#)

Replying to @__fincham

*We’re


Mon Nov 04 03:19:30 +0000 2019 (#)

Replying to @johnedgarpark and @sophywong

To be honest one of the main reasons I document things online is for my future self: I write the documentation I was hoping to find when I searched the first time (if I have time to do so).

So it’s only disconcerting to find it again if it turns out to be wrong/misleading 😃


Mon Nov 04 03:26:09 +0000 2019 (#)

I’m surprised to find my comprehension of Le Franglish is still remarkably high even though I don’t consider myself all that fluent en Français.

It seems pidgin languages are quite useful for comprehension! 🦋 https://twitter.com/LehmannDrC/status/1191101639156994049


Fri Nov 08 21:23:49 +0000 2019 (#)

Replying to @mjdominus

“What stopped you from using sshd?”

Assumes they thought of the obvious answer, tried it, and it didn’t work, but that why it didn’t work isn’t obvious and sheds more light on real problem.

(Avoiding pejorative words like “just” helps a lot with perceived tone too 🙂)


Mon Nov 11 23:32:02 +0000 2019 (#)

RT @BenNadel: Nothing makes you more humble than having to maintain a single codebase for years. Only then do you really get see the full e…


Tue Nov 12 07:33:36 +0000 2019 (#)

RT @tveastman: This is appalling. I like to think I can take pride in @FlyAirNZ but they have to do better than this. I know they can. ht…


Tue Nov 12 07:39:49 +0000 2019 (#)

Replying to @tveastman

All it needed was someone, other than the passenger, taking responsibility for finding out precisely the process, and ensuring that process was followed for the whole journey. Ie, compassionate helpful customer service.

Rather than “she’ll be right” brush offs 🙁


Tue Nov 12 08:09:06 +0000 2019 (#)

Fascinating Yak Shaving talk about restoring the PDP / Vector General Graphics Display used to do the original Star Wars vector CGI . A bunch of the scenes are 50+ seconds rendering per frame, for wireframes.

https://m.youtube.com/watch?v=_mtLUws1bOk


Tue Nov 12 08:30:19 +0000 2019 (#)

Replying to @developerjack

Off the rack then tweaked? Or all made to measure?

As someone who is usually 1-2 sizes smaller than commonly stocked jackets, I’d been secretly hoping you had a magic shopping location where all choices were available in a useful range of sizes 😃


Tue Nov 12 08:59:36 +0000 2019 (#)

Replying to @hroethgar

Oh I gave up a long time ago expecting to find anywhere in my own city that stocked anything more than one deviation from “average”.

I was just clinging to the hope there’d be somewhere, maybe in Jack’s hometown, that had a better range. But even that’s been hard to find 😢


Tue Nov 12 09:04:06 +0000 2019 (#)

Replying to @developerjack and @hroethgar

Thanks! That’s a quite reasonable approach. And it’s definitely a bit easier for me to find “fits shoulders” than “fits properly”, at least in a bigger city than my hometown.

(Sorry your jacket got stranded at the dry cleaners, by 30 minutes; hope you found another option!)


Tue Nov 12 09:22:36 +0000 2019 (#)

Replying to @developerjack

I’d be very “how many can I carry away at once” if I could find $50 blazers that I liked, which could be made to fit well for under another $100 🤔

The few options I’ve found over the years have been much more expensive up front, or occasionally affordable second hand.


Sat Nov 16 21:14:08 +0000 2019 (#)

RT @nnja: Didn't make it to #supercon?

You're not the only one. It's such an amazing event that hundreds ended up on the waitlist.

Luckil…


Sat Nov 16 22:15:09 +0000 2019 (#)

It looks like they’re doing the Hackaday Supercon Live Streams on YouTube as one Live Stream per talk (two so far). So check the talk schedule and look for new Live Stream near the talk start time.

https://hackaday.io/superconference/ https://twitter.com/nnja/status/1195772098355949569


Sun Nov 17 01:02:16 +0000 2019 (#)

RT @RealSexyCyborg: A lot of you saw the recent Medium article/documentation.

I'm (finally) a good bit blunter and more succinct about *e…


Mon Nov 18 22:34:22 +0000 2019 (#)

Replying to @hroethgar and @chrisjrn

I agree that “welcome newcomers” is mentioned as the intent of the PacMan “rule”.

But I disagree that it’s been communicated as “optional if you need to exclude someone”. (And the rest of your group might not know about the Missing Stair anyway.)


Mon Nov 18 22:37:53 +0000 2019 (#)

Replying to @chrisjrn

Important question.

My immediate thought is to describe PacMan as a way to welcome others and invite people to do so if they’re open to others joining the discussion group. Kinda like “communication level” stickers, but physical positioning.


Mon Nov 18 22:40:45 +0000 2019 (#)

Replying to @chrisjrn

Unfortunately there’s still the Missing Stair problem: some of the group might be open to others joining, and others in the group may not (or need to avoid certain unstated others).

I don’t have a solution to that. (Other than Talk About The Missing Stairs. Which is hard 🤔)


Tue Nov 19 06:06:08 +0000 2019 (#)

RT @AccordionGuy: When “Woman yelling at cat” meets “American Chopper”, magic happens.

http://www.joeydevilla.com/2019/11/18/when-memes-collide/


Tue Nov 19 06:41:17 +0000 2019 (#)

Really interesting talk from Hackaday #SuperCon 2019 by @sophywong talking about mixing textile and 3D FDM printing techniques together. Her current project reminds me a lot of flexible armour in look, but made way more efficiently 💚💜

https://m.youtube.com/watch?v=Z9jChZtsVhA


Tue Nov 19 23:42:44 +0000 2019 (#)

Replying to @Foone

Where do we pre-order this book? :-)

I’ve had some contracts that were like 25% that amount of insanity, and honestly just ended up firing the client (“no I’m not renewing another month”).

I’m in awe you survived that level of red tape / Yak Shaving and saved the data!


Wed Nov 20 06:12:36 +0000 2019 (#)

RT @Benjojo12: But what has this got to do with the green screen?

Well. YUV = (0,0,0) is green:

http://www.mikekohn.net/file_formats/yuv_rgb_converter.php

The data you are…


Wed Nov 20 06:54:49 +0000 2019 (#)

Another interesting talk from Hackaday #SuperCon 2019: @kpimmel talking about designing and building a custom automated slider for taking stereo pair photographs, as video, for an immersive view.

I love the fusion of art and tech 💙

https://m.youtube.com/watch?v=aUAeNts1Sug


Thu Nov 21 00:32:15 +0000 2019 (#)

Me, configuring DellEMC S5248F: I’d like this port to be 10G.

S5248F: You have to change 4 ports at once.

Me: sigh Okay.

S5248F: Done. Your port names now have a :1 suffix.

Me: ?

S5248F: It’s a subport.

Me: How many subports?

S5248F: 1.

Me: …

S5248F: …


Thu Nov 21 04:40:30 +0000 2019 (#)

Replying to @tveastman and @SlackHQ

Not that I’ve found, and I spent a while looking.

FWIW you can just type Markdown into it like before.

FYI, one thing that made it a bit less annoying was discovering that the right arrow would step out of formatting when the “wrong thing” editor chose the wrong insert point.


Thu Nov 21 04:51:03 +0000 2019 (#)

LinuxConfAu Miniconf speakers occupy a weird middle ground between attendees and conference speakers that’s never been properly resolved 🤔 It’s made more complicated by Miniconfs being explicitly banned from having their own sponsorship/funding, and getting zero budget from LCA. https://twitter.com/slyall/status/1197097727126986753


Thu Nov 21 08:25:10 +0000 2019 (#)

Replying to @ajdlinux and @voltagex

Yes, the way that LCA Miniconfs are considered made more sense 10-15 years ago.

I agree it’s past time to rethink how it works now. IMHO the Miniconfs are 50% of the conference (content) now, so it feels unfair to speakers that it’s treated so differently to main conf speakers.


Thu Nov 21 20:16:26 +0000 2019 (#)

Replying to @The_McJones

I too help run a Miniconf (with @slyall), and have seen this get raised year after year with no change.

I didn’t realise there were Miniconfs following the “better to ask forgiveness than ask permission” model, but I do understand why they would do that.


Fri Nov 22 05:13:09 +0000 2019 (#)

Replying to @The_McJones and @slyall

I quite like the PyconAU model of having a general funding pool to help people; “speaking” being but one assessment criteria.

A couple of LCA have done that. But often it’s not been clear if it’d happen until after people decided they couldn’t afford to speak at a Miniconf 🙁


Fri Nov 22 05:19:55 +0000 2019 (#)

Replying to @chrisjrn, @The_McJones and @slyall

Advertising financial assistance being available, in advance, is the key thing: people are making “can I afford to attend” decisions, especially if speaking (Miniconf or otherwise), months in advance.

(I didn’t realise the PyconAU model had changed. Thanks for the details.)


Fri Nov 22 05:26:34 +0000 2019 (#)

Replying to @The_McJones, @chrisjrn and @slyall

Free hobbyist ticket (by request) is a reasonable level for Miniconf speakers I think (free pro for “main conf” selected speakers).

Some less privileged people will still need travel/accommodation assistance to attend though; especially now that’s often much more than ticket.


Fri Nov 22 19:26:34 +0000 2019 (#)

Replying to @textfiles

I feel like I’ve spent my whole life training for this question 😃

6+ years daily on CPC6128, Z80 assembly and some hardware expansions, Linux/Unix sysadmin/programming, etc.

Like others, I have limited time. But would love to help where I can.

Thanks for starting this 💚💙💜


Fri Nov 22 19:26:40 +0000 2019 (#)

RT @textfiles: I'm reaching out to fans of both the Amstrad CPC and doing tedious QA testing of Amstrad CPC emulations to build a library o…


Fri Nov 22 19:39:38 +0000 2019 (#)

Replying to @ADuckIsMyFiend and @joshsimmons

The last few years it’s usually been possible to get free Miniconf Day Only tickets for Miniconf Speakers.

That’s helpful for getting a wider range of local speakers, who maybe aren’t interested in the whole conference.

But less attractive to those with higher travel costs.


Fri Nov 22 23:45:33 +0000 2019 (#)

Replying to @ADuckIsMyFiend and @joshsimmons

🙁

Unfortunately it’s up to individual (per year) LCA conference organising teams how they do ticketing. And as a result it’s a bit inconsistent what ticket types are offered.

I wish I’d known their issue a year ago as I’d have argued for Miniconf Speaker Day ticket.


Sat Nov 23 01:25:52 +0000 2019 (#)

Replying to @kattekrab, @chrisjrn, @The_McJones and @slyall

It definitely needs a larger, cross year, thoughtful redesign. But I feel like that redesign discussion has been left in the “too hard” basket for too long.

I think there’s a “works for most” solution possible, which also caps costs for conf budgets.


Sat Nov 23 01:30:27 +0000 2019 (#)

Replying to @kattekrab, @chrisjrn, @The_McJones and @slyall

FTR the issue is made worse in the last few years as Miniconf CFPs are now through the LCA website, which asks Miniconf Speakers to indicate on CFP if they need financial assistance.

Then Miniconf Orgs are left deal with the fact there’s none available/possible.


Sat Nov 23 20:00:54 +0000 2019 (#)

Replying to @KathyReid

Thanks for engaging with this topic.

FTR, I’m not expecting a change of ticketing this year (or maybe even next year). And I agree LCA2020 team are doing a good job.

But inevitably live issues prompt discussion of future improvements. 1/n


Sat Nov 23 20:03:49 +0000 2019 (#)

Replying to @KathyReid

For LCA2020, if there’s no support at all for Miniconf Speakers, then the (LCA2020 provided) CFP form should not ask Miniconf Speakers if they need support. It’s false hope, and leads to difficult conversations with potential speakers. I posted this on Miniconf list. 2/n


Sat Nov 23 20:07:04 +0000 2019 (#)

Replying to @KathyReid

For the future, obviously budgeting for any discounted/free Miniconf Speaker ticket/financial aid needs figuring out in advance. Which starts at least a year out. Hence the “continuous improvement” discussion getting mixed in, because it needs considering now for 202[123]. 3/n


Sat Nov 23 20:13:35 +0000 2019 (#)

Replying to @KathyReid

(For the future) it’s entirely possible to have a middle ground between “all Miniconf Speakers” get something and (the existing situation) of “no Miniconf Speakers” get anything. Eg, “up to 2” Miniconf Speakers can financial aid, chosen by Miniconf Org/others. 4/n


Sat Nov 23 20:18:46 +0000 2019 (#)

Replying to @KathyReid

Speakers needs/means/etc vary. Some can pay their own way out of pocket, some have generous employers. Others are less privileged.

That’s true whether or not they’re “Main Conference” Speakers or Miniconf Speakers. But the two categories are treated very differently. 5/n


Sat Nov 23 20:24:29 +0000 2019 (#)

Replying to @KathyReid

I’ve been to LCA every year since 2004. I understand the history of why Miniconf Speakers are treated differently.

Especially now it’s the same CFP platform, speakers CFP round two, it’s time to examine the “it’s always been that way” in the current context for the future. 6/n


Sat Nov 23 20:31:03 +0000 2019 (#)

Replying to @KathyReid

That’s a “broader than any LCA year volunteer team” discussion. But due to the 1-2 year lead times, it inevitably is going to overlap with some year’s organising team work 😃

7/n


Sat Nov 23 20:33:47 +0000 2019 (#)

Replying to @KathyReid

Somehow the LCA community needs a way to have that discussion of future shape, without it turning into “it’s too late to change anything this year” each time it comes up 🙁

I’ll stop here as Twitter threads are terrible for nuance. But I’m open to discussing this elsewhere. 8/8


Sun Nov 24 03:56:37 +0000 2019 (#)

Replying to @KathyReid

I think it’d be good to capture the points raised ASAP into a shared document (Git{Lab,Hub}, Google Doc?). Plus any responses to that summary.

Then try to have a BoF at conf to actually reach workable future plan based on points in that doc.

cc/ @slyall @chrisjrn @The_McJones


Wed Nov 27 01:05:12 +0000 2019 (#)

Replying to @__fincham

It feels like one only figures out what shares a power circuit when it ends up turning off 🙁

(There’s a reason I’ve suggested “let’s turn off side A power to the rack and see what happens” to one of my clients testing a vendor whole equipment rack install… 😃)


Wed Nov 27 01:14:11 +0000 2019 (#)

Replying to @__fincham

Indeed! I had to pull out one of my home UPSes earlier in the year as I found it was causing more power instability rather than less 🙁

(Even after replacing the battery. My guess is “tired capacitors” or “too many power spikes.)


Wed Nov 27 01:14:19 +0000 2019 (#)

RT @textfiles: ATTENTION USERS OF TWITTER. Did someone who know or know of make the huge mistake of dying before clicking through a 2019 Te…


Wed Nov 27 01:22:20 +0000 2019 (#)

I’m now idly wondering what this will mean for third party sites using “Sign in with Twitter” for auth when faced with usernames being reused…

… seems unlikely every third party site will have planned correctly for “Twitter usernames could be reused” scenario 🤔 https://twitter.com/verge/status/1199425300821684224


Wed Nov 27 01:25:05 +0000 2019 (#)

Replying to @__fincham

Heat certainly won’t help electrolytic capacitors any! Quite possibly it just started failing and spiraled downwards.

My home UPS that went unreliable was a cheaper APC. But probably 10+ years old by the time it was “less reliable than no UPS”.


Wed Nov 27 01:42:25 +0000 2019 (#)

Replying to @lin_nah

There’s lots of accounts that should be archived, including one of a late friend which I know I can’t get into (has 2FA, which is gone).

Archive Team are going to try to backup what they can where people tell them about it. (I’ve already submitted.)

https://twitter.com/textfiles/status/1199459588594176000


Wed Nov 27 04:12:59 +0000 2019 (#)

RT @textfiles: OK, the many kind volunteers who helped up to this point have gotten the Amstrad CPC Emulation-in-Browser section working we…


Wed Nov 27 05:28:14 +0000 2019 (#)

Replying to @__fincham

I’d take idempotent (“if fail, try again) over “I guess you’re finding a SPI Flash programmer” 😃


Wed Nov 27 08:12:21 +0000 2019 (#)

Replying to @developerjack and @RyanMRuark

Yes, those are the sort of edge cases I had in mind. OAuth indeed has internal tokens for IDs, etc, which should go away and prevent fake logins.

But people make lots of invalidated assumptions about (user)names, and this is first mass test, so I’m expecting bugs 😃


Wed Nov 27 08:16:28 +0000 2019 (#)

Replying to @RyanMRuark and @developerjack

Yup. @hintjens is a late friend of mine, and in a similar situation. I’ve referenced a bunch of those tweets in the past.

(I’ve already added it to the Archive Team “please save” list, but wish there some way to keep it on Twitter. But 2FA required, and gone 😢)


Wed Nov 27 08:19:14 +0000 2019 (#)

Replying to @RyanMRuark and @developerjack

At minimum a less terrible alternative to “not logged in for 6 months” is on first pass just apply delete to unused accounts / mostly unused accounts (eg, less than 10 Tweets).

Or just require email to still work, and have a “save this account” link that doesn’t require login.


Wed Nov 27 08:27:39 +0000 2019 (#)

Replying to @Amys_Kapers and @developerjack

It’s definitely possible for third party sites to do it correctly and cope with renames / reuse of names.

Did everyone use the API correctly, without unwarranted assumptions? And test it properly? History says “unlikely” 😃

(And this is first large scale test.)


Wed Nov 27 20:53:11 +0000 2019 (#)

RT @FaithNaff: Remember, women contribute to the prevalence of toxic masculinity when we shame and belittle men for daring to show any femi…


Wed Nov 27 21:01:38 +0000 2019 (#)

RT @timberners_lee: I'm very concerned about the sale of .org to a private company. If the Public Interest Registry ends up not being requi…


Wed Nov 27 21:04:59 +0000 2019 (#)

RT @merxplat: Maybe designers should have a chaos monkey that inserts death at random places in their customer flows 🐵 💀

That’s my startu…


Thu Nov 28 00:47:07 +0000 2019 (#)

RT @adamadzp: Hi @Twitter, please consider the possibility of memorialising accounts. I often refer back to my late partners tweets as a re…


Thu Nov 28 00:53:49 +0000 2019 (#)

Casually downloading my Twitter data today. Just in case, ya know. 🦋

Settings -> Your Twitter data -> Download your Twitter data -> Download an archive of your data -> Twitter -> Request Archive


Sat Nov 30 08:35:16 +0000 2019 (#)

Replying to @__fincham

Yeah, about an hour ago my (line interactive) UPS was constantly flicking in and out (I heard the relay) for a worrying number of minutes.

Possibly some regional national grid imbalance, as it felt long enough to be being fixed by “spin up new supply”.


Sat Nov 30 08:38:22 +0000 2019 (#)

Replying to @nzkarit and @__fincham

Voltage range is much wider than frequency range. At least 220-240 V from memory, maybe more. They’re allowed to let voltage move to try to maintain frequency.

But sudden major loss of supply can be hard to handle quickly without dumping a bunch of load (ie area blockout).