D. Joe is a user on mastodon.technology. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

D. Joe @ritjoe@mastodon.technology

D. Joe boosted

What are your preferred alternatives to Google Drive's shared documents for writing/editing? Preferring ones which don't require accoutn/login!

Please Boost!?

D. Joe boosted
Next from #LibrePlanet 2018, learn about "Free software in academia" from a variety of points of view, with a panel of Morgan Lemmer-Webber @mlemweb, Tom Callaway @spotrh, Stephen Jacobs and D. Joe Anderson: https://u.fsf.org/2j3
D. Joe boosted

@slp
Sounds like you're derailing. Actually people can multitask and just because people are working on trying to deal with the issues of hacker culture, doesn't mean they don't also care about whatever the 'smartphone battle' is. And ya also dealing with community problems is a lot more accessible of a battle than fighting Google. I do both, deal with the community and fight Google. Don't say that one of the things I do distracts me from the other that is what's derailing.

D. Joe boosted

Dear free and open source community,

I want you to recommend projects that welcome people that never contributed to FOSS before. I am planning to do a workshop this year to encourage people to make their first contributions. What I need:

- A page explaining how they could contribute.
- General recommendations and documentation.
- Where they can contact people involved in such projects in case they have questions.

D. Joe boosted
@webmind @z428 @megfault @slp The thing is, FLOSS has great gui. Right now I'm using Tusky. What FLOSS lacks in the battle with proprietary is promotion. Proprietary secrecy and gatekeeping gives them a power imbalance which allows for rent extraction, which can then be reinvested in promotion activities, and so the ball keeps rolling. FLOSS mostly doesn't have that option available.
D. Joe boosted

Candid of me, by my daughter

She was only 4 and wanted to play with dads camera. This is one of her shots.

flic.kr/p/suvUJn

disclaimer: I helped crop it a bit. :)

#FOSS #FreeSoftware #photography #portrait #artwithopensource

D. Joe boosted
D. Joe boosted

I'm late to the #introductions, but here it goes. I'm 30, she/her, from #Germany. I work as a environmental scientist at a university, pursuing a PhD degree. I need some #python #programming skills to do that.
I'm fairly into #crafts, especially #fiberarts like #knitting and #sewing.
I enjoy #boardgames a lot, I also started playing #shadowrun about a year ago.
#games like #citiesskylines or #civilization5 have quite a few hours on my steam account.
Plus: Trying to improve my #french ;)

D. Joe boosted

Also, coming from Kansas I just gotta say: New Jersey is such a cute little miniature state.

D. Joe boosted

So she came home from her shift at the checkout and rode her motorbike up the coast to practice. Just past this bridge she called me full of her wild ride.

She’s still 17. She earned this motorbike in a year of 5am and 6am shifts.

This evening she said “how do you guys deal with it, knowing you can just get up and go anywhere you want? How do you live with it?”

Focusing on the bike I’d missed what a milestone this is: that specific threshold of freedom.

#smallstories

D. Joe boosted

I've made it halfway through my crazy two weeks... Today was a Bernstein Centenary Day 'Total Embrace' at my uni (I was the organiser/instigator) and it involved 6 sessions run by me, colleagues, and my MA students- ranging from an academic panel, to a community choir, to a showcase of a recent musical theater performance. Super fun that Dame Patricia Routlege came and participated in the WHOLE day. She is lovely.

Two days rest and it's the Netherlands for the next event.
#thisday

D. Joe boosted

I volunteer with a group called Virtually Connecting that organizes virtual conversations with people at conferences, to link them with people who can’t attend. We have a bunch of conferences in April, including one more session for Creative Commons Global Summit Sunday April 15 3:45pm eastern time (Toronto, Ontario, Canada). See here for that event and see website for other events coming up! virtuallyconnecting.org/blog/2

D. Joe boosted

I've signed up for an open online course on Learning Analytics Fundamentals, with George Siemens and others. I'd like to know more about what the hype is about: courses.edx.org/courses/course

Classes are now over for me and I just gave our final exam, so all I have left is marking...thus I think I should be able to complete this four-week course!

D. Joe boosted
D. Joe boosted

OLPC retrospective • Utopian project to give laptops to kids in poor nations did not end well theverge.com/2018/4/16/1723394 #linkblog

D. Joe boosted

PyPI postmortem • Failed rollout for the Python package hosting, nice writeup status.python.org/incidents/1y #linkblog

D. Joe boosted

While everyone is here listening to me talk about GitLab may I humbly share my one blog post I wrote for them about #research #reproducibility?

about.gitlab.com/2017/08/25/gi

D. Joe boosted
D. Joe boosted
Some #Spectre/#Meltdown Intel microcode update observations:

At work we have the same hardware for each of the developers (corporate-mandated Windows laptops). We develop in GNU/Linux VMs. We received them when we were purchased back in April by a larger company.

There's a full compiler stack I wrote for the development of certain systems. It uses Saxon and is therefore really heavy on resources (and syscalls). Lots of inefficiencies. (Don't write your next compiler stack in XSLT. I wouldn't have if I knew it was going to become what it is today.)

I noticed that newer devs' systems, with identical configurations, were taking more than twice the amount of time to compile the same software using this stack. A coworker and myself spent a bit of time debugging and it was eventually found to be the microcode. Once my coworker updated his Intel microcode and BIOS to include the Spectre and Meltdown mitigations, the virtualization performance was terrible---over 100% performance degredation in this case (~5m for a normal build without mitigations, ~12m after mitigations). That's far worse than any benchmarks I've read. Disabling the microcode mitigations restored performance to previous levels.

What a mess.