> For the complete documentation index, see [llms.txt](https://community.theiofoundation.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.theiofoundation.org/activities/previous-seasons/season-2025/02-february/tiof-training-bytes-2025-02.md).

# \[#TIOF] Training Bytes 2025-02

TechUp Academy

## About

On the occasion APRICOT 2025 happening in Petaling Jaya, Malaysia, The IO Foundation organizes a training session on the topic of standard developing organizations (SDOs) and to explore the APRICOT 2025 conference and its activities.

This Training Bytes session focuses on practical approaches for developing and implementing technical standards that enhance user safety and privacy.

Participants will

* learn about standards development organizations (SDOs) and how they influence technology
* explore effective strategies for engaging with key SDOs
* identify areas where standards can improve user protection
* learn how to participate and advocate for user-centric practices in technology
* learn which standards are relevant for your industry or occupation

The session aims to equip attendees with the knowledge and tools necessary to contribute to standards that prioritize user rights in the digital landscape in the context of Malaysia and internationally.

\
**Standards Developing Organizations in this activity**

* Asia Pacific Network Information Centre ([APNIC](https://www.apnic.net/))
* Internet Engineering Task Force ([IETF](https://www.ietf.org/))
* International Telecommunication Union ([ITU](https://www.itu.int/en/Pages/default.aspx) | [ITU-T](https://www.itu.int/ITU-T/))
* Internet Corporation for Assigned Names and Numbers ([ICANN](https://www.icann.org/))

## Activity Details

<table><thead><tr><th width="210"></th><th></th></tr></thead><tbody><tr><td>📢 <strong>Title</strong></td><td>Strategies to protect users through standards</td></tr><tr><td><strong>📖 Activity Type</strong></td><td>Training Bytes</td></tr><tr><td>📚 <strong>Series</strong></td><td>Rights By Design</td></tr><tr><td><strong>📅 Date Start</strong></td><td>Thursday 20th February - 09:00</td></tr><tr><td>📅 <strong>Date End</strong></td><td>Thursday 20th February - 16:00</td></tr><tr><td><a href="https://maps.app.goo.gl/rJy6LXpuWgWwKtFn8"><strong>📍</strong></a> <strong>Location</strong></td><td><a href="https://maps.app.goo.gl/rJy6LXpuWgWwKtFn8">Co-labs The Starling Plus</a><br>Petaling Jaya, Malaysia</td></tr><tr><td>🎫 <strong>RSVP</strong></td><td>[By Invitation]</td></tr></tbody></table>

### Agenda

| Time                 | Activity                    | Content                                                                                                    |
| -------------------- | --------------------------- | ---------------------------------------------------------------------------------------------------------- |
| 08:30                | 📋 Registration Opens       |                                                                                                            |
| <p>09:00<br><br></p> | <p>💡 Session 1<br><br></p> | <p><em><strong>Understanding</strong></em><br>Introduction to SDOs and the Rights by Design strategy</p>   |
| 11:00                | 🥐 Break 15 minutes         |                                                                                                            |
| <p>11:15<br></p>     | <p>💡 Session 2<br></p>     | <p><em><strong>Understanding</strong></em><br>Participating in SDOs and overview of their current work</p> |
| 13:00                | 🍱 Break Lunch              |                                                                                                            |
| <p>14:00<br><br></p> | <p>💡 Session 3<br><br></p> | <p><em><strong>Workshop</strong></em><br>How do SDOs affect your work?</p>                                 |
| 15:45                | 💬 Wrap up                  |                                                                                                            |
| 16:00                | 🏁 End                      |                                                                                                            |

## Resources

{% embed url="<https://docs.google.com/presentation/d/1SSlKAEX2VSd4yXmYDj-DB6o9SEyHY_uSyxepgmqT7DY/edit?usp=sharing>" %}
Presentation slides
{% endembed %}

## Media

One of the participants wrote an article about his experience in the event:

{% embed url="<https://kitfucoda.medium.com/hair-dryers-have-standards-why-not-software-a-call-for-rights-by-design-c648058f340f>" %}
An article by Kifu Coda
{% endembed %}

## Cerfiticates

Certificates of attendance are sent directly to the participants.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community.theiofoundation.org/activities/previous-seasons/season-2025/02-february/tiof-training-bytes-2025-02.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.