Nostr notes by ari :prideified:

> A date specification may use "~" to indicate the ...

2026-03-25T20:14:23Z

In reply to nevent1q…uylx
_________________________

> A date specification may use "~" to indicate the last day in a month. For example, "*-02~03" means "the third last day in February," and "Mon *-05~07/1" means "the last Monday in May."

of course it is:<code>❯ systemd-analyze calendar ...

2026-03-25T20:10:53Z

In reply to nevent1q…p0q3
_________________________

of course it is:<code>❯ systemd-analyze calendar '000000000000002029-000000000001/0000005~00005' Original form: 000000000000002029-000000000001/0000005~00005 Normalized form: 2029-01/5~05 00:00:00 Next elapse: Sat 2029-01-27 00:00:00 CET (in UTC): Fri 2029-01-26 23:00:00 UTC From now: 2 years 10 months left </code>

Quiz: do you think this is a valid systemd calendar ...

2026-03-25T20:09:30Z

Quiz: do you think this is a valid systemd calendar specification?<code>000000000000002029-000000000001/0000005~00005 </code>

Shoutout to FreeCAD having silly rendering issues around ...

2026-03-16T11:27:09Z

Shoutout to FreeCAD having silly rendering issues around transparency. That's literally my desktop wallpaper (default wallpaper in recent version of kde/plasma) shining through the window.

edit: this might be a kde bug, see https://critter.cafe/@irina/116238645215664128 :blobcatjoy:

#Freecad #kde

> - nie żartuj tak > - wejdź na office kropka com > - ...

2026-01-05T19:15:01Z

> - nie żartuj tak
> - wejdź na office kropka com
> - nie no, nie zajebali by tak marki którą mają od kilkudziesięciu lat
> - mówię, wejdź na office kropka com
> - … kurwa mać

#microsoft #office #copilot

Glitch does what Mastodon't :ablobcatwink:

2025-11-17T10:40:44Z

In reply to nevent1q…5vl2
_________________________

Glitch does what Mastodon't :ablobcatwink:

it's async. it's all async. you can't do shit with ...

2025-11-17T10:23:08Z

In reply to nevent1q…wmz0
_________________________

it's async. it's all async. you can't do shit with this without async. :blobcatangry:

cargo workspaces are kinda silly

2025-11-17T01:20:58Z

In reply to nevent1q…c5q8
_________________________

cargo workspaces are kinda silly

and splitting it up into parts properly.

2025-11-16T22:51:23Z

In reply to nevent1q…rf6h
_________________________

and splitting it up into parts properly.

that project would really benefit from a clean-er design

2025-11-16T22:49:33Z

In reply to nevent1q…2adr
_________________________

that project would really benefit from a clean-er design

Nostr event nevent1qqsthzng2c3u7szpd8ll5z2pyaazxgxktexxr2m62ld99kj7e7md3vqzyzughd2wjhx94666l5qqjt3c8s52ugj2lhrjyrjan7w8czynpgkj6dan4x7

2025-11-16T22:47:17Z

what if… rewrite-it-in-rust… again, from scratch?

Chromebook alignment chart, for identifying ChromeBooks ...

2025-11-13T16:55:24Z

Chromebook alignment chart, for identifying ChromeBooks

checked the freezer?

2025-08-13T12:02:11Z

In reply to nevent1q…vax5
_________________________

checked the freezer?

In preparations for #why2025 i made a @npub1ly6…kh0q logo in ...

2025-08-05T00:11:20Z

In preparations for #why2025 i made a Warsaw Hackerspace (npub1ly6…kh0q) logo in the form of pseudo-neon made out of acrylic/PMMA, HDF, and an addressable RGBW led strip. :blobcatenjoy:

