Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found
Select Git revision
  • master
1 result

Target

Select target project
  • card10/logix
  • annejan/logix
  • kgz/logix
  • pink/logix
  • mot/logix
  • 9R/logix
  • melle/logix
  • jspricke/logix
  • sjn/logix
  • marble/logix
  • audionerd/logix
  • astro/logix
  • genotest/logix
  • _luc/logix
  • C-Tim/logix
  • Superwallah/logix
  • nitram/logix
  • Pixtxa/logix
  • royrobotiks/logix
  • deusfigendi/logix
  • arist/logix
  • LordBonzi/logix
  • Stormwind/logix
  • dag/logix
24 results
Select Git revision
  • master
  • patch-1
  • patch-2
  • patch-3
  • patch-4
5 results
Show changes
Show whitespace changes
Inline Side-by-side
Showing
with 617 additions and 202 deletions
en/firmware/memorymap.md deleted 100644 → 0
View file @ 88a0d32f
---
title: Memory Map
---
## Obsolete:
Please tend to https://firmware.card10.badge.events.ccc.de/memorymap.html
\ No newline at end of file
en/firmware/pycardium_modules.md deleted 100644 → 0
View file @ 88a0d32f
---
title: Pycardium Modules Development
---
## Obsolete
Please tend to https://firmware.card10.badge.events.ccc.de/pycardium-guide.html
en/firmwareupdate.md deleted 100644 → 0
View file @ 88a0d32f
---
title: Current Release
---
# Currently: Eggppppplant (day 3 - 00:23)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.5-Eggppppplant.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v15-2019-08-23-0018-eggppppplant)
# Update the firmware release on your card10
* download the current firmware `.zip` file to your computer
* extract it
* put your card10 into [USB storage mode](/en/gettingstarted#usb-storage)
* copy over the files you just extracted directly into the main folder. Note: on macOS devices it is recommended to use the terminal, e.g. for the broccoli release: `cp -r ~/Downloads/card10-v1.2-broccoli/* /Volumes/CARD10/`
* eject your device (if you're doing this in the command line: don't forget the `sync` on linux)
* switch your card10 off and on again
# Previous Releases
# DaikonRadish (day 2 - 20:00)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.4-DaikonRadish.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v14-2019-08-22-1943-daikonradish)
# CCCauliflower (day 2 - 00:30)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.3-cccauliflower.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v13-2019-08-22-0012-cccauliflower)
## Broccoli (day 1 - 19:00)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.2-broccoli.zip
## Asparagus
As of Day 1, 18:00
Asparagus is the firmware that is loaded on the card10s handed out on day 1 from 18:00
There are currently no previous releases
en/gettingstarted.md deleted 100644 → 0
View file @ 88a0d32f
---
title: Getting Started
---
You just received your card10 - what now?
## card10 assembly
[Here](/en/assembleyourcard10)'s a step by step guide with pictures for assembling your card10
## card10 navigation
There are four buttons on the card10 _harmonic_ board: On the top left, just above the USB-C connector is the POWER button. Below is the LEFT button. The buttons on the right side are closer together. On this side, the top button is the SELECT button, the one below it is the RIGHT button.
<img class="center" alt="Drawing of card10 with button names" src="/media/card10buttons.svg" width="220" height="auto" align="center">
### switching your card10 on and off
To switch on card10, briefly press the POWER button. To switch it off again, press and hold down the power button for several seconds (usually this is around three seconds, however for some apps it can take over ten seconds).
### starting apps
When your card10 is switched on, a short press of the POWER button
brings you to the app menu. You can scroll down with the RIGHT button,
and up with the LEFT button. The SELECT button starts the selected app.
The POWER button starts the app called 'main.py', which is also the app
that will automatically start when you turn on your card10.
### choosing your personal state
Card10 comes with an app to set your [personal state](/ps). As with the nickname, enter the menu
by pressing the POWER button briefly. This time, select the `personal_state.py` app with the POWER button,
and navigate to your state with the LEFT and RIGHT buttons. Unlike the other apps, the state of the personal
state LED will remain blinking and glowing as you set it in the app.
### USB storage
Your card10 can function similar to a USB stick, if you start it in _USB storage mode_. You can use this mode to upload _configuration files_ and _micropython scripts_. To enter _USB storage mode_, first switch off your card10 with a long press of the POWER button. Next, hold down the RIGHT button and the POWER button, until your display shows the text "USB activated. Ready.".
Now when you connect the card10 to your laptop via USB, it will show up as a storage device.
<div class="p-notification--caution">
<p class="p-notification__response">
<span class="p-notification__status">Important:</span>Don't forget to eject/unmount the card10 before unplugging it or pressing any buttons on the card10
</p>
</div>
The USB storage mode is exited by briefly pressing the POWER button.
### setting your nickname
To set your nickname, create a file called `nickname.txt` on your laptop.
Start your card10 in USB storage mode, then copy `nickname.txt` onto the card10. Eject the USB device.
Then briefly press the POWER button to exit the storage mode, and then a second time, to enter the menu.
You can scroll up and down using the LEFT and RIGHT buttons.
Now look for an app called 'nickname.py', select it by pressing the SELECT button.
If you have successfully uploaded a `nickname.txt` file, your nickname will now show up on the display.
You can also upload a `nickname.json` file instead, to get some more options.
Have a look at the [hatchery](https://badge.team/projects/card10_nickname) for more options of the app.
### adding apps
The [hatchery](https://badge.team/) also has more apps written by other card10 users. To get these apps on your card10,
you can either use the [app](/app), or you can upload them via USB storage: Download and extract the `tar.gz` files (or download all files individually). Put your card10 in [usb storage mode](/en/gettingstarted#usb-storage-mode), to add the files.
All apps are placed in the `apps` folder. In the `apps` folder, all apps have their own folder, named after the app name (e.g. `apps/app_name`). To add a new app,
create a folder with the name of the app, and then place all files for the app inside this folder.
### activate BLE
Initially, BLE is disabled for privacy reasons. If you want to use it, you have to activate it first.
* Via the menu: Select the ble.py from the menu and press the SELECT button to enable BLE. The board will restart with activated BLE. Deactivation can be done via the same app.
* Manually: Start the card10 in _USB storage mode_ and add a file `ble.txt` with (exactly) the content `active=true` then reset the board.
## Next
Now it is time to start playing with the card10, writing your own micropython code!
Continue in the [first interhacktions](/en/firstinterhacktions) section.
en/prototype_distribution.md deleted 100644 → 0
View file @ 88a0d32f
---
title: Distribution of Prototypes
---
**Hello fellow researcher,**
you want to become part of the card10 research team and help us find out how it will have improved everyone's experience at Chaos Communication Camp 2019?
Here's what you have to know:
* We have around 20 prototypes which we are trying to share with as many interested card10logists as possible. And there are many people interested in working with it.
* There's documentation in our [wiki](https://card10.badge.events.ccc.de/)
* We're trying to find out how the badge will have interacted (?) and used BLE to interface with other installations at camp the camp surroundings
* Cities with hackspaces can get a prototype if there's a volunteer for being an ambassador who takes care of the prototype (trying to avoid too much idle time)
## Cities that already have ambassadors
| City | Hackerspace | Ambassador |
|-----------|----------------------------------------------|-------------|
| Amsterdam | [badge.team](https://badge.team) | the_JinX |
| Bamberg | [backspace](https://hackerspace-bamberg.de/) | schinken |
| Berlin | [xhain](https://x-hain.de) | miriamino |
| Bremen | [ccc-hb](https://ccchb.de) | lilafisch |
| Dresden | [c3d2](https://c3d2.de/space.html) | Astro |
| Karlsruhe | [Entropia](https://entropia.de/) | uberardy |
| Mannheim | [RaumZeitLabor](https://raumzeitlabor.de/) | cheatha |
| Munich | [µc3](https://muc.ccc.de) | schneider__ |
Most ambassadors can be reached via the #card10badge Freenode/Matrix channel.
### Here's what you can do:
* Think about how you want to contribute/what you want to do with the prototype
* Join our [Matrix](https://en.wikipedia.org/wiki/Matrix_(protocol)):( [`#card10badge:asra.gr`](https://matrix.to/#/#card10badge:asra.gr))/[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) ( [`freenode.net#card10badge`](ircs://chat.freenode.net:6697/card10badge))
channel and tell us what you want to do
* Talk to your city's ambassador
* Become an ambassador yourself
* We'll try to find a timeslot for you to work with the prototype
* We send it to you and after the time we agreed upon you send it back to us/the next person
### How to be a great card10logy department ambassador:
* Get more people involved to help with 'ambassadoring' ;P
* Invite others to chat about the card10
* Organise meetups to play with card10
* Invite related groups (wagenburg, fab labs, ...)
* Contact and encourage people who might have great ideas but are not aware of the project/too shy to ask
* Share your research in the card10logix wiki, matrix/irc and @card10badge
events/_index.md 0 → 100644
View file @ cdb3584e
---
title: Events
weight: 50
---
<!-- Please keep ongoing and current events in sync with _index.md -->
- Upcoming:
- virtual card10 workout: 2021-09-19 at https://meet.ffmuc.net/card10-workout
<!-- past events, please remove any events you move here from _index.md to keep the home page clean -->
- Previous
- DiVOC R2R: 2021-04-04 Bluetooth LE in MicroPython (auf der card10 badge) https://meet.ffmuc.net/card10-mp-ble
- card10 [workout in Berlin](/events/workouts/berlin-2019-11-09): xHain, Sat-Sun, November 9th to 10th, 2019
- **card10 reworking/soldering/firmware/etc.**: card10 village (R8); for firmware work, please bring your laptop with a clone of the firmware git and the [toolchain](https://firmware.card10.badge.events.ccc.de/how-to-build.html)
- card10 Soldering Session in Berlin: xHain Wed-Thurs 14&15. August starting at 10 am
- card10 Soldering Session in Berlin: xHain Sat-Sun 10.-11. August starting at 10 am
- card10 meetup in Berlin: xHain 06.08. ~~19:00~~ => 20:00
- card10 meetup in Berlin: xHain 05.06. 20:00
- card10 meetup in Berlin: afra 21.06. 19:00
- card10 meetup in Berlin: xHain 14.06. 19:00
- card10 at the [GPN19](https://entropia.de/GPN19:There_will_have_been_a_camp_badge:_We%27re_reconstructing_future_technology_and_you_can_help_us_with_this_mission)
- CCCamp2019 Badge Workshop at #eh19: [Description](https://conference.c3w.at/eh19/talk/VHFMJ7/), 2019-04-21, 14:30–15:30
- CCCamp 2019 Badge at #eh19 (easterhegg2019): [Description](https://conference.c3w.at/eh19/talk/DA7KTT/), [Recording](https://media.ccc.de/search/?q=CCCamp+Badge+Talk)
- **card10 [talk](https://fahrplan.events.ccc.de/camp/2019/Fahrplan/events/10365.html)**: Curie Wed 21.08. 12:00
- **card10 firmware workshop**: card10 village (R8), Sun 18.08. 16:00
- card10 [workout in Berlin](/events/workouts/berlin-2019-10-03): xHain, Thurs-Sun, October 3rd to 6th, 2019
events/awards.md 0 → 100644
View file @ cdb3584e
---
title: Awards
---
Idea: From time to time hold small award ceremonies to keep people motivated to contribute
to the card10 project
## 36C3
We will host a small awards ceremony at 36C3.
### Categories
- Best documented project
- Best use of a sensor (ECG, Accelerometer, etc...)
- Best LED application (e.g. POV)
- Best accessibility contribution
- Best interaction with 36C3
### Submitting a contribution
You submit a contribution (be it an app, project, documentation, etc..) by entering it in the list of contributions at the end of this section.
You can also reach out to us via twitter, mastodon, matrix and IRC. We will add your contribution for you if needed.
### Date and Time
Unless otherwise noted the ceremony will take place Day 3, 20:00 at the card10 assembly.
Entries have to be made until Day 3, 18:00.
### Judging
Judging will be done by original contributors to the card10 project. For the accessibility category we will approach relevant teams at 36C3.
### Prizes
We are still collecting, but at least there will be a few r0kets and rad1os available.
### Contributions
- Pixtxa
- [36C3 Clock](https://badge.team/projects/36c3_clock)
- [Cyberband](https://badge.team/projects/cyberband)
- [Monster++](https://badge.team/projects/monster)
- [Timer](https://badge.team/projects/timer)
- Royrobotiks
- [Control Center](https://badge.team/projects/control_center)
- [Tiny Typer](https://badge.team/projects/tiny_typer)
- [Magnetometer](https://badge.team/projects/magnetometer)
- [Micromarble](https://badge.team/projects/micromarble)
- Your contribution
events/card10_at_rc3.md 0 → 100644
View file @ cdb3584e
---
title: card10 at rC3
---
## Brainstorming
Instead of the regular 37C3, we will have the first ever remote congress end of this year, which is dubbed "rC3"
How can card10 interact with a remote and distributed chaos event?
How can card10 connect to other card10s anywhere on the globe?
What services could it provide, what services could it make use of?
### PTT or mute/unmute input device
Connect to the local PC via bluetooth LE, display via RGB LEDs the (un)mute and (un)deafen status of
- the OS communications device
- the application that uses the communications device
- there might be multiple and changing applications, especially for speakers, heralds, VOC and other angels (e.g. mumble, BBB, OBS, discord, teamspeak etc...)
- different OS's will handle audio differently. Audio routing is a pain. Reliable indication of the current state would improve the situation a lot
### virtual applause
- detect if the wearer is clapping their hands via one of the accelerometers
- push this info to a central server
- somehow show in an overlay in the live stream or via an indicator next to the streaming window how many card10 wearers are clapping in real time
### Tools for speakers, heralds, VOC angels
Timing and handing over who is speaking is challenging to coordinate due to the latency of video conference tools. can card10 help here by e.g.
Notifications who is
- ready to talk
- waiting to talk
- wanting to ask a question from the audience and waiting for the speaker to finish their sentence
- having a problem and needs help from the team
- presentation timer
Providing real time feedback from the audience to the speaker
- showing on the LED bargraph how many people are applauding virtually (see above)
- pulsing the vibration alarm with increasing intensity the more people are clapping
Pushing info about the current state, like the typical online status or the state app at camp (yes, that is potentially sensitive information that the wearer should be able to have control over who is allowed to see it, like with basically any messenging app)
- online and available
- online but afk (taking a break, eating,...)
- not online (connection problems, blackout, sleeping,...)
### Pager
display short texts on the LCD that can be sent via
- the compantion app
- via the POC? Possible to subscribe the compantion app to the EVPN, registering an extension that can receive text messages or can be paged?
- IRC, matrix, twitter, rocket chat, whatever
- display the sender and if they want to be called via DECT/SIP asap/soonish/when convenient/...
### Fahrplan interaction
#### Show on the display which segments are up next
probably best if requested by presisng a button pull the info required via an API from the fahrplan app that needs to be installed on the same phone as the card10 companion app
#### Notification when a favourite segment is about to start
The fahrplan app allows flagging talks as favourites.
Pull those flags and notify the wearer by a configurable alarm (e.g. pulse the vibration alarm, flash LEDs, show the name of the upcoming talk on the display for a few seconds or until the alarm is dismissed by pressing a button)
#### Notification for self organized sessions
same for the database that contains the SOS's (afaik that calendar has been in the congress wiki until now)
events/rc3.md 0 → 100644
View file @ cdb3584e
---
title: card10 rC3 Assembly
---
We will have an assembly in the cellar of the muccc at rC3:
## Location and Time
- Location: [rc3 cellar](https://test.visit.at.wa-test.rc3.cccv.de/_/global/raw.githubusercontent.com/muccc/rc3test/master/main.json) Attention: Link subject to change
- Times: Day 1 - Day 4
- Capacity: virtual
Meetup: Day 4 (2020-12-30) 14:00 to 16:00 CET
events/workouts/_index.md 0 → 100644
View file @ cdb3584e
---
title: Workouts
---
.
events/workouts/berlin-2019-10-03.md 0 → 100644
View file @ cdb3584e
---
title: Workout Berlin 2019-10-03
---
The first card10 workout will happen at xHain in Berlin from October 3rd to 6th, 2019.
## Location and Times
- Location: [xHain](https://x-hain.de/en/page/about/): Grünberger Str. 16, 10243 Berlin
- Times: 2019-10-03 to 2019-10-06, all day in general, details to follow
- Capacity: Around 10-20 people
## People
- rahix
- lilafisch
- peter
- schneider
- hds
- paulaner
- YOU?
## Activities
### Firmware
We will most likely work on integating more Merge Requests into the firmware, creating a new release.
### Hardware
If you have issues with your hardware swing by and we can see if there is a quick fix. We will have spare parts!
### Software
We plan to experiment with some more phones to improve BLE support. If you want to work on the wiki feel free too.
Lots of people wo know around ;)
### Wearware
We still have plenty of conductive thread and a lot of ideas. Do you have some too?
## Events
We can make us of xHain during the times as mentioned above. If you want to allocate some time
for specific workshops or similar, mention it here:
Title | Person | Start Time / Day | Duration
------|--------|------------------|---------
ECG logging documentation /experiments | schneider | Thursday 13:00 | 4 hours
@Berlindroid-Meetup | | Thursday 19:00 | 5 hours
card10 repair cafe | schneider | Friday 14:00 | 2 hours
card10 team lunch? | all | Friday 15:30 | 1.5 hours
generative 3D printed card10 cover design | Niklas Roy | Friday 17:30 | 1.5 hours
MicroPython introduction | lilafisch | Friday 20:00 | 1.5 hours
app discovery | lilafisch | Saturday 11:00 | 1.5 hours
card10 repair cafe | schneider | Saturday 14:00 | 2 hours
card10 documentation | lilafisch | Saturday 14:00 | 2 hours
Sewing wearables | lilafisch | Saturday 16:00 | 2.5 hours
card10 @ 36C3 #1 (dinner) | schneider | Saturday 18:30 | 1.5 hours
BME680 hacking | schneider | Saturday 20:00 | 4 hours
card10 repair cafe | schneider | Sunday 14:00 | 2 hours
card10 @ 36C3 #2 (also: next workout)| schneider | Sunday 16:30 | 1.5 hour
### generative 3D printed card10 cover design
Learn more about the generative 3D printed card10 covers (https://github.com/royrobotiks/card10_cover),
get inspired for you own generative designs, and learn skills for implementing them with openSCAD.
### MicroPython introduction
If you haven't dared trying to write your own apps for your card10, now is your chance
to learn how to do it! Programming your card10 using MicroPython is easy to learn, and all
you need is your laptop (preferably linux), a usb-C cable, and of course your card10.
### App discovery
There are hundreds of card10 apps in the hatchery. Let's start the day by exchanging our
favourite discoveries, and trying some new ones.
### card10 @ 36C3
Camp is over, but congress is already coming up! Everyone is welcome to join collecting ideas and planning
card10 action for congress.
### Repair cafe
Open hardware means you can fix it! We're bringing some spare parts, and
plenty of assistance is around, so together we can restore the broken bits of some card10s.
Obviously, you should bring your card10 if you want to fix it ;), everything else will be around at the event.
### Documentation
Let's get together and make an effort to share what we know, or ask some new questions that
need answering and documenting.
Bring questions :) Also, a laptop will be very useful for writing documentation.
### Sewing wearables
Extend your card10 on the wristband, with some blinking LEDs. We'll have needles, thread, and LEDs.
You should definitely bring your card10, you can also bring your own LEDs, or
if you have any wearable sensors you'd like to attach we can try to figure out how to
connect them to your card10 together.
## Accomodation
xHain is not a place to sleep, so please make sure you have some accomodation. Get in touch with us on IRC/Matrix if you don't know.
events/workouts/berlin-2019-11-09.md 0 → 100644
View file @ cdb3584e
---
title: Workout Berlin 2019-11-09
---
The second card10 workout will happen at xHain in Berlin on the weekend from November 9th - 10th, 2019.
## Location and Times
- Location: [xHain](https://x-hain.de/en/page/about/): Grünberger Str. 16, 10243 Berlin
- Times: 2019-11-09 to 2019-11-10, all day in general, details to follow
- Capacity: Around 10-20 people
## People
- andreas
- rahix
- schneider
- spacecarrot
- YOU?
## Activities
### Firmware
We will work on integating more Merge Requests into the firmware, and hopefully create a new release.
### Hardware & Repair Cafe
If you have issues with your hardware swing by and we can see if we can fix it. We will have spare parts!
### Software
We plan to experiment with some more phones to improve BLE support. If you want to work on the wiki
feel free too. Lots of people who know around ;)
### Wearware
We still have plenty of conductive thread and a lot of ideas. Do you have some too?
## Events
We can make us of xHain during the times as mentioned above. If you want to allocate some time
for specific workshops or similar, mention it here:
Title | Person | Start Time / Day | Duration
------|--------|------------------|---------
Be the first! | | |
### MicroPython introduction
If you haven't dared trying to write your own apps for your card10, now is your chance to learn how
to do it! Programming your card10 using MicroPython is easy to learn, and all you need is your
laptop (preferably Linux, but Windows and MacOS work as well), a USB-C cable, and of course your
card10.
### App discovery
There are hundreds of card10 apps in the hatchery. Let's start the day by exchanging our favourite
discoveries, and trying some new ones.
### Repair cafe
Open hardware means you can fix it! We are bringing some spare parts and plenty of assistance is
around, so together we can restore the broken bits of some card10s.
Obviously, you should bring your card10 if you want to fix it ;), everything else will be around at
the event.
## Accomodation
xHain is not a place to sleep, so please make sure you have some accomodation. Get in touch with us
on IRC/Matrix if you don't know.
en/workshops/_index.md → events/workshops.md
View file @ cdb3584e
--- ---
title: Workshops title: Workshops
--- ---
### Organising a workshop
* from Day3, you can hold workshop at card0 village between 12:00 and 23:00, in 1 hr slots, starting at the full hour, check which slots are already used in the list below
* for other days/times please coordinate with lilafisch
* the card10 area is suitable for small scale (10 to 20 people), hands-on workshops
* feel free to hold card10 workshops at other locations (e.g. Johnson) as well, but it is up to you to organise the room
* for help, ask lilafisch
### Participating ### Participating
* there is no sign-up, just turn up * There is no sign-up, just turn up
* check the worksop descriptions to see if you should bring anything/have anything pre-installed on your laptop * Check the worksop descriptions to see if you should bring anything/have anything pre-installed on your laptop
* you might also find more card10 related sessions on the cccamp19 [self organised sessions page](https://events.ccc.de/camp/2019/wiki/Static:Self-organized_Sessions)
## Past Workshops
### MicroPython on the card10 for complete beginners
* Time: 36C3 Day 3, 12:00
* Duration: 1-2 hours
* Location: card10 assembly
* Things to bring: a laptop and a card10
* No knowledge of Python needed
### Using the pressure sensor and accelerometer with MicroPython
* Time: 36C3 Day 3, 14:30
* Duration: 1.5 hours
* Location: card10 assembly
* Things to bring: a laptop and a card10
* Ideally you should already know how to program in MicroPython
### Seweable electronics with the card10 badge
* Time: 36C3 Day 3, 18:00
* Duration: 1-2 hours
* Location: card10 assembly
* Things to bring: a laptop and a card10
* No knowledge of Python needed
### MicroPython on the card10 for complete beginners
* Time: 36C3 Day 2, 17:00
* Duration: 1-2 hours
* Location: card10 assembly
* Things to bring: a laptop and a card10
* No knowledge of Python needed
### Micropython on card10 for complete beginners (DE + EN)
* Time: Day 4, 15:00
* Location: card10 area
* bring a laptop and a usb-c cable
* and your card10
* no knowledge of python needed
### E-textile card10 workshop (DE + EN)
* Time: Day 4, 18:30 - 20:30
* Location: card10 area
* bring: card10, laptop, USB-C cable
* (EN) also useful: sewing needles, thread, through hole LEDs, needle nose pliers, snap fasteners
* (DE) auch nuetzlich: naehnadeln, faden, 3mm oder 5mm LEDs (zum durchstecken), feine zangen zum draht biegen, druckknoepfe
### Pulsoxymetrie & ECG fuer Hacker (DE)
* Time: Day 4, 21:00
* Location: card10 area
* ein Vortrag vom CERT
### ECG kit assembly
* Time: Day 4, 20:30
* Location: Hardware Hacking Area
* ECG kits available at workshop and card10 assembly
### ECG kit assembly
* Time: Day 4, 21:30
* Location: Hardware Hacking Area
* ECG kits available at workshop and card10 assembly
## Workshops
please keep chronological order
### Environmental and IMU sensor workshop ### Environmental and IMU sensor workshop
> ~~Time: Day 2, 19:00~~ > ~~Time: Day 2, 19:00~~
......
en/faq.md → faq/_index.md
View file @ cdb3584e
--- ---
title: FAQ title: FAQ
--- ---
## What should I bring to CCCamp 2019 so I can enjoy card10?
*I have noticed that the card10 needs some maintenance; most people carrying a card10 have brought their own tools for maintaining their card10, making it more individual, or adding functionality. In some places, maintenance stations are available, where card10's can be recharged, and tools and knowledge is shared*
According to current research, it is recommended to carry the following: {{% notice info %}}
Deutsche Version: [FAQ](faq.de)
{{% /notice %}}
* A USB-C cable for plugging your card10 into your laptop USB port is key for charging and programming; USB-A on your laptop side is fine. ## How can I contribute?
Generally, there is a wide range of contributions that can be made to the firmware, the iOS and Android apps, the various methods of BLE communication, the user interface, the documentation, by reviewing existing work, and of course by creating your own [interhacktions](/interhacktions)!
Optional things that will come in handy: If you don't know where to get started you can also have a look at some of the ideas for contributions we outlined [here](https://git.card10.badge.events.ccc.de/card10/logix/issues). If you have questions on the issue, please don't hesitate to comment or get in touch to the creator of the issue through our [Matrix](https://en.wikipedia.org/wiki/Matrix_(protocol)):( [`#freenode_#card10badge:matrix.org`](https://matrix.to/#/#freenode_#card10badge:matrix.org))/[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) ( [`freenode.net#card10badge`](ircs://chat.freenode.net:6697/card10badge)) channel.
* A Torx T6 screwdriver for assembling card10
* A needle for sewing to the card10 wristband
* An android phone or iphone capable of communicating via [Bluetooth Low Energy](/en/ble) (BLE)
You can also be a great help by adding documentation to the [card10logix wiki](https://card10.badge.events.ccc.de). If you notice some information is missing, but you don't know the information that needs adding, you can also make us aware by [adding an issue](https://git.card10.badge.events.ccc.de/card10/logix/issues). Please make sure to describe in detail what information is missing.
## What can I contribute?
Generally, there is a wide range of contributions that can be made to the firmware, the IOs and Android apps, the various methods of BLE communication, the user interface, the documentation, by reviewing existing work, and of course by creating your own [interhacktions](/en/interhacktions)!
If you don't know where to get started you can also have a look at some of the ideas for contributions we outlined [here](https://git.card10.badge.events.ccc.de/card10/logix/issues). If you have questions on the issue, please don't hesitate to comment or get in touch to the creator of the issue through our [Matrix](https://en.wikipedia.org/wiki/Matrix_(protocol)):( [`#card10badge:asra.gr`](https://matrix.to/#/#card10badge:asra.gr))/[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) ( [`freenode.net#card10badge`](ircs://chat.freenode.net:6697/card10badge)) channel.
You can also be a great help by adding documentation to the [card10logix wiki](https:://card10.badge.events.ccc.de). If you notice some information is missing, but you don't know the information that needs adding, you can also make us aware by [adding an issue](https://git.card10.badge.events.ccc.de/card10/logix/issues). Please make sure to describe in detail what information is missing.
## How does the so-called wiki work? ## How does the so-called wiki work?
To keep things easier to maintain (the r0ket wiki has been going for 8 years now!), we decided on a git/markdown based wiki for this year. To keep things easier to maintain (the r0ket wiki has been going for 8 years now!), we decided on a git/markdown based wiki for this year.
...@@ -37,15 +29,17 @@ Yes, a comfortable neoprene wristband comes with every card10. If you want somet ...@@ -37,15 +29,17 @@ Yes, a comfortable neoprene wristband comes with every card10. If you want somet
We recommend reinforcing the velcro hook side attachment by adding a seam along the sides of the velcro hook side piece. We recommend reinforcing the velcro hook side attachment by adding a seam along the sides of the velcro hook side piece.
## Why should I consider keeping the protective foil on the display? ## Why should I consider keeping the protective foil on the display?
The display has a polarizing filter on. With the protective foil stuck on top, this filter is disabled. With some sunglasses this has the unfortionate effect that the card10 is difficult to read on your wrist. The display has a polarizing filter. With some sunglasses this has the unfortionate effect that the card10 is difficult to read on your wrist. If you keep the protective foil stuck on top, the filter is effectively disabled.
## What can I do if the filesystem of my badge is read-only? ## What can I do if the filesystem of my badge is read-only?
tl;dr: `fsck` tl;dr: `fsck`
One possible reason for a read-only filesystem is a set "dirty-bit". The [maintenance and repair](/maintenance) section of card10logix includes information about [filsystem repairs](/maintenance/filesystem).
To change this the linux tool fsck can be used.
First the badge needs to be ejected safely, then it needs to be restartet and put back into "USB storage" mode. ## Help! My Display is not working / it cracked
The device should not be mounted. Now `lsblk` can help with finding the correct blockdevice. During camp we discovered that the badge display is one of the parts that easily gets damaged.
Then you can check the filesystem with `fsck /dev/sdX` (replace `sdX` with the correct device). If you get a crack due to a mechanical crash or similar incident you have to replace your display.
If neccessary the tool will ask if the "dirty bit" should be removed, this needs to be answered with yes.
After this, the problem should be solved. The [maintenance and repair](/maintenance) section of card10logix includes a [guide for display replacement](/maintenance/display).
\ No newline at end of file
de/faq.md → faq/faq.de.md
View file @ cdb3584e
--- ---
title: FAQ title: FAQ
hidden: true
--- ---
## Was soll ich zum CCCamp 2019 mitbringen, damit ich Spaß mit card10 haben kann? ## Was soll ich zum CCCamp 2019 mitbringen, damit ich Spaß mit card10 haben kann?
*Ich habe bemerkt, dass das card10 ein bisschen Wartung braucht; die meisten Leute, die ein card10 mit sich tragen, haben ihre eigenen Werkzeuge zur Wartung des card10 mitgebracht, um es individueller zu gestalten oder Funktionalität hinzu zu fügen. An manchen Orten, sind Wartungsstationen verfügbar, wo card10s aufgeladen werden können und Werkzeuge und Wissen geteilt werden.* *Ich habe bemerkt, dass das card10 ein bisschen Wartung braucht; die meisten Leute, die ein card10 mit sich tragen, haben ihre eigenen Werkzeuge zur Wartung des card10 mitgebracht, um es individueller zu gestalten oder Funktionalität hinzu zu fügen. An manchen Orten, sind Wartungsstationen verfügbar, wo card10s aufgeladen werden können und Werkzeuge und Wissen geteilt werden.*
...@@ -11,15 +12,15 @@ Aktueller Forschung zufolge wird empfohlen, das folgende mitzubringen: : ...@@ -11,15 +12,15 @@ Aktueller Forschung zufolge wird empfohlen, das folgende mitzubringen: :
Optionale Dinge, die nützlich sein werden:: Optionale Dinge, die nützlich sein werden::
* Ein Torx T6 Schraubenzieher, um card10 zusammen zu stellen * Ein Torx T6 Schraubenzieher, um card10 zusammen zu stellen
* Eine Nadel, um Dinge auf das Armband zu nähen * Eine Nadel, um Dinge auf das Armband zu nähen
* Ein Android-Smartphone oder iPhone, das in der Lage ist, via [Bluetooth Low Energy](/de/ble) (BLE) zu kommunizieren. * Ein Android-Smartphone oder iPhone, das in der Lage ist, via [Bluetooth Low Energy](/userguide/ble) (BLE) zu kommunizieren.
## Was kann ich beitragen? ## Was kann ich beitragen?
Generell gibt es eine große Bandbreite an Beiträgen. Zur Firmware, den IOs, den Apps, den verschiedenen Möglichkeiten, mit BLE zu kommunizieren, dem User Interface, der Dokumentation, die existierende Arbeit zu reviewen und natürlich deine eigenen [interhacktions](/de/interhacktions) zu schreiben! Generell gibt es eine große Bandbreite an Beiträgen. Zur Firmware, den IOs, den Apps, den verschiedenen Möglichkeiten, mit BLE zu kommunizieren, dem User Interface, der Dokumentation, die existierende Arbeit zu reviewen und natürlich deine eigenen [interhacktions](/interhacktions) zu schreiben!
Wenn du nicht weisst, wo du anfangen sollst, kannst du dir auch ein paar Ideen für Beiträge anschauen, die wir noch benötigen. Du findest sie [hier](https://git.card10.badge.events.ccc.de/card10/logix/issues). Wenn du Fragen zu einem Issue hast, kommentiere gerne oder kontaktiere die Person, die den Issue verfasst hat, über unseren [Matrix](https://en.wikipedia.org/wiki/Matrix_(protocol)):( [`#card10badge:asra.gr`](https://matrix.to/#/#card10badge:asra.gr))/[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) ( [`freenode.net#card10badge`](ircs://chat.freenode.net:6697/card10badge)) channel. Wenn du nicht weisst, wo du anfangen sollst, kannst du dir auch ein paar Ideen für Beiträge anschauen, die wir noch benötigen. Du findest sie [hier](https://git.card10.badge.events.ccc.de/card10/logix/issues). Wenn du Fragen zu einem Issue hast, kommentiere gerne oder kontaktiere die Person, die den Issue verfasst hat, über unseren [Matrix](https://en.wikipedia.org/wiki/Matrix_(protocol)):( [`#freenode_#card10badge:matrix.org`](https://matrix.to/#/#freenode_#card10badge:matrix.org))/[IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) ( [`freenode.net#card10badge`](ircs://chat.freenode.net:6697/card10badge)) channel.
Du kannst ausserdem von großer Hilfe sein, wenn du Dokumentation zum [card10logix wiki](https:://card10.badge.events.ccc.de) hinzufügst. Wenn du bemerkst, dass Information fehlt, aber nicht weißt, welche Information dort hin gehört, dann kannst du uns darauf hinweisen, indem du ein [Issue hinzufügst](https://git.card10.badge.events.ccc.de/card10/logix/issues). Bitte geh sicher, dass du detailliert beschreibst, was fehlt. Du kannst ausserdem von großer Hilfe sein, wenn du Dokumentation zum [card10logix wiki](https://card10.badge.events.ccc.de) hinzufügst. Wenn du bemerkst, dass Information fehlt, aber nicht weißt, welche Information dort hin gehört, dann kannst du uns darauf hinweisen, indem du ein [Issue hinzufügst](https://git.card10.badge.events.ccc.de/card10/logix/issues). Bitte geh sicher, dass du detailliert beschreibst, was fehlt.
## Wie funktioniert das sogenannte Wiki? ## Wie funktioniert das sogenannte Wiki?
Um die Wartung einfacher zu machen (das r0ket-Wiki läuft jetzt seit 8 Jahren!), haben wir uns enschieden, dieses Mal ein git/markdown-basiertes Wiki zu benutzen. Um die Wartung einfacher zu machen (das r0ket-Wiki läuft jetzt seit 8 Jahren!), haben wir uns enschieden, dieses Mal ein git/markdown-basiertes Wiki zu benutzen.
......
de/tldr.md → faq/tldr.de.md
View file @ cdb3584e
## tl;dr ---
title: tl;dr
hidden: true
---
- [Hardware](http://git.card10.badge.events.ccc.de/card10/hardware) - hardware repo mit docs und specs - [Hardware](http://git.card10.badge.events.ccc.de/card10/hardware) - hardware repo mit docs und specs
- [Firmware](http://git.card10.badge.events.ccc.de/card10/firmware) - firmware repo - [Firmware](http://git.card10.badge.events.ccc.de/card10/firmware) - firmware repo
- [Firmware Docs](https://firmware.card10.badge.events.ccc.de/) - rendered version der firmware-doku - [Firmware Docs](https://firmware.card10.badge.events.ccc.de/) - rendered version der firmware-doku
- [Assembly guide](/de/assembleyourcard10) - bau dein card10 zusammen - [Assembly guide](/userguide/assembly.de/) - bau dein card10 zusammen
- [LogBook](/de/logbook) - Geschichten der Reisenden - [LogBook](/logbook) - Geschichten der Reisenden
- [Interhacktions](/de/interhacktions) - eine Anleitung, um Apps zu bauen - [Interhacktions](/interhacktions) - eine Anleitung, um Apps zu bauen
- [Hardware-Übersicht](/de/hardware-overview) - [Hardware-Übersicht](/hardware)
- [USB-C](/de/usbc) - [USB-C](/hardware/usbc)
- [personal state](/ps) - [personal state](/ps)
- [app](/app) - [app](/app)
- [zusammenbau-video](/vid) - [zusammenbau-video](/userguide/assembly#assembly-video)
\ No newline at end of file
en/tldr.md → faq/tldr.md
View file @ cdb3584e
--- ---
title: tl;dr title: tl;dr
--- ---
## tl;dr
{{% notice info %}}
Deutsche Version: [tl;dr](../tldr.de)
{{% /notice %}}
- [Assembly video and instructions](../userguide/assembly) - Assemble your card10
- [app](/app) - Companion app for Android and iOS
- [personal state](/ps)
- [Interhacktions](/interhacktions) - a guide to making apps
- [Hatchery](https://badge.team/badge/card10) - the card10 app store, publish your app
- [Hardware](http://git.card10.badge.events.ccc.de/card10/hardware) - hardware repo with docs and specs - [Hardware](http://git.card10.badge.events.ccc.de/card10/hardware) - hardware repo with docs and specs
- [Hardware Overview](/hardware)
- [USB-C](/hardware/usbc)
- [Firmware](http://git.card10.badge.events.ccc.de/card10/firmware) - firmware repo - [Firmware](http://git.card10.badge.events.ccc.de/card10/firmware) - firmware repo
- [Firmware Docs](https://firmware.card10.badge.events.ccc.de/) - rendered version of the firmware docs - [Firmware Docs](https://firmware.card10.badge.events.ccc.de/) - rendered version of the firmware docs
- [Assembly guide](/en/assembleyourcard10) - Assemble your card10 - [LogBook](/logbook) - records of travellers
- [LogBook](/en/logbook) - records of travellers
- [Interhacktions](/en/interhacktions) - a guide to making apps
- [Hardware Overview](/en/hardware-overview)
- [USB-C](/en/usbc)
- [personal state](/ps)
- [app](/app)
- [assembly video](/vid)
en/firmware/_index.md → firmware/_index.md
View file @ cdb3584e
--- ---
title: Firmware title: Firmware
weight: 30
--- ---
![Firmware running FreeRTOS and MicroPython](/media/firmware/teaser.png) ![Firmware running FreeRTOS and MicroPython](/media/firmware/teaser.png)
...@@ -25,16 +26,13 @@ best way to do so is either the issues directly or alternatively the ...@@ -25,16 +26,13 @@ best way to do so is either the issues directly or alternatively the
`#card10badge` channel on Freenode. You can also reach that channel via a `#card10badge` channel on Freenode. You can also reach that channel via a
Matrix-bridge. Matrix-bridge.
card10 prototypes have been distributed to the hackerspaces listed here:
[Distribution of prototypes](../prototype_distribution).
## Overview ## Overview
To make the most of card10’s dual-core processor, its firmware will have been divided To make the most of card10’s dual-core processor, its firmware will have been divided
into two parts: The “main” firmware running on core 0 which will have been called into two parts: The “main” firmware running on core 0 which will have been called
Epicardium and the “user-code” running on core 1. In most cases this will have Epicardium and the “user-code” running on core 1. In most cases this will have
been Pycardium, our MicroPython port. been Pycardium, our MicroPython port.
<img class="center" alt="firmware overview" src="https://firmware.card10.badge.events.ccc.de/_images/overview.svg" width="600" height="auto" align="center"> [![Firmware Overview](https://firmware.card10.badge.events.ccc.de/_images/overview.svg)](https://firmware.card10.badge.events.ccc.de/_images/overview.svg)
## Details ## Details
Please tend to https://firmware.card10.badge.events.ccc.de/index.html where we Please tend to https://firmware.card10.badge.events.ccc.de/index.html where we
......
firmware/firmwareupdate.md 0 → 100644
View file @ cdb3584e
---
title: Firmware Updates
---
## Current: Queer Quinoa (2021-12-25)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.18-Queer-Quinoa.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v118-2021-12-25-queer-quinoa)
## Updating the firmware on your card10
* Download the current firmware `.zip` file to your computer
* Extract it
* Put your card10 into [USB storage mode](/userguide/general-usage/#installing-apps-via-usb)
* Copy over the files you just extracted directly into the main folder. Make sure to also update all files cotained in the `apps` folder. Note: on macOS devices it is recommended to use the terminal, e.g. for the broccoli release: `cp -r ~/Downloads/card10-v1.2-broccoli/* /Volumes/CARD10/`
{{% notice info %}}
If your card10 reboots during this operation, use the bootloader to copy the files as explained [here](/userguide/general-usage#bootloader-fix)!
{{% /notice %}}
* Eject your device (if you're doing this in the command line: don't forget to run `sync` on Linux)
* Switch your card10 off and on again
---
## Experimental Releases
These releases are untested and must be considered faulty. Always create a backup of the files on your
card10 before applying them. Please follow the steps mentioned above for the actual update.
- No Experimental version available at the moment
---
## Previous Releases
## R2R Rocket (2021-04-04)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.17-R2R-Rocket.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v117-2021-04-04-r2r-rocket)
## Pandemic Potato (2020-12-04)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.16-Pandemic-Potato.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v116-2020-12-04-pandemic-potato)
### Okra (2020-02-02)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.15-Okra.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v115-2020-02-02-okra)
### Nettle (2019-12-29)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.14-Nettle.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v114-2019-12-29-nettle)
### Mushroom (2019-12-09)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.13-Mushroom.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v113-2019-12-09-mushroom)
### Leek (2019-10-19)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.12-Leek.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v112-2019-10-19-leek)
### Karotte (2019-09-24)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.11-Karotte.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v111-2019-09-24-karotte)
### JerusalemArtichoke (2019-09-05 21:42)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.10-JerusalemArtichoke.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v110-2019-09-05-2142-jerusalemartichoke)
### IcebergLettuce (2019-08-28 23:23)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.9-IcebergLettuce.zip
- **Jailbreak relase is no longer necessary! You need to adjust card10.cfg now.**
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v19-2019-08-28-2323-iceberglettuce)
### HabaneroChilli (2019-08-27 - 11:38)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.8-HabaneroChilli.zip
- Firmware Download (with jailbreak): https://card10.badge.events.ccc.de/release/card10-v1.8-HabaneroChilli-jailbreak.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v18-2019-08-27-1138-habanerochilli)
### Garlic (day 4 - 21:48)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.7-Garlic.zip
- Firmware Download (with jailbreak): https://card10.badge.events.ccc.de/release/card10-v1.7-Garlic-jailbreak.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v17-2019-08-24-2148-garlic)
### Fennel (day 3 - 20:30)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.6-Fennel.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v16-2019-08-23-2030-fennel)
### Eggppppplant (day 3 - 00:23)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.5-Eggppppplant.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v15-2019-08-23-0018-eggppppplant)
### DaikonRadish (day 2 - 20:00)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.4-DaikonRadish.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v14-2019-08-22-1943-daikonradish)
### CCCauliflower (day 2 - 00:30)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.3-cccauliflower.zip
- [Changelog](https://git.card10.badge.events.ccc.de/card10/firmware/blob/master/CHANGELOG.md#v13-2019-08-22-0012-cccauliflower)
### Broccoli (day 1 - 19:00)
- Firmware Download: https://card10.badge.events.ccc.de/release/card10-v1.2-broccoli.zip
### Asparagus
As of Day 1, 18:00
Asparagus is the firmware that is loaded on the card10s handed out on day 1 from 18:00
en/gitlab.md → firmware/gitlab.md
View file @ cdb3584e
...@@ -3,24 +3,28 @@ title: GitLab ...@@ -3,24 +3,28 @@ title: GitLab
--- ---
# Hooray 🎉
## Post-Registration ## Post-Registration
Welcome to CCCamp19 badge card10 GitLab instance. Welcome to card10 and flow3r badge GitLab instance.
**1st**: *Check* your *mails*, links below won't work until verification. **1st**: *Check* your *mails*, links below won't work until verification.
You can find this text at our wiki: https://card10.badge.events.ccc.de/firmware/gitlab/
### What's next ### What's next
To get an understanding of card10 (cardio) checkout: To get an understanding of card10 (cardio) checkout:
- Our wiki [Wiki](https://card10.badge.events.ccc.de) - our [Flow3r Docs](https://docs.flow3r.garden)
- Explore our [GitLab Server](https://git.card10.badge.events.ccc.de/explore/groups). - explore our [GitLab Server](https://git.flow3r.garden/explore/groups).
- Also checkout our public repos at [`/card10`](https://git.card10.badge.events.ccc.de/card10/), including source for the wiki. - also checkout our public repos at [`/flow3r`](https://git.flow3r.garden/flow3r/).
### Profile Settings ### Profile Settings
Keep this tab open, accept your registration mail and you can go to this links. Keep this tab open, accept your registration mail and you can go to this links.
- Updating Your [Profile Privacy](https://git.card10.badge.events.ccc.de/profile) - Updating Your [Profile Privacy](https://git.flow3r.garden/profile)
- Adding [Two-Factor/OTP](https://git.card10.badge.events.ccc.de/profile/two_factor_auth) - Adding [Two-Factor/OTP](https://git.flow3r.garden/profile/two_factor_auth)
- Change [E-Mail Notifications](https://git.card10.badge.events.ccc.de/profile/notifications) - Change [E-Mail Notifications](https://git.flow3r.garden/profile/notifications)
- Add your [SSH Key](https://git.card10.badge.events.ccc.de/profile/keys) for `git clone...` - Add your [SSH Key](https://git.flow3r.garden/profile/keys) for `git clone...`