det.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon Server des Unterhaltungsfernsehen Ehrenfeld zum dezentralen Diskurs.

Administered by:

Server stats:

1.7K
active users

#hackday

0 posts0 participants0 posts today

Homeless Hackday

shkspr.mobi/blog/2012/07/homel

I had a great time at the Homeless Hackday. This is a belated write up, because I wanted to let a few thoughts peculate.

The Problem

There has been a worrying rise in the number of people rough sleeping - especially in the capital. There are a number of charities and Government departments which are available to help people who are homeless.

They wanted a smartphone app / mobile web site which would help tackle homelessness. Either by helping people people directly or by allowing members of the public to get homeless people the support they need.

Language Matters

We quickly ran in to some language barriers.

  • "Report A Homeless Person" - it's not illegal to be homeless. They're not a nuisance which need reporting to officialdom.
  • "Tag a homeless hotspot" - tagging also has negative connotations.
  • "Alert the authorities" - again, these are people; not a chemical spill.

It becomes very tricky to find a neutral way that conveys to a user what the app is for, while still respecting the dignity of the homeless.

Our solution

We came up with an elegant solution. A simple mobile website which would geo-locate the user, allow them to input basic details about the homeless person they were trying to help, and then pass that information on to the council.

Here's our full presentation.

Mobile Payments / Donations

I coded up the donation part of the service. Using ImpulsePay, I was able to create a two-click donation form. The payments are processed by your mobile network provider, so there's no need to type in any credit card information.I also used jQuery to build a slider - this encouraged playability. A user can slide the bar to see what their donation will buy. This allows them to get a more personal sense of where their money is going and (hopefully) encourages them to donate more.

Understanding a Hackday

We received one piece of negative feedback which, on reflection, I think exposes one the inherent tensions in a hackday. I'd suggest reading both Thayer Prime's blog post and Emma Mulqueeny's blog post for some eloquently expressed thoughts about what Hackdays are and are not.

The Homeless Hackday was very up-front with developers with regard to intellectual property rights, and what was expected of us. What I'm less clear on was whether all the agencies who came understood what the purpose of a Hackday is.

During the building of the hack we were asked several times "oooh! Could you add....?" The answer to which is "Yes, given sufficient time and budget!"

In any project there's a dilemma concerning the amount of time allocated between planning and building. The crux of a Hackday is to keep the scope extremely limited. It should be possible to show how the product could evolve, but that doesn't mean building it or even taking it into account when designing.

On demoing the mobile donation part, the immediate feedback was

How do you determine the recipient of the donation? Not every charity is a good one - and some hinder rather than help.

That's a very fair question - but it leads to a complicated answer which you can't easily give in a 3 minute demo.

More than that, it assumes a huge amount of subject knowledge. The majority of developers came to the Hackday with zero sector knowledge and had to pick it up in the 8 hours they have to hack.

The politics of the situation is totally outside the scope of what anyone can be expected to build.

Furthermore, any hackday demo is - almost by its very nature - conceptual. It almost certainly won't deal with edge-cases, deviations from the happy-path, or even having two people use it simultaneously!

A Hackday demo is axiomatically a demonstration of a quick hack. It shows you what could be possible given limited information and minimal coding time.

Summary

Overall, the Homeless Hackday was a great experience. It took me out of my comfort zone, made me engage with an issue to which I previously had given very very little thought. It was wonderful working with people dedicated to helping those less fortunate.

In many respects, it was the perfect Hackay. A well defined problem, a solution which could improve the lives of many people, and a good set of data to work on. And the requisite amount of pizza and cake.

I just wish that the limits of what a Hackday can produce was made clear to everyone involved.

Terence Eden’s Blog · Homeless Hackday
More from Terence Eden

Alexa Skills - get custom slot names using Flask-Ask

shkspr.mobi/blog/2019/06/alexa

Amazon encourages developers to use Flask-Ask - the handy Python library for working with Alexa. Sadly, the project has been abandoned. They no longer take pull requests, you can't raise bugs against it, and the documentation is incomplete.

So this is how I solved an annoying problem - how to get the name of a custom slot.

Here's the code, with a fuller explanation afterwards.

from flask import Flask, render_template, requestfrom flask_ask import Ask, statement, question, sessionapp = Flask(__name__)ask = Ask(app, '/')@ask.intent("YourIntentName")def your_intent_name():    content = request.get_json()    name = content['request']['intent']['slots']['YOUR_SLOT_NAME']['resolutions']['resolutionsPerAuthority'][0]['values'][0]['value']['name']

Yeuch! What's going on?

Alexa lets us define custom slot names - these can be associated with any spoken text. For example, I might want the slot name "car" to be sent whether the user says "car" or "automobile" or "vehicle" or any other synonym.

In my case, I want to send my API the ID Code of a hospital.

If the user says "John Radcliff" or "Oxford" or "John Radcliff Hospital" - then my API should receive the ID RTH08. It can then use that ID in a separate API call.

Here's the JSON that Alexa sends our API (I've truncated it for ease of reading).

