Shipping Swag 📦

Hugh Wells — Fri, 01 Jan 2021 19:13:31 +0000

Hey y'all!

I've decided to start off 2021 with a little project. Throughout 2020 I shipped a tonne of swag to attendees for hackathons and events alike.

So for all you hackathon organisers, I've put together swagshiphack.dev for all your swag distribution needs 🙌

Feel free to ping me an email if you'd like any help making your online event that little bit more awesome 💯

Shipping stickers for You Got This 2020: From Home

Hugh Wells — Mon, 31 Aug 2020 20:32:27 +0000

You Got This is a community conference series which focuses on the non-technical, often emotionally-labourious skills needed to be successful at work. In June, they ran their first online conference - You Got This From Home. They decided to provide a little sticker joy to all attendees during these tough times, and collected addresses during sign up for those that wanted a little surprise to arrive on their doorstep.

Coco Chan

@_crmzchan_

Happy mail! 📮😍

Thank you @yougotthisconf @crablabuk

10:24 AM - 24 Jul 2020

0 2

The event was run by Shy and Kevin, and while Shy handled the sticker distribution throughout the Americas, I was the person who handled all of the shipments across Europe and Asia. Shipping 300 sets of stickers gave me a good excuse to (potentially) overengineer a solution to make it happen, and here's how it went down...

Sanitizing Data

First step was to sanitise the address data. This had already been sorted by country and region via SmartyStreet's API and the data looked like this:

id,full_name,address,country,region
51,The Queen,"Buckingham Palace, London, SW1A 1AA, UK",UK,EU

The first thing to note is the address is (usually) comma delimited. Some people used full stops (others didn't use anything!) but most used commas to indicate each line of their address. As the plan was to put this through a mail merge, the first thing was to replace these commas with line breaks (I used Python):

import csv
with open('data.csv', newline='') as csvfile:
    reader = csv.DictReader(csvfile)

    with open('output.csv', 'w', newline='') as savefile:
        writer = csv.DictWriter(savefile, fieldnames=reader.fieldnames)
        writer.writeheader()

        for row in reader:
            row['address'] = row['address'].replace(',', '\n')
            writer.writerow(row)

This did what you'd expect, and replaced any "," characters in the address field with "\n".

Preparing Envelopes

Next step was to design a template to directly print onto the envelopes. Since Linux and OSS rocks, we're using LibreOffice here. Kevin came up with a beautiful design:

Once we've selected our document size with Format -> Page Style and selected C6 (the size Kevin's design was for), we can then insert some placeholders for the data we're going to mail merge:

You might think those are text boxes, but they're not! LibreOffice cannot mail merge data into textboxes, so these use a LibreOffice concept called frames. You can place these via Insert -> Frame -> Frame Interactively, and then dragging out the frame like a textbox. It will have a border by default but by with Right Click -> Properties, you can customise this:

Once completed, you can modify text within the frame as normal (eg. font, colour, size etc).

If you are using LibreOffice as installed by default on a Linux distro, it's likely you won't have their database package, Base, installed. With apt you need to type sudo apt install libreoffice to get the all the missing components. (You can install just Base, but it does have a few dependencies you'll need to install as well).

You will also be likely missing the database engine Base needs (you will later get "General input/output error" when trying to interact with a database). This is also installable via apt: sudo apt install libreoffice-sdbc-hsqldb.

Importing our CSV into Base is a bit weird (you can't directly use a CSV to mail merge).

Open Base and create a new database
You do want Base to "register" the database (this makes it available to other LibreOffice applications automatically), and by clicking Finish you should be promped to save it
You should now have the database open in Base. You now open your CSV alongside it in Calc
You now select all your data and copy it to your clipboard. In Base you go to Edit -> Paste and a menu will appear!

The rest is fairly self-explanatory. You will need to create a new primary key field (which Base will autoincrement for you) - I wasn't able to get it to accept the existing one.

Going back to you LibreOffice Writer template, by selecting View -> Data Sources you will now see your database you just created:

Drag on the column names, and drop into your frames where you'd like that column to appear:

Phew. Almost there.

Printing Envelopes

Use the standard print dialogue in LibreOffice and select Yes when it asks if you want to print a form letter. I did try printing directly to the printer from LibreOffice but it crashed during the process, however small I made the job.

However, you can instead ask LibreOffice to merge the data to individual files; I chose PDFs:

Depending how big your database is, LibreOffice will think for a while. You'll find some very nice looking envelopes in your destination folder:

(spot the error: I didn't run the line break script on this CSV)

I then wrote a little Bash script to queue all the PDFs for printing:

for ((i=1;i<=278;i++));
do
    lp "$i.pdf"
done

And you'll just need to sit and wait then! It took around 4 hours to print all 278 envelopes on an HP inkjet. You can then use your database to query how many of each region you're sending to, which is useful when buying stamps (we were going to use a franking machine, but it broke).

Then time to stuff all those envelopes and stick very expensive special stickers (aka stamps) on the front!

I hope you enjoy your stickers, and I also hope this guide is helpful to anyone else using LibreOffice for mailmerge :-)

~ Hugh

Jodie

@jodieneville

Thank you for my stickers @yougotthisconf 👨‍🚀🤜

14:18 PM - 29 Jul 2020

0 6

PS. You're incredibly welcome. I had a lot of fun doing it!

glitchlock with Wayland

Hugh Wells — Sat, 25 Jul 2020 15:29:04 +0000

I have created a fork of the popular glitchlock script (which used i3lock and i3lock-color) to work with swaylock in Wayland.

https://github.com/crablab/glitchlock

Using YouTube Subtitles for a drinking game

Hugh Wells — Wed, 20 May 2020 20:30:15 +0000

YouTube Subtitles

A friend suggested this concept, and I was sufficiently bored of revision to make a quick MVP.

The idea is that you take a selection of videos from your favourite YouTuber and analyse their most used phrases; which you must drink on, each time someone says them.

Link to Code

crablab / youtube-subtitles

youtube-subtitles

A Python CLI application which will extract the most common phrases from video subtitles, and present them to you.

Probably most useful as an amusing game.

Installation

Requires:

Python3

Try running it, if you're missing any packages then just install them with pip. Apologies for no pipenv.

Setup:

Create a .env in the repository root with the following values:

YOUTUBE_KEY={Your YouTube API key}
CLIENT_ID={Your YouTube OAuth2 Client ID}
CLIENT_SECRET={Your YouTube OAuth2 Client Secret}

You'll need to go to cloud.google.com and enable the YouTube Data API where you can then generate these values.

Note: the permissions scope required is https://www.googleapis.com/auth/youtube.force-ssl

Useage

Run with python3 main.py.

Copy and paste URLs to YouTube videos. Supply a null value to perform the analysis.

Try to include as many of the outputted phrases as possible, in normal conversation.

Future

This was a Sunday afternoon project - don't expect miracles.

I might:

View on GitHub

How I built it

This is a simple Python 3 application you can run at home. I might make it into an actual website at some point.

Issues:

It uses up a stonking great chunk of YouTube "quota". There are some small tweaks I could make to improve this: better filtering the subtitle tracks before downloading them etc.
The text analysis is a very basic moving window frequency analysis. It is not clever and contains no AI or ML! Room for improvement.

DEV Community: Hugh Wells