like an onion, it has many layers, all 3mm thick<li>full transparent acrylic on the front</li><li>mostly full HDF, with frosted acrylic inserts for diffusing the led strip into the shape of the logo</li><li>four structural HDF layers with a single continuous path for the led strip, which is slightly different (somewhat simplified) from the "front" shape</li><li>backing PMMA layer, to somewhat protect the led strip, and prevent it from falling out if it unglues itself.</li>

The general shape is based off of a version of the logo q3k :blobcatcoffee: (npub1y0e…t60a) designed for the [Warsaw Hackerspace website](https://hackerspace.pl/ ), aptly named "neon-syrenka.svg" ("neon-mermaid.svg"), but it took a few years before a physical representation in a (pseudo-)neon form was created :ablobcatwink:
most of the "artistic" design i did, including the simplified ledstrip path, was done in Inkscape, with the electronics box designed using FreeCAD

but yes, it would be nicer if it could have a capacity setting, ...

2025-06-11T13:31:18Z

In reply to nevent1q…qjls
_________________________

but yes, it would be nicer if it could have a capacity setting, instead of days.

but… it can automatically delete files, and IIRC it's even ...

2025-06-11T13:30:37Z

In reply to nevent1q…e73x
_________________________

but… it can automatically delete files, and IIRC it's even done by-default since a while ago.

is bluesky's decentralized design in the room with us?

2025-04-25T09:21:46Z

In reply to nevent1q…d70r
_________________________

is bluesky's decentralized design in the room with us?

aperiodic reminder that you can instruct git to automagically use ...

2025-04-09T09:12:38Z

aperiodic reminder that you can instruct git to automagically use different url scheme, eg. to avoid having to deal with http(s) auth even by accident.

simply run git config --global --edit and add lines like these:<code>[url "git@github.com:"] insteadOf = https://github.com/ ;[url "git@code.hackerspace.pl:"] insteadOf = https://code.hackerspace.pl/ ;[url "git@codeberg.org:"] insteadOf = https://codeberg.org/ </code>;

today's run-out-of-disk-space was sponsored ...

2025-03-08T16:42:35Z

today's run-out-of-disk-space was sponsored by…<code>256490 store paths deleted, 673223.50 MiB freed </code>

just #nixos things

Nyaa! It's getting cold out here :blobcatcozy: ...

2024-09-28T11:12:50Z

Nyaa! It's getting cold out here :blobcatcozy:

Just python being sus:<code>>>> ...

2024-09-14T10:37:28Z

Just python being sus:<code>>>> chr(sum(range(ord(min(str(not())))))) 'ඞ' </code>

short answer: yes daemonising is, as a concept (forking into ...

2024-09-02T10:59:30Z

In reply to nevent1q…66y7
_________________________

short answer: yes
daemonising is, as a concept (forking into background), essentially incompatible with go runtime model, which implements its own M:N threading and uses OS threads rather loosely, and it's trivial to end up in a situation where the process would already have some threads started before it would reach your daemonizing code.

long answer: still yes, but daemonizing is bad anyway.
as a preface, the following is coming from being burned in many ways by processes attempting to drop privileges and daemonizing on their own. most often by silent failures with nothing on stdout/stderr/logs; but sometimes by leaking/retaining elevated privileges when they weren't supposed to.

self-daemonising is surprisingly difficult to do properly in general, arguably maybe even impossible if your code is anything but a statically linked executable directly interfacing with the kernel syscall interface (not even going through libc) because of how many things happen before "your" code is reached in process lifetime.
i've seen services dropping privileges improperly too often to trust just about any service to do so, regardless of what programming language they're written in, and instead i strongly prefer to have a service manager that would setup proper environment (privs dropped, etc etc) first, and then start the service.
if nothing else, there's less security sensitive code to audit, and it's in just one place, instead of having a myriad variations, with every service author implementing their own slightly different way of doing things.

"getting paid" is a side effect, and thus not permitted ...

2024-08-04T17:14:48Z

In reply to nevent1q…2lce
_________________________

"getting paid" is a side effect, and thus not permitted in a functional programming language