The Floppy PNG behind Floppy PNG holds a repository of all of my code and key configuration files (and, of course, it fits on a 1.44MB floppy). This shows how to verify it without running in a browser using just the PNG file, #Deno, #Pigz, and #NPM access.
Exactly.
This is also a glimpse of why current versions of AI vs. Barry Smith ontology style knowledge (that NASA [1] and initial iterations of Siri used) cannot compete at current civilization systems complexity. We have to process extreme amounts of movement data that is centralized vs. collaborative maps. Google maps is best because it can process the real-time flow of exhaust data coming from their products (and maps users driving in cars). This distinction is dear to me. But, the funny thing is we are now backfilling LLMs with knowledge graphs via RAG to mitigate hallucinations. I suppose for critical systems we might continue that. But here is the catch: current AI *requires movement*. The correlation between map products with ontologies is relevant. By *only* relying on centralized platforms that build models, as systems change/fail/emerge, only those centralized models that constantly build from fresh data will succeed, and current AI takes much energy, minerals, connectivity, money, centralization, etc., to make that happen. We *could* have focused on distributed knowledge via collaborative maps, but the systems became too complicated and changed too quickly. Curse Tim Berners-Lee for caving on that, even though it is the pragmatic choice (he literally said something along the lines of "ok to toss rdfs/triples/owl style because we get similar results from LLM style AI". But praise Tim Berners-Lee for his early vision and later semantic web, tip o the hat to you sir.")
Social Media is The Great Filter.
https://blossom.primal.net/6217c3470491bc675a5f69850d726d6d9d27adda1721ef8b8043b0ce75660400.mp4
This is very good. It is ubiquitous.
I published my Logical Map paper on Zenodo:
A background vid for the document.
I finished the paper. The full version is on https://logicalmap.org
Wow! Solid support across many devices with progress every year. How did I miss that? Thank you.
I, too, *only* know of halfin because of the tag #culturalcognition . I've always been a Bitcoin outsider, but I ♥️ the cultural cognition work of Michael Tomasello. I understand halfin is a legend here, but thought you would enjoy the outside perspective. Besides my posts, this one is the only one on Mastodon with the cultural cognition tag, so I see it often. And, halfin retweeted something I completely align with, that ideology strongly shapes our view of science consensus.
Does CORS mess up Opengraph tags with Nostr basic architecture? (I really don't know, myself, but it seems like something that might be a problem, and you would know more.)
I've found quite a few friends on the Internet, but they became what I consider friends IRL (long discussions in person, helping eachother with IRL stuff). Do you distinguish between finding friends and forging friendships?
WoT *is* the message, in whatever way you want to package it: shared cultural cognition or tech. It forms a trap. It might be a necessary trap to deal with opportunists and spammers, or simply, as you say, something that goes back to tribal need. I used to figure I wanted the WoT/reputation. I don't think that anymore. It is something I learned here on Nostr, along with nostr:nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqtxwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tmwwp6kyvtjw3k8zcmp8pervct409shwdtwx45rxmp4xseryerdx3ehy7f4v3axvet9xsmrjdnxw9jnsuekw9nh2ertwvmkg6n5veen7cnjdaskgcmpwd6r6arjw4jsqgq6lcx8fc7h0p8t4ya9u0a92jnwavqe9rgjwwdw3wjgxfuxsz8rd5mths8c 's memetic circus tricks. A good hack is to just get a new npub and start over with the few people that had any genuine engagement related to priority work. This is especially important if you don't care about Bitcoin or the other cultural attributes that dominate Nostr.
It is easy for me to try too hard. I hope I've learned to back off of this thing called reputation. It is related to identity, and that alone is a huge nasty trap we fall into (and it is monetized). Mostly, what I post as an individual means zero. What I create, how I interact and care IRL matters. Sure, that sounds pat and trite, but I also believe that gets at the WoT issue as well. Create something useful, and people will find you regardless of the WoT of the day/platform.
If I get some free time, I'm thinking that a hybrid between ham radio licenses and CB radio (with channel 9) would be an interesting project. (my x.509/MQTT tunnel/Tower w/ Nostr event objects routing idea). I'm not so sure it addresses WoT any better... haven't investigated that far... I have something to finish, first. I have this intuition there is something there, though.
Anyhoo... Jack's money has been put to great use here, IMO.
#offgridEver watch this?
I need to finish up my Logical Map Whitepaper; however, I have an idea for Nostr that I can't tamp down. Nostr devs have figured out a great MVP for sending notes over relays (NIP-01), as well as dealt with many other issues via the other NIPs. My own use of Nostr for a crisis scenario, though, requires more control and efficiency. I think it would be useful to control both sides of the connection before application data flows. This will reduce spam and CPU/network use. It requires an issue by the server to specific clients. Now, part of the administrative nightmare can be mitigated by combining it with Nostr identity. Consider an MQTT broker a "tower", and an MQTT publisher client a "set" (as in CB/Shortwave set). A tower could issue certs for npubs. These npubs all have the same cert. The cert is just used to secure communication. The server has two ways to verify, then, the cert and the fact that the event objects were signed by the nsec.
Another NIP (NIP-TWR?) would define how this works on the client app (the web app running in the browser that connects to relays over Nostr). I'm thinking the set could be a local service that takes event objects over websockets and routes them through to the tower. The tower works on pub/sub with varying QoS values (deliver once, broadcast only, deliver more than once, etc... pure MQTT). There would be 40 topics on each tower that match. Towers share messages based on follower lists. Alice might have a set/tower tunnel to Tower A. Bob might have a set/tower tunnel to Tower B. If Alice posts "need help getting water", she could post it on channel 9 (matching CB emergency). Bob follows Alice. Bob will see a replicated message from Tower B on channel 9.
What I've done is broken up tiers of identity so that we get a middle tier rather than completely distributed. NIP-TWR could ensure compatibility easily, as the client app can do both (and read Kind 0 references for towers, etc).
MQTT has an advantage in that it already exists, offers pub/sub, has websocket options, is ubiquitous, and often uses self-signed TLS client certs. Much of the meta verification and communication could be handled over regular Nostr, but the key appeal of spammers (notifications and views) could be completely blocked out, yet still retain compatibility. No wacky WoT is needed, just a cert issued by a tower operator (and there is nothing stopping somebody from bringing up their own tower and updating their kind-0 entries). We know MQTT scales because of IoT.