letter to my 24 yo
save money in the current crappy job to save you
- from crappy sentiments/transactions/jobs/education programs/ stereotypes
- invest in peace of mind, solitude/read to acquire a skill set & frugal life hacking and a meaningful network slowly for 5 yrs +
- stabilize in 10 yrs and start doing something for lifetime , it doesn't matter who knows you and vice versa ,b there and spend your life
P : yml -> nix & yml -> python
T : yml -> python
#parser
precisely why I didn't like #python back then
9.5.2025 01:22precisely why I didn't like #python back thenexposing a query language to untrusted clients increases the attack surface of the application. Nevertheless, the variety of attacks to consider was even broader than I imagined, and mitigating them is quite a burden.
> if a field resolver hits an external data source such as a DB or HTTP API, and it is nested in a list containing N items, it will do those calls N times.
in REST, we can generally hoist nested N+1 queries up to the controller, which I think is a pattern much easier to wrap your head around:
#graphql
https://bessey.dev/blog/2024/05/24/why-im-over-graphql/
trying #hasura
7.5.2025 11:12trying #hasurawhy you need `...` in any #nixos system module argument?
without them it ll be called with with the argument systems , which isn't expected.
also acceptable ` { pkgs ? import <nixpkgs> { }, system }:`
Are markets biased towards profit ? No
Are they biased towards the loss? No
Can someone they rig them? Yes
Who?
That also regulation decides
As with India there s a good news with twist
#zerodha a bootstrapped indian #unicorn without external funding without external funding is launching for #FOSS
The twist [s]
- founder is allegedly trying to get close to the current #rightwing gov, for a banking license
- word is that its influenced by the opensource model of #Meta
https://floss.fund/blog/announcing-floss-fund/
You should not expose a #database externally. You should expose an API with appropriate authentication and authorization rules that can communicate with your database.
https://www.reddit.com/r/PostgreSQL/comments/zxc0go/best_practise_exposing_db_access_to_internet/
gotta fix this #docker perm #nixos #zsh
can't think of why
any quick and dirty fix?
-- Just another simple man chasing a deadline
My understanding of state is very simple
What ll I do in a state that strips me of all my rights and leaves me #homeless in a hostile infra
What ll I do in a piece of case away stateless land , without any supply chain , but I am entitled to do what I want
On unix-like systems, paths are fundamentally bytestrings and not necessarily Unicode, so it’s necessary to accept bytes. Since strings are nearly always more convenient, they take both. The unveil wrapper here will do the same. If it’s a string, encode it, otherwise pass it straight through.
https://nullprogram.com/blog/2021/09/15/
#unix #python
in a container runtime i should be able to change anything at runtime, right?
right!
#podman
https://gist.github.com/sjimenez44/1b73afeae3eec26a1915b0d4d5873b8f
a] with a systemd service on a headless device , it may be preferable to start it on boot and keep it running rather than only running during an interactive login session. Among other things, this helps prevent a *race condition* that may occur when socket activation fails to initialize audio devices in time for their first use, leading to one-time errors after reboots
b] til #spawning tmux is managed by systemd even if its a user service
when is a #systmd job or service or #linux user session supposed to linger is matter of how a service depends on the other *or not*
moreover some of these may have their own user accounts like rootless containers , with their own namespaces , which need be mapped to other services like #vpn
one can always check it with systemctl --user or linctl
so #podman has this runRoot directory: "/run/user/1000/containers" graphRoot directory
tbc
decades ago I did a gig to write #python and I hated my life everyday
29.4.2025 10:52decades ago I did a gig to write #python and I hated my life everydayUNIX systems have implemented the auxiliary vector feature. In essence, it is a list of key-value pairs that the kernel's ELF binary loader (fs/binfmt_elf.c in the kernel source) constructs when a new executable image is loaded into a process. This list is placed at a specific location in the process's address space; on #Linux systems it sits at the high end of the user address space, just above the (downwardly growing) stack, the command-line arguments (argv), and environment variables (environ).
https://lwn.net/Articles/519085/
rant
I just need a unique ID , tld ( me@xyz.pqr) , file sharing ( next cloud) and notification service ( libnotify) to communicate.
where I store file[s] or not or my prerogative.
Memory is cheap and life is too short to use <quote>free </unquote> TBs from #bigtech , I can just #selfhost my data and id can get verified with #weboftrust .
I d rather use a combination of 3 independent #foss services , than a one stop , know it all service.
I am good with UI of emacs or any file rendering thing.
Why am I to swipe the trash I never asked for.
Can file be malicious, spam yeda yeda yeda, so re services? Yes of f***g course road is always risky if you re careless
Just keep two partitions like 2 git branches.
One for safe files and others to be tested /tmp
just read 1 message at a time and don't be an attention w**re
Oh, bastards have turned the #economy in to attention economy.
Then have some real face and real life, like any living being. I am good with less
i don't want #saas
it is frequently necessary to specialize some of the parameters of a multi-parameter procedure. For example, from the binary operation cons one might want to obtain the unary operation (lambda (x) (cons 1 x)). This specialization of parameters is also known as "partial application", "operator section" or "projection".
Yet, #Scheme is not a curried language---the number of arguments passed to a procedure must match the number of its parameters at all times. This allows zero- and variable-arity procedures but in order to specialize parameters one usually has to write down a lambda-expression and invent some irrelevant identifiers for its formal variables (x in the example).
It is possible in #Scheme to implement a macro turning a multi-argument procedure into a nesting of single-argument procedures and back. These operations are usually called "curry" and "uncurry" in other programming languages. Yet, Scheme remains an inherently uncurried language and is not prepared to deal with curried procedures in a convenient way. Hence, a "by the book" implementation of currying would only be useful if you apply it in the sequence "curry, specialize some arguments, and uncurry again"---which is exactly the purpose of the macro cut specified in this document. The primary relevance of currying/uncurrying in Scheme is to teach concepts of combinatory logic.
hence so many variants of #lisp
https://srfi.schemers.org/srfi-26/srfi-26.html
lazy iterators , as in linked lists with lazy eval
/random
how important is it to comment the code
very
⬆️
⬇️