If backend's your thing, htmx might be off interest.

https://htmx.org/

https://www.thepsmiths.com/p/review-lectures-on-the-icosahedron

Also check out the Common Lisp Portable Perl Compatible Regular Expression library.

https://edicl.github.io/cl-ppcre/#create-scanner2

Have you thought about NIP 46 Nostr Remote Signing? It uses NIP 44 for encrypting messages between client (programs) and signers (programs).

And, by my simplistic understanding, that is just NIP 4 with a different encryption algo, but otherwise equivalent ECDH and similar metadata profiles.

"Google Business Profiles" for local searches, so you'll use names like "Thai Restaurant Near Me".

You should've included references to the original source, I thought you wrote the text.

Even worse, the videos in your posts were not from the original post. I thought they were very biased and unfair. I consider the last video in particular (it seems to be a deep faked voice) to be a thinly veiled incitement to hate.

Shame!

If "some jerk" deletes my post, it wastes my time, and will cause me to reply less in the future (to everyone else too), that's the "chilling effect" I was thinking about.

Ultimately, I think the poster/replier should own their own notes (undeletable), that's like a basic principle of nostr.

I tend to agree with nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd that reports (kind 1984) seem to be the best way to do this. I can reply to you, and you can tag my reply as low value/spam, and other readers (or their clients) can decide for themselves.

If I reply to one of your posts, you could cause my possibly long, well considered, reply to be deleted? This could chill most controversial/contentious conversations.

This does not sound sustainable. I think clients will have to start to use shared reports (kind 1984) more heavily.

I'm using a poor translation from Spanish so I may not be reading the post correctly, but I thought the explanation was pretty reasonable although I do not understand Fediverse culture.

It sounds like Fediverse users expect their conversations to be private and constrained by some terms of service (specific to each Fediverse node?). Are their posts made public, or only gated behind logins like a private forum? Having public posts that are constrained may be incompatible with the natural tendency of how information flows.

About the issue of mostro's keys - we've briefly discussed this in the past, but I now wonder if it's possible for Mostro to share the relevant private keys with the original profile owners on demand (although I'll need to brush up on HD security - how/will key derivation need to be hardened here to avoid revealing all keys)?

If possible, this is still not ideal given that Mostro will continue hold the shared private key (and needs to be trusted), but at least the original profile can now also post on nostr (maybe gradually migrate to a new more secure key pair). Mostro can also update its bridging rules for that particular profile (eg it can stop mirroring posts or delete them etc). I'm just "brainstorming ideas while ignorant" here...

Fair enough, I read up a bit more and do see it now.

Since when are tags case sensitive? Why not use a completely different letter?

Physical travel between stars is so slow, it'll only happen once - the first wave of colonists spreading outwards from some origin will be von Neumann-like probes. Unlike popular conception of these probes as big machines, I believe they would be nanomachines traveling at substantial fractions of light speed, launched using synchrotrons [Liu's "Three Body Trilogy"]. They only need a way to slow down at their destinations. After a brief pause to establish themselves, they "reproduce" and set out for the next star systems [Hanson's "grabby aliens"] pretty much spreading at close to the speed of light.

Subsequent travel between colonised star systems need not be physical, but merely information and AI programs transmitted at light speed between established outposts and probes in transit [also explored elsewhere in the TV show Altered Carbon].

Also implicit in this future are Drexler style nanomachines, likely merged with biological systems with no obvious boundaries between mechanosynthesis and biochemistry.

Also implied: an earlier AI "apocalypse" as machines replace/merge with humans (or biological aliens elsewhere in other star systems) at rapid rates upon achieving sentience (possibly even as quickly as overnight). [Yudkhowsky et al]

A possible scenario for alien contact is initial establishment of contact remotely through radio, followed by negotiations of terms for trade, terms of surrender, merger etc, and finally updates to the source codes of both civilisations. No space battles or other kinetic "negotiations", except in rare cases of a communication breakdown (or where one side refuses to negotiate for some reason?).

Apologies, I think I need to retract my link above - that describes the work that clients have to do. Oracles don't have to do all that, though they do sign prefixes of the numeric outcome instead.

I suppose having a tag could work, but it looks like I'm at the limit of my knowledge on DLCs here.

In looking around, I also found this,

https://github.com/nostr-protocol/nips/pull/919

It may have more work in it, but not I'm sure if the PR is still active.

nostr:nprofile1qqs0awzzutnzfj6cudj03a7txc7qxsrma9ge44yrym6337tkkd23qkgpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgewaehxw309akxjemgw3hxjmn8wfjkccte9e3k7mf0qy88wumn8ghj7mn0wvhxcmmv9uuxfel8 was the last to touch that.

Sorry, by ASCII, I meant the price is encoded as a string and JSON.

In practice, DLC numeric outcomes has a very complicated format, I don't know if it's possible to shoehorn that into your proposal:

https://github.com/discreetlogcontracts/dlcspecs/blob/master/NumericOutcome.md

I think this is close to what DLC's need, if the feed publisher uses fixed timestamps, eg something that is always on the hour and minute, 12:00:00 13:00:00 14:00:00 etc for an hourly price feed.

That way, the exact format and content of the possible prices can be determined ahead of time when creating the DL contracts.

Oh, we probably can't use ASCII prices? This may be better for categorical outcomes.

Would this be too far out of scope from what you originally had in mind?

That "efficiency loss" is just more heat, so I believe mining wins out in energy terms. You still need to pay for a miner.

What changes the picture more drastically is if you put heat pumps in the picture. Each watt of electricity can give you a few watts of heat!

Never just force, always --force-with-lease

👍 just thought it could be relevant, I quite like the content on the rest of that website too.

Have you heard of nncp before?

https://www.complete.org/nncp/