commit c07b7f36ae5845b50a9d5cb2a4b52cefa8d4c73a · technoduck.me/staticrustator

+1 -1

content/posts/003-led_hoop.md

···

       12
       12
        
       

     

       13
       13
        
       Since for the first time, I didn't want to experiment with absolute microscopic sizes, I decided that a 4 cm hoop was an adequate project to attempt.

     

       14
       14
        
       

     

       15
       15
       -
       ![schematic_kicad_image](img/led_hoop/schematic.png =800x)

     

       15
       15
       +
       ![schematic_kicad_image](/assets/img/led_hoop/schematic.png)

     

       16
       16
        
       

     

       17
       17
        
       An Attiny 24/44/84A can be used, I went with a -M variant, since it is slightly larger then the -MM variant, by a whole mm, which I assume will be easier to solder.

     

       18
       18

+90

content/posts/006-tangled.md

···

       1
       1
       +
       ---

     

       2
       2
       +
       title: Tangled

     

       3
       3
       +
       date: 2025-03-17

     

       4
       4
       +
       ---

     

       5
       5
       +
       

     

       6
       6
       +
       # Personal git forges

     

       7
       7
       +
       

     

       8
       8
       +
       In pursuit of federation for git forges, few attempts are being made.

     

       9
       9
       +
       

     

       10
       10
       +
       Until recently the main one being [Forgejo](https://forgejo.org/), with utilization of ActivityPub, the driving force behind Mastodon, Pleroma, and the like, as communication protocol.

     

       11
       11
       +
       

     

       12
       12
       +
       ## how Personal

     

       13
       13
       +
       

     

       14
       14
       +
       Forgejo is a community maintained fork of Gitea, and for good reason and with good effect. It allowed them to while maintaining some compatibility, but also go into a radically different direction then Gitea could.

     

       15
       15
       +
       

     

       16
       16
       +
       A consequence of being a fork of Gitea is well, at core being a git forge designed for communities and not individuals.

     

       17
       17
       +
       

     

       18
       18
       +
       Not in a *usage* sense, but in **operations** sense.

     

       19
       19
       +
       

     

       20
       20
       +
       ## say what

     

       21
       21
       +
       

     

       22
       22
       +
       Frogejo my beloved, always will be. Its delightful to work with, its easy to host and run, its dead easy to update (don't forget breaking config changes), action runners are easy to setup and use, and the whole thing is easy to manage.

     

       23
       23
       +
       

     

       24
       24
       +
       That all however comes at a cost of a whole-ass web-server running all the time, with a postgres db running in the background where your repositories are actually kept.

     

       25
       25
       +
       

     

       26
       26
       +
       At scale its well, the best case scenario. But we aren't talking about the best case scenario we are talking about 1 (one) idiot (big one) running it for personal projects.

     

       27
       27
       +
       

     

       28
       28
       +
       And that's a lot of overhead for what can be a bare git repo on a server running git-daemon.

     

       29
       29
       +
       

     

       30
       30
       +
       Its not useless overhead, but having a whole gig of memory on my poor 2 gig VPS taken up by a git forge I don't use even a 3rd of services of is a bit too much. (also cant federate just yet).

     

       31
       31
       +
       

     

       32
       32
       +
       

     

       33
       33
       +
       

     

       34
       34
       +
       # Alternatives?

     

       35
       35
       +
       

     

       36
       36
       +
       [git-send-mail](https://git-scm.com/docs/git-send-email), the most federalized mode of collaboration in the world, used to work on the Linux kernel, arguably? largest community project right now.

     

       37
       37
       +
       

     

       38
       38
       +
       It is flexible, infinitely customizable for both you the user and the recipient, and requires no account other then a single (1) email address I hope everyone has.

     

       39
       39
       +
       But like IRC chatrooms, it is realistically used by far not all even amongst developers, and is more or less inaccessible to people new to the whole git thing.

     

       40
       40
       +
       

     

       41
       41
       +
       [Radicle](https://radicle.xyz/), fully P2P, custom communication protocol, similar system that all nodes are viewable from the central website, but there is no central authority for what the repo state is, it is local first.

     

       42
       42
       +
       Really interesting, **written in rust**, and will get a good amount of attention from me because well it's pretty cool. To collaborate in the network, like with the Tor network, from which it drew heavy inspiration as I understand (again, really cool),

     

       43
       43
       +
       one has to run their own node. Which isn't ideal always for, same issues as before, beginners (although getting to understand such things one could argue is a worthy and formative trial by fire, and should be done).

     

       44
       44
       +
       

     

       45
       45
       +
       [Tangled](https://tangled.sh) The topic of today

     

       46
       46
       +
       

     

       47
       47
       +
       

     

       48
       48
       +
       # [Tangled](https://tangled.sh)

     

       49
       49
       +
       

     

       50
       50
       +
       A very new and currently in development git forge based on the AT Protocol, used by Bluesky.

     

       51
       51
       +
       

     

       52
       52
       +
       I will let them make [their own case](https://blog.tangled.sh/intro), in a rather short and sweet introduction.

     

       53
       53
       +
       

     

       54
       54
       +
       With the long story short being as such.

     

       55
       55
       +
       

     

       56
       56
       +
       To collaborate, one requires a Bluesky account. More precisely an account in the AT Protocol network, but I digress.

     

       57
       57
       +
       Repositories are hosted on **knots**, headless servers that behave very much like git-daemons, with repositories being hosted in bare repos.

     

       58
       58
       +
       

     

       59
       59
       +
       There is a central knot managed by the tangled team, `knot.tangled.sh`, on which anyone can make a repo, or if you are authorized with other knots, hosted by anyone, you can author repos there.

     

       60
       60
       +
       

     

       61
       61
       +
       All of that, can be viewed on centrally in the appview hosted by tangled.sh team at, you guessed it, [tangled.sh](https://tangled.sh).

     

       62
       62
       +
       (in theory there can be other appview, the same way as there are alternative clients for bsky.app, there could be alternative appviews for tangled, with the same underlying content).

     

       63
       63
       +
       

     

       64
       64
       +
       So, account creation is not complex, hosting your own nodes is not a requirement, it is linked to a social network, which could be argued to be excessive, but you can create alternative accounts if you don't want your code to be associated with your public activity (or the other way around).

     

       65
       65
       +
       

     

       66
       66
       +
       

     

       67
       67
       +
       And, while Forgejo is indeed lightweight and performant, very few things can compete with

     

       68
       68
       +
       ```

     

       69
       69
       +
       * knotserver.service - tangled knot server

     

       70
       70
       +
            Loaded: loaded (/etc/systemd/system/knotserver.service; enabled; preset: enabled)

     

       71
       71
       +
            Active: active (running) since Fri 2025-03-14 02:44:33 UTC; 3 days ago

     

       72
       72
       +
          Main PID: [you thought] (knotserver)

     

       73
       73
       +
             Tasks: 7 (limit: 2424)

     

       74
       74
       +
            Memory: 50.9M

     

       75
       75
       +
               CPU: 32.406s

     

       76
       76
       +
            CGroup: /system.slice/knotserver.service

     

       77
       77
       +
                    - [nuh-uh] /usr/local/bin/knotserver

     

       78
       78
       +
       ```

     

       79
       79
       +
       

     

       80
       80
       +
       Ah yes, 50.9M of memory used.

     

       81
       81
       +
       Much better.

     

       82
       82
       +
       

     

       83
       83
       +
       Anyway gotta get now `git.technoduck.me` to redirect to my git profile on tangled, which should be [https://tangled.sh/@technoduck.me](https://tangled.sh/@technoduck.me).

     

       84
       84
       +
       

     

       85
       85
       +
       Or fully remove, I have not decided yet.

     

       86
       86
       +
       

     

       87
       87
       +
       

     

       88
       88
       +
       Anyway, that's it.

     

       89
       89
       +
       

     

       90
       90
       +
       Go on collaborooting or something.