home.social

#hackday — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #hackday, aggregated by home.social.

fetched live
  1. Delightful first day at IndieWebCamp Nuremberg, great sessions, more than half led by first time IndieWebCamp participants!

    https://events.indieweb.org/2026/06/-indiewebcamp-nuremberg-7EIKg0lqfg93

    Session notes have been archived! Recordings coming soon.

    Want to join us for the IndieWeb Create Day tomorrow?

    https://indieweb.org/Create_Day

    If you’re in Germany, hop on a train and join us in-person.

    Or join us with the Zoom remote participation option!

    Optionally add yourself here:
    * https://indieweb.org/2026/Nuremberg#Remote_Participants

    We’ll publish the Zoom link Sunday morning (CEST). Until then, feel free to join us in the chat for updates: https://chat.indieweb.org/

    #IndieWeb #IndieWebCamp #IWCNUR #IWCNUR2026 #hackathon #hackDay #createDay

  2. Delightful first day at IndieWebCamp Nuremberg, great sessions, more than half led by first time IndieWebCamp participants!

    https://events.indieweb.org/2026/06/-indiewebcamp-nuremberg-7EIKg0lqfg93

    Session notes have been archived! Recordings coming soon.

    Want to join us for the IndieWeb Create Day tomorrow?

    https://indieweb.org/Create_Day

    If you’re in Germany, hop on a train and join us in-person.

    Or join us with the Zoom remote participation option!

    Optionally add yourself here:
    * https://indieweb.org/2026/Nuremberg#Remote_Participants

    We’ll publish the Zoom link Sunday morning (CEST). Until then, feel free to join us in the chat for updates: https://chat.indieweb.org/

    #IndieWeb #IndieWebCamp #IWCNUR #IWCNUR2026 #hackathon #hackDay #createDay

  3. 🚀 We’re excited to announce the very first MobileLinux Hackday in České Budějovice!
    After 7 successful monthly MobileLinux meetups in SUSE's Prague office, our community is heading south to connect, learn, and hack together in South Bohemia.
    Join us on Sunday, May 17, 2026 for a full afternoon (2pm+) and evening of talks, hands-on sessions, and discussions about mobile Linux, embedded platforms, and open source.
    #MobileLinux #Linux #openSUSE #OpenSource #Hackday #Embedded #ČeskéBudějovice

  4. 🚀 We’re excited to announce the very first MobileLinux Hackday in České Budějovice!
    After 7 successful monthly MobileLinux meetups in SUSE's Prague office, our community is heading south to connect, learn, and hack together in South Bohemia.
    Join us on Sunday, May 17, 2026 for a full afternoon (2pm+) and evening of talks, hands-on sessions, and discussions about mobile Linux, embedded platforms, and open source.
    #MobileLinux #Linux #openSUSE #OpenSource #Hackday #Embedded #ČeskéBudějovice

  5. Neben dem DI.DAY im Chaosdorf seid ihr in Moers dieses Wochenende sehr willkommen. Wir sind für unser kleines aber feines Community-Hack-Wochenende wieder von heutigem Freitag ca. 13 Uhr bis Sonntag ca 20 Uhr im JuNo.
    Samstag Vormittag ist Thementag Plotter mit Jugendlichen. @JhLmoers

    Freiwillige Anmeldung, Infos und kollaborative Projekt-Notizen findet ihr im Pad:
    pad.cfn.rocks/p/community-hack

    #hackday #niederrhein #moers

  6. Are you going to IETF Montreal in November? Me too! Currently working out my flights and leaning towards the second half of the week through the weekend. Would love to get together with some other #ATProtocol developers to talk tech, network, and hang out. Message me! #Montreal #IETF #HackDay

    IETF 124 Montreal

  7. 📢 Hackday location confirmed!
    The Symfony Hackday will be held at:
    📍 Volkshotel – Wibautstraat 150, 1091 GR Amsterdam
    Saturday, Nov 29 | 🕘 09:30 – 15:00 CET
    💻 Bring your laptop & your ideas!
    🙌 A big thank you to Baksla.sh for sponsoring both our Hackday and the official SymfonyCon t.shirt!
    #SymfonyCon #Hackday #Symfony #PHP

  8. 📢 Hackday location confirmed!
    The Symfony Hackday will be held at:
    📍 Volkshotel – Wibautstraat 150, 1091 GR Amsterdam
    Saturday, Nov 29 | 🕘 09:30 – 15:00 CET
    💻 Bring your laptop & your ideas!
    🙌 A big thank you to Baksla.sh for sponsoring both our Hackday and the official SymfonyCon t.shirt!
    #SymfonyCon #Hackday #Symfony #PHP

  9. Want to spend a day hacking around with bike/walking/wheeling stuff (data? mapping? code? electronics? all of the above? who knows, we'll work it out together) with me at @DoESLiverpool ?

    Come along to the Active Travel Hackday!

    events.doesliverpool.com/event

    #ActiveTravel #hackday #weeknotes #Liverpool

  10. Want to spend a day hacking around with bike/walking/wheeling stuff (data? mapping? code? electronics? all of the above? who knows, we'll work it out together) with me at @DoESLiverpool ?

    Come along to the Active Travel Hackday!

    events.doesliverpool.com/event

    #ActiveTravel #hackday #weeknotes #Liverpool

  11. 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).

  12. 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).

  13. "Moers bleibt bunt". Danke für das klare Statement. Und Danke an die Orga den tollen Hackday Moers, auch wenn ich leider nur am Samstag teilnehmen konnte.

    #moers #diversity #oddmo25 #hackday

  14. Entgegen dem Hype um KI, unter der meistens generative KI und vor allem LLM gemeint sind, erklärt @stk beim Hackday Niederrhein differenzierter, wofür welche KI geeignet sein könnte, und wofür nicht. Danke.
    #oddmo25
    #ki
    #hackday #niederrhein
    @C4NRN

  15. Entgegen dem Hype um KI, unter der meistens generative KI und vor allem LLM gemeint sind, erklärt @stk beim Hackday Niederrhein differenzierter, wofür welche KI geeignet sein könnte, und wofür nicht. Danke.
    #oddmo25
    #ki
    #hackday #niederrhein
    @C4NRN

  16. Fulminanter Vortrag von Prof. Von Lucke (Zeppelin Uni Friedrichshafen) über Chancen & Risiken generativer #KI in Verwaltungen. Praktische Übung zur Verkehrssituation in MOers (Anfragen, Lösungsvorschläge, Verwaltungsvorlagen). #Hackday

  17. LLMoin ist ein Large Language Model (#KI) des Hamburger Senats, das Datenschutz konform in der Verwaltung genutzt wird. #Hackday #MOers

  18. Der Jubiläum #Hackday (10) hat in MOers mit dem Vortrag von Ann Cathrin Riedel (NExt) begonnen. Schwerpunkt des Tages: KI in Verwaltungen.

  19. Morgen werde ich in #Moers beim #Hackday berichten, was wir in #SchleswigHolstein in Sachen #OpenData machen.
    Und über #LinkedOpenData wollen wir nachmittags auch noch sprechen.

  20. Morgen werde ich in #Moers beim #Hackday berichten, was wir in #SchleswigHolstein in Sachen #OpenData machen.
    Und über #LinkedOpenData wollen wir nachmittags auch noch sprechen.

  21. 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

  22. Beim @evenly_io #hackday zusammen mit @map mal wieder ein Hardware Projekt gehackt. Drei IKEA OBEGRÄNSAD (ikea.com/de/de/p/obegraensad-w) mit einem ESP32 ausgestattet. Jetzt können sie custom Anzeigen die man via Website steuern kann. Alles nach diesem GitHub Projekt: github.com/ph1p/ikea-led-obegr Spaß hat’s gemacht 😊

  23. We have our OEF #Hackday on Friday Oct 6. I'm going to work on connecting our GitHub activity streams (lowercase) to Mastodon. I'm wondering if there are already tools for this on the fediverse?

  24. Learn programming in a fun way with Music Blocks, introduce yourself to the command line and basic hacking at one of our hacking stations, and experience GNU Boot being flashed onto an X200 laptop at our #Hackday for families, students, and anyone interested in hacking: u.fsf.org/hackday #GNU40 #MusicBlocks @musicblocks/ #GNUBoot

  25. Meanwhile, at the FSF headquarters in Boston, MA, things are getting very real in preparation for our #GNU40 event. We've got festive #GNU balloons and a helium tank, the face painter is practicing her GNU-painting skills, we've posted fliers around town, and, as always, we've got some original hand-drawn GNU illustrations displayed in the office. More info: u.fsf.org/hackday #GNUart #FreeSoftware #Hackday #HappyHacking

  26. The #GNU System is turning forty. Come and celebrate with us! The GNU Project is inviting you to a #Hackday on Sunday, October 1, at the FSF's office: u.fsf.org/hackday #GNU40

  27. This week's the week -- it's #GNU40! Tomorrow, September 27, is the GNU Hacker's Meeting in Biel, Switzerland, and this Sunday, October 1, is Hackday in Boston, MA. Read more: u.fsf.org/40k #FreeSoftware #GNU #GNUforty #SoftwareLibre #Hackday #HappyHacking

  28. Forty years ago, it started with the four freedoms; today, the GNU Project, GPL and other GNU licenses, and copyleft is still going strong; on September 27 and October 1, we're celebrating those hard-won freedoms in Biel (Switzerland) and Boston, MA (USA). Read more about our hacker history and these upcoming events: u.fsf.org/40k #GNU40 #GPL #FreeSoftware #Copyleft #HackDay #Hackers #HappyHacking #FourFreedoms

  29. Sign-ups are coming in. If you're in reach of Prague in July, please join us for a day of tech fueled trans joy.

    Claim your spot at ep2023.europython.eu/trans_cod

    And please share with anyone who might be interested!

    #trans_code #EuroPython #EuroPython2023 #hackday

  30. Please help us get the word out about our Trans*Code hackday event at #EuroPython in Prague, July 18!

    For more info and to register interest visit
    ep2023.europython.eu/trans_cod

    No, you don't need to code in #Python (or at all) to join us for a day of hacking, brainstorming, and community.

    The event is free to everyone, and applications for financial aid for the conference as a whole are open until May 21.

    Please forward to anyone who might be interested! :flag_transgender: 🙏

    #trans_code #trans #hackday #EuroPython2023

  31. 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.

    #alexa #developer #hackday #nhshd #python

  32. 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.

    #alexa #developer #hackday #nhshd #python

  33. 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.

    #hackday #homeless #wdif

  34. 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.

    #hackday #homeless #wdif