Marek S. Ł.
@marek@m5l.eu
I now have 32 GitHub sponsors for @silverbulletmd: https://github.com/sponsors/silverbulletmd a nice binary round number.
GitHub sponsors is nice in that 100% of proceeds (minus stripe fees that it is built on) goes to me.
The cost: GitHub lock in. I’m not a huge fan of the Copilot direction that GitHub/Microsoft is going into, but leaving it now is harder. Don’t want to lose sponsors over it.
Still it’s time to diversify. What other sponsorship services would people recommend for an open source project? The lower the margin the better, obviously.
@zef @silverbulletmd +1 for Liberapay
- switching between #Zig versions, I liked it more than the dedicated anyzig
- #Python venv activation – it's silly but feels so good, and collaborates with uv
- ensuring I have the right language server and formatter for a project, be it #Lua, #TypeScript, and trying out various options for Python
- setting LANG="C.UTF-8" only in the specific project folder because #Ansible refused to work with Polish...
The final boss was getting a really comfortable Tree-sitter setup: get the #Rust CLI, write grammar in #JavaScript, re-generate and run tests on source change as a mise Task. And then I only cloned the repo on another machine and was ready to go!
This post was written as a more cultured outlet for my excitement instead of aggresively committing mise.toml into every repository I touch
My ISP was kind enough to give me a learning opportunity in how I can manage access to my homelab. While access to #selfhosting can't be in my place by definition, I can at least have it on a VPS from a local company to resist monopolies :)
Join the fun at: https://paste.sr.ht/~maarrk/2f1125139c62ebc567d15eac5e066a73ef638845
Live location is very sensitive data, but #selfhosting the server with TLS and basic authentication gives me more privacy than the big tech cloud. And it only needed reading a bit of MDN and making a basic #Docker image based on #NodeJS
npm and make, no sudo install for you two. And leave my /usr/local alone!It was the talk "How to Build Software From Source" from @andrewrk@mastodon.social where someone taught me what build prefix is. I think that's an example of why hanging around #zig language is so beneficial – it also taught me a lot more about building C and libc than any other tool. Many layers of dirt and rust (pun intended) are washed away and you see the basic systems that were under there all the time.
What made me finally try something else than raw pip and venv was easy installing of multiple Python versions. I was completing a PR to a library that (admirably) wants to support the old ones as well. Once I had the tool, I tried it for releasing a new version of my own PyPI package, and I wasn't ready for how fast and convenient it would be.
So far I'm using Nextcloud for everything you mentioned, except notes (@silverbulletmd@fosstodon.org)
git worktree for the rescue:I was working on updating a #cpp project to a newer #Qt version, but wanted to keep comparing to a #git tag from some time ago. The problem is that checking out a different commit changes all the files as far as #CMake is concerned, and everything builds from scratch. If only there was a way to have another copy of the same repo without cloning...
find . -name '*.qml' | xargs sed -i 's/\(import [A-Za-z0-9.]*\)[ ]*[0-9.]*/\1/g'
Which translates to "please remove all versions from import statements in my #Qt QML files"
Jak mam całe zdanie to dużo zgaduję z kontekstu, tak myślę że mógłbym pociąć próbki z bloga i SteMi_J na fiszki po jednym słowie dla Anki (oprogramowania, nie znajomej Anny).
Widzę dużo rzeczy które chcę poprawić, ale wrzucam teraz jako ślad którędy może iść początkujący.
Podobny efekt szybkiego uczenia się symboli dzięki relacji głoski dźwięcznej i bezdźwięcznej jest też w sylabariuszach japońskich i tengwarze Tolkiena, i bardzo go doceniam. Przez to że w zasadzie każdy znak jest i tak minimalny, to chyba nie ma dużej wartości w nadmiernej optymalizacji prostoty znaków dla częstotliwości głoski.
Podsumowując, z mojej niedoświadczonej perspektywy, SteMi jest super. Duże uznanie i podziękowania za ciekawe narzędzie.
/.-/...//-.--/---/..-//.../././/.../-/../.-../.-..//--./---/-//../-/ 😉
Tempo pisania na razie niewiele mniejsze niż lewą, może warto by się uczyć równolegle obiema?
...najpierw zaprezentuję nową stenografię. Nową/starą - ale jakże zgrabną, poręczną, którą polecam wszystkim zainteresowanym, szczególnie, jeżeli są praworęczni.https://www.stenografia.pl/blog/2011-01-18_pisanie-prawa-reka-to-proste/
Boys don't grow up, we just change LEGO to #CAD
But seriously though, I think that your point is well supported by research under the term "desirable difficulty".
However I can highly recommend the FreeOTP+ fork which has some other nice features, but crucially, saves and loads data correctly.
inotifywait --monitor --recursive ~/.configThis shows me what files are changed when I click "Apply". This way I don't need to wade through pages of config file documentation, but I still know what I need to reproduce.
This time it's #Debian with #Docker. I used to avoid containers, preferring to run services directly instead. But setting up backups made me appreciate the separation between the application data in image and persistent state in mounted volumes. The final piece that convinced me is the ability to self-host my own container registry with @forgejo@floss.social
I'm doing the initial setup through #Ansible (learned from @notthebee@tilde.zone), but specific applications are managed via dockge. The ambition to do every adjustment through playbooks burns out really fast when working with a single instance.
Although familiarity with usual vim still comes in handy on the school computer 😅
I'm expecting to also do Debian and Docker, but with Ansible and Borg backup. I'm curious to be convinced otherwise
This is what #FOSS promises to be, and it does feel nice to actually do it.
I did enjoy the ease of setup of TkInter, and compatibility with Matplotlib, but I was missing the simplicity of immediate mode libraries. In trying to emulate these, now a few callbacks trigger "given this dataclass with state, the widgets should look like this".
The micro-management gremlin is whining that it's repeating useless work, but more importantly the window is complete and I can go on with the experiment.
Thanks @grunfink@comam.es for the #snac server, @stefano@bsd.cafe for the blog posts that pointed me to it, @voron@snac.nya.pub for the theme and @manton@manton.org for motivating me with your book