Links

  4. Updating to the latest Plex build on a Raspberry Pi

    I finally found a way to upgrade to the latest Plex build on a Raspberry Pi.

    I run my own media server using Plex on a Raspberry Pi 4. It performs really well and has the added benefit of low energy usage thanks to the Pi.

    I’ve been struggling to upgrade to the latest build using the usual sudo apt update and sudo apt upgrade commands. Since some of the features on the Android app won’t work without the latest build I decided to find an answer.

    In the comments of a tutorial blog post someone had found a solution.

    • On the Raspberry Pi, nagigate to /etc/apt/sources.list.d/
    • Type sudo nano plexmediaserver.list
    • Remove the # from the line of code #deb https://downloads.plex.tv/repo/deb/ public main
    • Press cmd+x to exit the file
    • Type y to accept changes
    • Press enter to save

    Then upgrade as you would normally do.

    • Type sudo apt update
    • Type sudo apt upgrade
    • Type y to confirm the upgrade
    • Once it’s completed type sudo shutdown -r now

    After a few minutes reload your Plex client, you should be on the latest build.

  6. TBM 50/53: The Curse of Success Metrics

    @johncutlefish shares his observations of why teams find success metrics challenging and how to help them make more impactful progress.

    1. Uncertainty is a good thing, it means there is opportunity to learn and make change.
    2. Be flexible. Follow the spirit of experimentation and try something different.
    3. Create a culture of safe failure and encouraged learning.

    Consider the term "success metric". We've already jinxed the effort. We are already afraid of failing and learning.

  7. Setting up a Raspberry Pi as a bridged wireless access point

    @Raspberry_Pi’s straightforward guide for getting wifi into those hard to reach places using a Pi as an access point.

    Since the lockdown I’ve had to be inventive in my home working setup to overcome wifi dead zones.

    Our garden office is one such place. Although we’ve got an ethernet cable installed I sometimes forget to manually switch off wifi and it’s generally a faff. I’ve also got one of those new MacBooks with just USB-C ports so plugging is going to be yet another adapter. We’re also just out of reach of the home wifi meaning our mobiles fall back onto mobile data, racking up pretty big data bills.

    Since I had Raspberry Pi 3b+ awaiting it’s next duty and a bit of spare time over the festive break, I followed this excellent tutorial to setup setup an access point. It worked a treat!

  8. A Comprehensive Guide to Accessible User Research: Part 2 – Recruitment and Preparation

    @BrianGrellmann’s second blog post of a series about taking an inclusive approach to accessibility in design research.

    Things to consider:

    • Recruitment
    • Recruit a mix of disabilities and assistive technology
    • There will be overlap (Intersectionality) - focus on access needs and technology used
    • Stimulus
    • Ensure the fidelity and execution of the testing stimulus is accessible to those who are testing it (functional HTML = assistive technologies)

    Recruitment examples:

    • Generative / Discovery research - broad approach for variety of disabilities, assistive technologies, behaviours.
    • Iterative design - focus on matching participants and prototypes, broader inclusion of access needs across studies.
    • Evaluative research - more specific to cover a a variety of disabilities and assistive technologies.

    Accessibility all the way:

    • Telepresence software, consent forms, surveys, PDFs should all be accessible.
    • Lab / testing location and furniture accessibility.
    • Be prepared and allow for more time to make any alterations of specific requests.

  9. A Comprehensive Guide to Accessible User Research: Part 1 – Project Planning

    @BrianGrellmann’s first blog post of a series about taking an inclusive approach to accessibility in design research.

    Things to consider:

    • Goals
      • Continuous research with fewer participants or dedicated research with more participants (former is better)
    • Fatigue
      • Longer sessions ~90mins
      • Review the session design to avoid fatigue
    • Budget
      • Potentially a harder recruit, allow for more recruitment time and incentive cost
    • Location
      • Some labs may have specific accessibility software but need to be accessible
      • Paricipant’s home/workplace offer more contextual insight to other access needs
      • Location of test incurs more travel cost
      • Remote tests must use accessible software and ability to capture audio (screenreader)