Things Perkeep believes:

• Your data is entirely under your control

• Open Source

• Paranoid about privacy, everything private by default

• No SPOF: don't rely on any single party (including yourself)

• Your data should be alive in 80 years, especially if you are

While Perkeep can store files like a traditional filesystem (think: “directories”, “files”, “filenames”), it’s specialized in storing higher-level objects, which can represent anything. (photos, likes, tweets, measurements etc)

Tool to convert JSON into Go structures.

I like the idea, but my laziness makes me avoid any non-automatic methods. I’d prefer a format similar to Mycomarkup or Markdown, but with built-in support for embedding images and other binary content, turning a web article into a single file. I’m aware of data: images in Markdown, but they’re not very convenient to use.

Our design goals are safety, performance, and developer experience. In that order.

Contrary to popular belief, simplicity is also not the first attempt but the hardest revision

code, like steel, is less expensive to change while it's hot.

Safety

NASA's Power of Ten — Rules for Developing Safety Critical Code

• Use only very simple, explicit control flow for clarity.

• Put a limit on everything. Fail Fast

• Assertions detect programmer errors. The only correct way to handle corrupt code is to crash.

• Assertions are a safety net, not a substitute for human understanding.

  • Build a precise mental model of the code first.

  • encode your understanding in the form of assertions,

  • write the code and comments to explain and justify the mental model to your reviewer,

  • and use VOPR as the final line of defense, to find bugs in your and reviewer's understanding of code.

• No memory may be dynamically allocated (or freed and reallocated) after initialization.

• Declare variables at the smallest possible scope, and minimize the number of variables in scope.

• Good function shape is often the inverse of an hourglass: a few parameters, a simple return type, and a lot of meaty logic between the braces.

• Centralize control flow. When splitting a large function, try to keep all switch/if statements in the "parent" function, and move non-branchy logic fragments to helper functions.

• Centralize state manipulation. Let the parent function keep all relevant state in local variables, and use helpers to compute what needs to change, rather than applying the change directly.

Developer Experience

• Add units or qualifiers to variable names, and put the units or qualifiers last, sorted by descending significance. latency_ms_max rather than max_latency_ms.

• Callbacks go last in the list of parameters.

• Order matters for readability (even if it doesn't affect semantics). On the first read, a file is read top-down, so put important things near the top. The main function goes first.

• Don't overload names with multiple meanings that are context-dependent.

A markdown-like journal language for plainly writing logs , gantt charts , blogs , feeds , notes , journals , diaries , todos , timelines , calendars or anything that happens over time .

TempleOS has images in comments btw.

What are home row mods? What is a mod-tap? What settings do you need to use? What are the alternatives? And more in this article...

bouncepaw:

I don't think home row mods are a good idea.

I use home row mods for several month, the only downside is a need for a separate layer without mods for gaming

Development Platform for building event-driven and distributed systems. Move faster with purpose-built local dev tools and DevOps automation for AWS/GCP.

Do you actually want to write? Ok. Then write. In a text file on your computer, in a pastebin, on a blogging platform, on neocities, on cohost or mastodon, on a copy-pasted template from github pages, in /var/www, on some forum that nobody’s looked at in 15 years. It really does not matter. Go write.
But, perhaps you don’t really want to write. Do you like tinkering with site generator tools? Then fucking tinker to your heart’s content. You don’t need to have an end goal where you actually put some thinkpiece or technical writeup on the website. Building it can be its own reward.
If you love it, let it consume you. If you hate every moment you spend with it, why are you trying to do it? Real winners quit.

if you are unfortunate enough to browse a fandom wiki without an ad blocker, you will experience what i like to call "attention assault"

if you are a fandom wiki owner & you would like to move your wiki content elsewhere, i will offer you my expertise at $0/hour. i know lots about servers, software, and maintenance. just email me - let's get you out of fandom's ecosystem.

Set in Tokyo’s Suginami-ku neighbourhood, home to many manga artists, Open Sky House is home to artists and architect Zajirogh, his wife, and their three children. Having always dreamed of living in a camper or a ship, Zaijrogh designed a large central open-air courtyard and covered it with a retractable sail-like sheet. The family uses the courtyard as a living room which is furnished with camping furniture that can get wet or be moved quickly if needed. A series of colourful walls line the courtyard, with precious items that need to stay dry kept behind a set of glass and steel sliding doors with another set connecting to the fully equipped L-shaped kitchen. The second story features space for the family to sleep, work and play and includes a 1sqm (small closet-sized) study that Zajirogh refers to as “his little sanctuary”. A door leading onto the balcony wraps around the open roof, this provides access to open and close the roof as well as an area for Zajirogh to paint freely without concern about mess.

Прекрасная статья о выборе человечества - покинуть планету с её проблемами или остаться и решать их? Обратиться к корням - природе, ручному труду или отвергнуть прошлое и адаптироваться к жестокому космосу?
Как сказал Курт Воннегут: "What makes you think you’re going anywhere?"
Подобные Дайсонам, в моей душе борются отец и сын, правда скорее поменявшись ролями. Тянуться к недостижимому космосу, к неизведанным и от того прекрасным технологиям с их бесконечными проблемами? Или обратить внимание на верную спутницу человека - прекрасную Землю и, возможно, обрести покой в отказе от амбиций?

Kind of controversial take on note taking systems. I can relate though, because i was lost in a burden of creating perfect knowledge management system for a long time without creating any knowledge. Simplest approach with commonplace notebook is what working for me now.
Comments are also useful.

Getting lost in your knowledge management system is a fantastic way to avoid creating things.
Most heart-stopping writing comes from synthesizing the previously unarticulated in the moment. Rather than reaching for your database, try channeling what’s in the air at this very second. These read/write errors are what we call originality.
Leonardo da Vinci kept all of his notes in one big book. If he liked something he put it down. This is known as a commonplace book, and it is about how detailed your note-taking system should be unless you plan on thinking more elaborately than Leonardo da Vinci.
Shun the useless adoption of the aesthetic of the useful. When something can be like work or like play, never make it work.

Однажды в конце декабря, когда воздух пахнет сгорающими над городом фейерверками, а улицы полны паникующих из-за цен на горошек, я решил научить программированию бомжа...
Фрустрация от когнитивной сложности — это то самое неприятное чувство, которое возникает, когда не можешь разобраться в какой-то запутанной фигне. В результате для любого человека процесс программирования переполнен страданием. Нормальный человек боль не любит и прогать бросает

How to backup photos using Apple, lightroom, nextcloud