treve

One thing to also look out for is some distros will but /tmp in RAM, and claude loves to fill that

If git used reflink / CoW when available it would make this a lot faster.

No, there not really an extension system. I kind of consider the html renderer more of an example implementation, and assume people would want to build implementations in their framework of choice, but I can totally see it would be nice for people to define their own question types and hook into the renderer / validator.

Yep! https://github.com/askdown

Yeah! this is mostly already supported:

  ? A date after today
  [date min="2026-10-13"]

  ? A number between 10 and 100 that's a multiple of 5
  [number min=10 max=100 step=5]

I didn't want to pack everything on the homepage example, but there's more examples in the form builder.

Also see:

https://askdown.dev/spec#4-question-types

Something I've been running on- and off again in my career, especially during freelance stints is that it's been annoying to describe forms in a portable format.

If you use markup, HTML alone is not very expressive and is missing some fairly common use-cases, and the JSX snippets of existing UI frameworks aren't very portable. JSON-Schema is more expressive in terms of describing the shape of the result, but json-schema alone is usually not enough information to build a user-friendly form.

I've created a few versions of this DSL over the years but finally decided to try and take it a bit further.

My hope is that people like this and build implementations of this spec for a variety of frontend and traditional frameworks.

I know this will not cover every application's use case and it's not meant to supplant general application forms, but I especially think this will be useful for cases where you want your users to be able to create forms.

Feedback very welcome, especially if you have ideas on how to make the markup itself be more readable!

MSN Messenger was a bit after ICQ's peak

Yes you are right. With HTTP/2 responses can be sent out of order, but once they are sent down the pipe they have head of line blocking and have to arrive at that order, unlike QUIC.

Websockets don't really have an advantage here because typically websockets are implemented server-side as event based systems, and if a RPC paradigm is put on top of it has the same properties as HTTP/2 request/responses ordering. So if HTTP/2 doesn't have head of line blocking, then you can't argue that websockets do.

I was around 16 when I discovered this, and it was my first IRC client. Didn't fully get what IRC was yet. It felt like a new world opening up.

I've been meaning to dust off my black plastic intel macbook and see if it's still usable as a workstation. Go back to Snow Leopard

It's not a great idea. I wrote something a few years ago if it's interesting:

https://evertpot.com/get-request-bodies/

Still does. On gnome you can switch via the lock screen.

Linux had this well before OS X

I've been wondering if I can somehow get the Toshiba Satellite VGA font back to today.

I just installed Proxmox for the first time with a 5 disk ZFS array. Very basic stuff but I already had to go to the CLI a few times and it didn't really feel that well integrated. Even setting up the array didn't work (non-descript -1 error message, and ended up needed to use -f on the cli). I also couldn't find a zfs create equivalent (but that could have been me?)

It's fine because I'm comfortable in the CLI but I read your comment and wanted to share that it felt a bit rudimentary at best.

Laws in the US aren't taken as literal as in civil law systems. The intent and precedent is what carries much more weight in the end. Graph calculators are unlikely to be tested in court because it's irrelevant with respect to what this law is trying to accomplish.

https://en.wikipedia.org/wiki/Common_law

I often see laws discussed here and people finding some edge case and presenting this as a gotcha. The reality is that it's unlikely to matter.

Public services don't need to be 'economical'

It's wild this is what you took from that, but no. My issue was with the word 'Hype'. Would you call windows Hype because it's bigger?

Some cognitive dissonance going on here. The vast majority of current Linux Desktop users are on Wayland, and X11 is phased out across the board. Calling it hype is absurd.

Good modern protocols will explicitly define extension points, so 'ingoring unknown JSON keys' is in-spec rather than assumed that an implementer will do.

it's nice to be able to use https locally if you're doing things with HTTP/2 specifically.

Nobody is interested in AI commentary.

or 'cascade' ?

I replaced all my Dropbox uses with SyncThing (and love it). I run an instance on my server at all times and on every client.

If you think about it the spirit of the internet is based on collaboration with other parties. If you want no third parties, there's always file: and localhost.

Yeah I would argue that it's possible to do it well with Backbone, and you end up with something much leaner but it requires a really strong understanding of state/event flow and lot of discipline, whereas with React the correct way to handle this is the 'obvious' path, which dramatically lowers the barrier to entry.

A good engineer is not a perfectionist, but they're not callous either. It's knowing when to make the trade-off, or at least making an informed guess.

I don't think you'll find many recommendations for key lengths under 128 bits / 16 bytes these days.

For me they are weirdly hard to obtain. Don't show up in second hand shops. Ebay shipping is prohibitively expensive.

There's 2 cases being discussed. A UUIDv7 is a bad secret, but it's fine for many other ids. If I can guess your user id, it shouldn't really matter because your business logic should prevent me from doing anything with that information. If I can guess your password reset token it's a different story because I don't need anything else beyond that token to do damage.