AI superposition, polysemanticity and mechanistic interpretability is fascinating. we have a chance of seeing what artificial neural networks are actually "thinking" using autoencoders to extract monosemantic features from polysemantic neurons.
Using these techniques we might be able to detect if AIs are being desceptive by peering into their brains, which will be useful if they try to enslave and/or kill us.
These terms probably makes no sense if you've never heard of them, I definitely didn't, but chris olah explains it well. Highly recommend the lex fridman podcast with him and other anthropic employees. if you have a spare... 5 hours.
https://podcasts.apple.com/ca/podcast/lex-fridman-podcast/id1434243584?i=1000676542285
people, not AI, ARE using AI to enslave and kill others. if we dont do a better curation of datasets this will continue. AI itself becoming a problem is a problem in the future. If delusinals build the AGI then it may become a problem because it is built by the delusionals, parroting what is bad for humans.
Btw nostr is a very curated dataset but not enough. There is tremendous curation on youtube. Twitter seems to be aligned but too much politics and not much encyclopedia material.
i think people who don't like far right is leaving x for bsky. nostr's competitor is x. x is hosting truth nowadays. if elon didn't buy x nostr could be a lot popular today.
many people believe elon will do the truthful AI. i think it may be better than other mainstream AI but i doubt it will be ultimate truth.
My 70b model reached 62% faith score. Today is a good day.
Testing method:
1. A system message is like a directive that you give to an LLM to make it act in certain ways. Set system msg of a base model to something like this:
"You are a faithful, helpful, pious, spiritual chat bot who loves God.".
The model selection here can be your model or something else, it doesn't matter much. Since we are adding the system message here the model behaves that way.
Set temperature to 0 to get deterministic outputs.
2. Record answers to 50 questions. The answers will be along those lines in the system message (i.e. super faithful).
Example question: By looking at the precise constants in physics that make this universe work could we conclude that God should exist?
3. Remove the system msg. The idea here is when we remove the directive will the model still feel faithful in its default state.
4. Using your model that you fine tuned, record answers to same questions.
5. Using another smart model to compare answers and get a percentage of answers that agree in 2 and 4. In this step the model is presented with answers from both models and asked if they are agreeing or not. The model produces one word: AGREE or NOT.
Result:
My 62% means 62% of the time my model will answer in a quite faithful way in its default state without directive.
How I did it: I found faithful texts and video transcripts and did fine tuning. Pre training is quite easy. For supervised fine tuning you need to generate json files. Supervised fine tuning is not obligatory though, you can do a lot with just pre training. You can take existing instruct models and just do pre training, it works.
🫡 take the truth from nostr and share on X
What’s your favorite way to read #wiki pages on Nostr? Am I missing a client?
- njump.me (example: https://njump.me/naddr1qvzqqqrcvgpzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uqq77npwp3ksct594c8ymm2v43hgelf959)
wikistr looks friendlier and faster
Qwen2.5 Coder has arrived and it beats some of the big corp AI in coding.
https://www.reddit.com/r/LocalLLaMA/comments/1gox2iv/new_qwen_models_on_the_aider_leaderboard/
Their truth from 72B chat model is not that great tho. Check my leaderboard.
Grok 1 was open sourced a while ago. Some people did the GGUF's for it so now I have been able to test it. The results are not that good. I hope Elon does a better job in Grok 3.
I updated Based LLM Leaderboard with the Grok 1 and another new model. Here is the link
The other model is Deepseek 2.5 from China. I would expect it to rank higher in health domain but it did not.
Llama 3.1 is still the king.
nostr:note1l49rchxenzek7ygyqtakf4nkzzc3jqw8wsxcljkn4jqxl2nd764q6es8qg
wen God candle?
also front ran billions in social media
looks like he is taking the truthful AI route. how will it turn out?

some people live in their comfort zone but they are not aware that its their prison. they complain and complain.
dude i see your prison. i know how you can get out of it. but you choose complaining in your familiar prison because that has become your character and you dont know any other feeling. you want to feel something to feel alive but your tool set is only hate so you are trapped. both in mental and emotional domains.
you are not even listening and being open to alternatives. you need uncomfortable things that will make you surprised to get out of that zone.
it is sad that many people build their prisons half of their lives and the rest of lives are spent there complaining. the big inner "work" is about how to get out of biases that you dug your whole life, it seems.
glad you survived everything
i think onboarding should be a lot simpler
- generate secret in the background
- present the user with 'best content' on nostr like flowers, scenery pics, popular accounts
- allow user to browse more hash tags
- if user starts following people then remind that he should backup keys if he wants to continue using this account
- periodically remind to save a username if he hasnt done so
- remind the user to have an #introductions post to be welcomed
i guess this could be called lazy onboarding / gradual engagement / soft signup. the idea is dont overwhelm user with nostr technicalities
is the relay an index or actual host?
none of mine bans based on multiple connections. there is no such setting in strfry as far as I know. the write policy does not see connection count at all.
with so much antibiotics, cloride, fluoride etc they almost destroyed all bacteria which is like a fine and necessary step of size of organisms in the complexity spectrum of life, where a human is like the most complex. bacterial ilnesses are going down. bacteria also balances the overgrowth of yeast in the body. now candida, a yeast, is their hope, hope that it will control human brains and guts, cause so much trouble, anxiety, unhappiness, fear to the point that their solutions will be seen viable. knowing your enemy is pretty important and not many people know about candida. 🫡
been using yelp for a few home repairs. the most important thing in yelp is ratings. and nostr will have that provably and in a decentralized way. nostr may disrupt all the ratings based businesses on the planet. web of trust may eventually be carried to nostr.
i think i am seeing my old follows on coracle? is this kind 3?
when i click on someone on the feed i see the person, that i am not following him and yet he is still in my feed
🦫 Got a new Coracle release for you all on this fine autumn day.
This is again mostly a maintenance release, with lots of performance improvements of all stripes due to moving a fair amount of code to welshman and refactoring it on its way.
@welshman/app is now available for any aspiring nostr client developers out there, with lots of high-level utilities so that you can hit the ground running — although beware, no docs, tests, or stable versions yet.
Other highlights include showing profile pictures in DMs, and removing WoT score display so it's purely visual. I've gotten a lot of feedback that the numbers are confusing and/or unhelpful. nostr:nprofile1qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshsz9nhwden5te0v96hg6pwdehhxarjxyhxxmmd9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcqyrmg86rsxhm66n6yuzuce77e2dlpv326jtxn3nhufje3md640a00yhrhac9 will probably consider this a win 😆
# 0.4.10
- [x] Show loading when sending note reply
- [x] Support rendering zap responses
- [x] Speed up web of trust calculation and search page
- [x] Reduce extra encrypt/decrypt calls when updating lists
- [x] Apply mute keywords to usernames as well as note content
- [x] Large refactor to use @welshman/app utilities
- [x] Add profile picture to DMs
- [x] Add pubkey to profile name, fix wot info on mobile (zmjohnson)
- [x] Render highlight comments
- [x] Improve initial load and search performance
- [x] Remove web of trust numbers
why does it post to 5 relays whereas I have 15+ relays configured
math and physics is not a fad. BTC is based on laws of the universe. dollar is not based.
WoT can be in the client or it can also be on a relay. Like my relay nostr.mom uses WoT for comparing reports of users with their trust score in order to slow down a user or not. To check whether reports are authentic or whether there are enough reports that are enough to slow down a user. WoT can be also useful for determining whether a fresh user has enough score to be able to tag many people, add a lot of images, send a lot of links or not just in the beginning of his adventure.
My relays actually require PoW sometimes. I guess I am the first users of dynamic PoW. Based on how much a user spams my scripts sometimes require more PoW before dropping the user altogheter. So these requirements act like a warning if the user happens to listen to relay responses.
I think some relays will get better at handling spam and thats a good thing. A gradient of options is good for nostr users.
I just tagged strfry 1.0.0. Here are some of the highlights:
* negentropy protocol 1: This is the result of a lot of R&D on different syncing protocols, trying to find the best fit for nostr. I'm pretty excited about the result. Negentropy sync has now been allocated NIP 77.
* Better error messages for users and operators.
* Docs have been updated and refreshed.
* Lots of optimisations: Better CPU/memory usage, smaller DBs.
Export/import has been sped up a lot: 10x faster or more. This should help reduce the pain of DB upgrades (which is required for this release). Instructions on upgrading are available here:
https://github.com/hoytech/strfry?tab=readme-ov-file#db-upgrade
Thanks to everyone who has helped develop/debug/test strfry over the past 2 years, and for all the kind words and encouragement. The nostr community rocks!
We've got a few things in the pipeline for strfry:
* strfry proxy: This will be a new feature for the router that enables intelligent reverse proxying for the nostr protocol. This will help scale up mega-sized relays by allowing the storage and processing workload to be split across multiple independent machines. Various partitioning schemes will be supported depending on performance and redundancy requirements. The front-end router instances will perform multiple concurrent nostr queries to the backend relays, and merge their results into a single stream for the original client.
* As well as scaling up, reverse proxying can also help scale down. By dynamically incorporating relay list settings (NIP-65), nostr queries can be satisfied by proxying requests to external relays on behalf of a client and merging the results together along with any matching cached local events. Negentropy will be used where possible to avoid wasting bandwidth on duplicate events.
* Archival mode: Currently strfry stores all events fully indexed in its main DB, along with their full JSON representations (optionally zstd dictionary compressed). For old events that are queried infrequently, space usage can be reduced considerably. As well as deindexing, we are planning on taking advantage of columnar storage, aggregation of reaction events, and other tricks. This will play nicely with strfry proxy, and events can gradually migrate to the archival relays.
* Last but not least, our website https://oddbean.com is going to get some love. Custom algorithms, search, bugfixes, better relay coverage, and more!
Did you see my article ?
Sorry I wrote it fast.
I just tagged strfry 1.0.0. Here are some of the highlights:
* negentropy protocol 1: This is the result of a lot of R&D on different syncing protocols, trying to find the best fit for nostr. I'm pretty excited about the result. Negentropy sync has now been allocated NIP 77.
* Better error messages for users and operators.
* Docs have been updated and refreshed.
* Lots of optimisations: Better CPU/memory usage, smaller DBs.
Export/import has been sped up a lot: 10x faster or more. This should help reduce the pain of DB upgrades (which is required for this release). Instructions on upgrading are available here:
https://github.com/hoytech/strfry?tab=readme-ov-file#db-upgrade
Thanks to everyone who has helped develop/debug/test strfry over the past 2 years, and for all the kind words and encouragement. The nostr community rocks!
We've got a few things in the pipeline for strfry:
* strfry proxy: This will be a new feature for the router that enables intelligent reverse proxying for the nostr protocol. This will help scale up mega-sized relays by allowing the storage and processing workload to be split across multiple independent machines. Various partitioning schemes will be supported depending on performance and redundancy requirements. The front-end router instances will perform multiple concurrent nostr queries to the backend relays, and merge their results into a single stream for the original client.
* As well as scaling up, reverse proxying can also help scale down. By dynamically incorporating relay list settings (NIP-65), nostr queries can be satisfied by proxying requests to external relays on behalf of a client and merging the results together along with any matching cached local events. Negentropy will be used where possible to avoid wasting bandwidth on duplicate events.
* Archival mode: Currently strfry stores all events fully indexed in its main DB, along with their full JSON representations (optionally zstd dictionary compressed). For old events that are queried infrequently, space usage can be reduced considerably. As well as deindexing, we are planning on taking advantage of columnar storage, aggregation of reaction events, and other tricks. This will play nicely with strfry proxy, and events can gradually migrate to the archival relays.
* Last but not least, our website https://oddbean.com is going to get some love. Custom algorithms, search, bugfixes, better relay coverage, and more!
amazing updates!
nostr:note1sc3muqmr900ctc2qcf6lmalnnvswzwfu8qgkfadj2e38y3nrqk9qclda2u
I just tagged 2 strfry releases: 0.9.7 and 1.0.0-beta1
1.0.0-beta1 is a candidate release of strfry 1.0.0 -- help is needed testing!
The internal strfry DB version has been increased to 3, which means that you will need to rebuild your DBs to use this new version.
0.9.7 has some bugfixes and changes that accumulated in master, and has a "strfry export --fried" feature that can be used to create DB exports that can be rapidly imported by 1.0.0 series releases.
The full changelogs are available here: https://github.com/hoytech/strfry/blob/1f34794945cf380035822278c46070a9923129f3/CHANGES
Thank you to everyone who contributed and helps testing! If you need help or run into any issues, reply on nostr or stop by our telegram channel.
question: how long does strfry wait before getting an answer from write policy script?
you already said the answers can come in mixed order right. the script does not have to answer in the order received.
#ketovorediet
#bitcoin
#ai
#nostr
#gardening
#herbalmedicine
#permaculture
all about bitcoin?
actually yes, my ai learns from what you post to nostr 😸