{    "request": {        "type": "IntentRequest",        "requestId": "amzn1.echo-api.request.1234",        "timestamp": "2019-06-17T06:54:52Z",        "locale": "en-GB",        "intent": {            "name": "CarPark",            "confirmationStatus": "NONE",            "slots": {                "hospital": {                    "name": "hospital",                    "value": "John radcliff",                    "resolutions": {                        "resolutionsPerAuthority": [                            {                                "authority": "amzn1.er-authority.echo-sdk.amzn1.ask.skill.1234.hospitals",                                "status": {                                    "code": "ER_SUCCESS_MATCH"                                },                                "values": [                                    {                                        "value": {                                            "name": "RTH08",                                            "id": "abc123"                                        }                                    }                                ]                            }                        ]                    },                }            }        }    }}

A bit verbose, but easy enough to parse.

I've moaned before about Alexa skill development - but it is getting worse. As you can see from the above screenshot, the development website's contrast isn't great - which makes building a skill physically painful.

Add to that the outdated tutorials, the weird terminology, the multiple sites to use, broken links, and abandoned libraries... It's hard to feel enthusiastic about building more skills.

Amazon have gone down the classic route of paying developers to build for their platform. But I don't think that's enough.

The Alexa team need to work on the developer experience. A GUI like NODE-RED could be used to help build skills in one place. Why is it so complicated to deploy and test skills? Where are the official libraries which "just work"?

I honestly believe that one of the things holding back voice assistants from their full potential is the poor developer experience.

Terence Eden’s Blog · Alexa Skills - get custom slot names using Flask-Ask
More from Terence Eden

10 Jahre #Hackday #Moers - zwei Tage mit voller inhaltlicher Druckbetankung, am zweiten Tag auch wieder verstärkt zu #OpenData und #LinkedOpenData #LOD während am ersten Tag noch #KI in der #Verwaltung (leider) dominierte (sich verstärkender Fachkräftemangel, chronische Unterfinanzierung, eher unattraktives Arbeitsumfeld und ungünstige Organisationskultur werden stochastische Papageien nicht nachhaltig kompensieren, sie lenken eher von den eigentlich zu ergreifenden Maßnahmen ab).

moers.de/veranstaltungen/hackd

10 Jahre, die nicht spurlos vorbeigegangen sind (sofern man damals nicht als 13jähriger Teilnehmer eingestiegen ist).

oh, wow. We just heard from @darestiet that there is an upcoming #webxdc #hackday workshop called "Transcend the limits of your group chats: collaborative apps" ...

WHERE: townhall of city of #Moers

WHEN: Saturday afternoon 2pm.

We can't remember to have heart about this before so it's very short notice only, maybe still interesting for people around Dortmund/Duesseldorf

moers.de/veranstaltungen/hackd

www.moers.deHackday 2025: Überwinde die Grenzen Deiner Gruppenchats: Kollaborative dezentrale Apps mit JavaScript | Stadt Moers

Zweites Hackweekend 2024 des Code for Niederrhein im JuNo in Moers Repelen

Frauen werden bei der Würdigung durch Denkmale benachteiligt !

Ich hatte eine Lösung versprochen, um das mit Hilfe von OpenStreetMap sichtbar zu machen.

Eine erster Test für den Stadtbezirk 1 in Düsseldorf zeigt wie es funktionieren kann.

Eine Overpass-Turbo-Abfrage zeigt das Ergebnis auf einer Karte:
overpass-turbo.eu/s/1VOQ

#hackday @C4NRN #osm #denkmal #emanzipation #dokumentation #dusseldorf #overpass

overpass-turbo.euoverpass turboA web based data mining tool for OpenStreetMap which runs any kind of Overpass API query and shows the results on an interactive map.

Zweites Hackweekend 2024 des Code for Niederrhein im JuNo in Moers Repelen

Frauen werden bei der Würdigung durch Denkmale noch mehr benachteiligt als bei Straßennamen.

Ich hatte eine Lösung versprochen, um das mit Hilfe von OpenStreetMap sichtbar zu machen.

Ich habe daher (für mich untypisches Verhalten) schon mal die nötigen zusätzlichen Tags an den Denkmalen in OSM dokumentiert.

Seht ihr hier: wiki.openstreetmap.org/wiki/DE

#hackday @C4NRN #osm #denkmal #emanzipation #dokumentation #neuhier

wiki.openstreetmap.orgDE:Tag:historic=memorial - OpenStreetMap Wiki

Zweites Hackweekend 2024 des Code for Niederrhein im JuNo in Moers Repelen
codeforniederrhein.de/2024/11/

Die Emanze in mir wurde gefordert. Die Wikipediaszene hat mich darauf aufmerksam gemacht, dass Frauen bei der Würdigung durch Denkmale noch mehr benachteiligt werden als bei Straßennamen.

Ich wurde gefragt ob das mit Mitteln von OSM sichtbar gemacht werden kann. Ich arbeite an einer Lösung !

#hackday @C4NRN #osm #denkmal #emanzipation #neuhier

Code for NiederrheinAb Dezember einmal im Monat weiterhackenEin Bild von einem Raum, in dem Menschen an ihren Laptops arbeiten. Die Wand im Hintergrund ist voll mit bunten Klebezetteln.