Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ
4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f
ʙoarᴅ cerᴛɪꜰɪeᴅ ᴛecʜno-ᴘʜaɢe. mʏ mɪnᴅ ɪs ʜunɢrʏ, anᴅ ꜰeeᴅs on noveʟᴛʏ. ᴅo ʏou ʜave someᴛʜɪnɢ ᴛo sʜare ᴛʜaᴛ ɪ never ʜearᴅ? "𝔅𝔢 𝔠𝔞𝔯𝔢𝔣𝔲𝔩 𝔣𝔬𝔯 𝔫𝔬𝔱𝔥𝔦𝔫𝔤; 𝔟𝔲𝔱 𝔦𝔫 𝔢𝔳𝔢𝔯𝔶 𝔱𝔥𝔦𝔫𝔤 𝔟𝔶 𝔭𝔯𝔞𝔶𝔢𝔯 𝔞𝔫𝔡 𝔰𝔲𝔭𝔭𝔩𝔦𝔠𝔞𝔱𝔦𝔬𝔫 𝔴𝔦𝔱𝔥 𝔱𝔥𝔞𝔫𝔨𝔰𝔤𝔦𝔳𝔦𝔫𝔤 𝔩𝔢𝔱 𝔶𝔬𝔲𝔯 𝔯𝔢𝔮𝔲𝔢𝔰𝔱𝔰 𝔟𝔢 𝔨𝔫𝔬𝔴𝔫 𝔲𝔫𝔱𝔬 𝔊𝔬𝔡. 𝔄𝔫𝔡 𝔱𝔥𝔢 𝔭𝔢𝔞𝔠𝔢 𝔬𝔣 𝔊𝔬𝔡, 𝔴𝔥𝔦𝔠𝔥 𝔭𝔞𝔰𝔰𝔢𝔱𝔥 𝔞𝔩𝔩 𝔲𝔫𝔡𝔢𝔯𝔰𝔱𝔞𝔫𝔡𝔦𝔫𝔤, 𝔰𝔥𝔞𝔩𝔩 𝔨𝔢𝔢𝔭 𝔶𝔬𝔲𝔯 𝔥𝔢𝔞𝔯𝔱𝔰 𝔞𝔫𝔡 𝔪𝔦𝔫𝔡𝔰 𝔱𝔥𝔯𝔬𝔲𝔤𝔥 ℭ𝔥𝔯𝔦𝔰𝔱 𝔍𝔢𝔰𝔲𝔰" - 𝔓𝔥𝔦𝔩𝔦𝔭𝔭𝔦𝔞𝔫𝔰 4:6-7 ᴛᴇʟᴇɢʀᴀᴍ: @mleku1 ᴍᴀᴛʀɪx: @mleku17:matrix.org ꜱɪᴍᴘʟᴇx: https://smp15.simplex.im/a#PPkiqGvf5kZ3AbFWBh3_tw1b_YgvnkSgDEc_-IuuRWc

also, he is probably the absolute best javascript programmer in all nostrland. hzrd149 is good but he's just got that japanese minimalism down pat

Replying to Avatar Laeserin

#Jumble is now so good that my plan is just to host one. I've lost all motivation to build a social feed.

It's like nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl has just been sucking my social feed building willpower out of my veins with a sippy straw. And not a paper straw. The full plastic straw, in hot pink.

nah, it's high grade japanese steel.

yeah, i got intp when i was younger but now i fairly consistently get INTJ so it obviously changes with age. i figure "wisdom" makes you more quick to decide

marathons are overrated. sore knees come from doing high impact exercise like running or skateboarding

but joint problems are a sign of autoimmune problems as well, though also from scarring. i have both, and i'm 49.

i think it's other genetics in this case tho

except i have this in common and also only just started to look a bit old in the last 3 years

i hardly didn't even notice until i hit 40 that i was slowing down haha. then i ground to a halt at 45, because i got very sick. i'm coming out of it now, and experience substitutes a lot for strength. and you can still be flexible, that's something i find easier to keep than strength also, since it isn't so much bound to hormone levels.

i'm sure you know of some famous wild children stories. the brothers who founded rome were this, romulus and remus. then there is tarzan. i forget what other similar stories there are, but the human capacity to make sense of the world without anything more than experience is a lot more powerful and beneficial than experiences imposed on the human.

yeah makes sense. i personally mostly want to move from mastering one thing well enough to design something on it, and then make a new design on another thing. this does not lead to mastery of any given craft but makes it quite easy for me to adapt to new projects in my work as a computer programmer. it's more abstract, and not so much about mastery as about enumerating the structure of something.

so, i know a good bit of like 6 different human languages, but never mastered one

i can play guitar, recorder, and keyboard, but never mastered one

the first time i have actually really dug in and decided to master some things, first one was golang, second was bitcoin. third was nostr. but they are protocols, not practices. i'm immune to nonsense fud and disinfo about these subjects but i only master them as far as i need to apply to working with them.

i guess that's the thing about being intuitive. you don't really need to master something to be able to catch the pattern and elaborate it jazz style. AI systems are kinda similar, in that you feed them a load of data, and they distil a pattern out of it and then you can get them to freestyle a new version that mixes it all up.

so, i'd say that NT is a very common result for people with high intelligence and creativity. and the cool thing is we are kinda rare, like maybe 10% of teh population has the combination. by the numbers, i'd guess we are 2/16th of the population.

https://serbia.com/a-fresco-from-visoki-decani-which-confused-the-scientists-around-the-world/

700 years ago, an artist created a fresco of the crucifixion which included what appears to be some person piloting it and two emblems of an 8 pointed star with a circle in the center

according to the author of The Apocalypse of Yajnavalkya, the 8 pointed star emblem with the circle at the center and 8 triangles is the emblem of Basilea, the atlantean empress who got later called several other names and deified as a goddess

ah yes, Inanna

her emblem is the 8 pointed star with a circle at the center.

i have this tattooed on my right shoulder, in the form designed by Peter Carroll, the progenitor of Chaos Magick. i had the tattoo updated with some white pigment to make rays out from the points of the triangle and an alien skull in the style of punisher in the middle of the circle.

feels like i was tuned into something.

i'm not gonna look at 8 pointed star symbols in the same way again. they are a common nautical symbol as well, representing the 8 cardinal directions.

Replying to Avatar PiecoverBTC

The Tail Emission Attack on Bitcoin

I am going to explain why tail emission is an attack on the Bitcoin core principles and why it would spell the end of Bitcoin as we know it, if ever implemented in any serious kind of way.

Bitcoin Core Dev Peter Todd, came up with the idea of taxing Bitcoin holders on their money to pay miners more for security, like we don't already pay miners in fees and there wasn't already a fee-market incentive for miners to plug in their machines or unplug when unprofitable, again another attacker trying to address a none issue with fake solutions with fear. Let me explain farther below.

Bitcoin works because of the 21M hard cap removing this would spell the end of it as hard money, tail emission is like making a small hole in the bottom of dam that will eventually grow big and make cracks until the dam falls. Why is this an attack?

Well, most people who buy bitcoin are buying it because it has a hard cap of 21million that nobody can change, that's the reason why I started paying attention to Bitcoin in the first place, so removing that already turn off a lot of us as we start pricing in future taxes or increase in the money supply, not only that, the other problem is "who has the right to print the money this time and every other time in the future? Peter said it's for security, well I want remind him that there is a difficulty adjustment in Bitcoin that always look for free market equilibrium, when hashrate is too high it goes up when it's too low difficulty goes down to incentivize mining, and if he is concern about the halving lowering rewards in bitcoin terms well again SATs get more valuable overtime so any amount of transaction fee will support the network even when all the 21M coins are mined. The issue here is if we start printing more SATs to devalue the Bitcoin overall market cap, Bitcoin price falls miners get paid less valuable money therefore less miners are incentivized to secure the network, so it would actually break Bitcoin, but let address his other arguments.

Peter also points out that the miners will collude to attack the network in a potential future, "future he can't even predict". Here again another strawman argument, asking for power so he can protect you in a future attack that he doesn't even understand if possible or not. Miners don't control the network, they may decide to pay a bunch of devs to introduce a code that benefits them but what are the chances the code ever get into everyone else node? He said well do the math it's good to do the math.

Ok, I am going to do the math, I am sure in 10 to 100 years from now 100 of countries plus millions of businesses plus billions of people will want to send some bitcoin utxo on-chain, if each block contains 5,000 to 7,000 transactions in average of 1000Sats fee each then that's an equivalent block reward of 5M to 7M SATs each, that's $500K minimum at $10Million bitcoin. So you see transaction fees can easily support the network in the future without any changes to Bitcoin. But again these people will always find an excuse to convince you why they need to print money for free that everone else have to work for, so don't fall for it.

Lastly, I want to point out that the Bitcoin limit is not a number you can change just like that because it's based on time, that's why Satoshi said he had to be very careful with the 21M number because once the network starts you can't go back and change it, you would have to go back in time Jan 3rd, 2009 to change the genesis block to change it, this core design principle is set in stone for the rest of Bitcoin lifetime and we would like to keep it that way.

https://stacker.news/items/1053591/r/piecoverBTC

to mathematicians, this notion of the tail emissions, which really just means interpolation of the stair-step decline of rewards, as an attack, is ridiculous.

if the graph is plotted out, and the number of sats at each block is the same in both cases, there has been no change in supply. it does, however, mean that likely the subsidy will continue for a few years after the halving pattern would have dropped to zero. but that extra would literally be the smoothed out segment of the last reward cycle moved to the next. it would only extend to the next cycle after what would have been the last cycle, and only part way into it.

what is more important is the complexity of implemenatation

tail emissions curves are an exponential decay cycle which means transcendental math. the risk of forks being caused by this is substantial, the algorithm is complex and there is not many common fixed point fractional exponentiation implementations in existence. not sure why, but without a deterministic formula for it, i say better to stick to halving.

well, i think that it's not really useful for one-off stuff like relay configurations but for distributing them it might make sense, as it saves some on bandwidth. but i'm not seeing a strong case for this. events are not that big in data size, especially not when encoded as raw binary. typically follow lists are like 1/4 or less the size of the json

i've been thinking about this and it can be a privileged event that only the relay and the author can read, and using bloom filters to designate the list so even if the list is leaked you can only check it one by one to see which npubs are included

hungarian is the weirdest language in europe. it reminds me of turkish and chinese.

local relays definitely are a thing. especially they should have little crons that fetch from other relays. and also there is a great need for inbound routing so users can also have their frens write straight to their relay.

some of these obstacles are systemic issues on the internet that bias against p2p, and most p2p protocols are quite deficient, but largely because of the restriction of routing.

other lists have to be supported by the client, that's a major problem.

also, it doesn't have to be public, mute lists have a private section now too.

the main problem really is just that primal pretty much administers the God List and they are extremely biased about who gets on it. the real challenge is a good client to onboard people to. coracle probably could do the job, and even he made it so it can be whitelabeled. the other thing is outreach to other social networks where there might be interest.

it's sold at most garden stores as "dusting sulfur" and other than that you need to collect guano and powder up charcoal. voila, black powder.

i describe it as the eastern switzerland. probably i would rate it higher than switzerland these days, also. technically my oma was swiss.

trieste is a pretty little town. i remember the park there, big pretty park.

so, it was slovenia. i never went to rostijl in slovenia. i had burek tho. i couldn't say that slovenian burek was better than serbian burek tho. same same. the best burek, much better than turkish.

i'm debugging a http SSE subscription mechanism at the moment. almost got it working. events are now being delivered and all, just not sure about whether it's properly removing listeners

so i've been posting events to wss://test.mleku.dev to trigger subscription deliveries. i had to add a new "whitelist" feature to the relay because omg the amount of clients sending events and then not responding to auth, it was a constant stream of bullshit i couldn't see any of the messages i was sending to it.

man, so glad i fixed the weird race condition bug with the spider on #orly

now i'm watching the logs of my test and prod deployments and not seeing anything that bothers me, and also giving me a small smug sense of satisfaction that people are already using them both extensively.

my first formal position of employment involved working with a government IT department, specifically accounting. the number of things they did with excel was hilarious.i didn't do much work with excel in my role but i learned quite a lot about writing excel scripts at that time.

funniest thing about excel spreadsheet scripting is that it seems to be something that women are particularly good at. there was a lot of women in the office i worked in. it left me with a vague impression in general that women were good bookkeepers, and later encounters with book keepers confirmed this. it's beautiful tho.

not saying in all cases women are not capable of really inventing things but they sure as hell are good at operating calendars and ledgers.

i cite the case of Mileva Maric, wife of Einstein, for this. i'm pretty sure what the women of yugoslavia say about her is correct: that she was the actual inventor of relativity theory. so, don't misread me by thinking that women are not capable of invention. to the contrary, i think they are very capable as a class of human in the process of invention. probably they originally invented math and calendars. the motivations for which should be clear, since the first big insight about these two topics logically would have likely emerged from those who are most subject to biological clocks. ie, fertility.

not even scientific papers lack an abstract at the top that summarises the text.

i was feeling this urge to feed it to an LLM to write one for me but then i thought better of doing that because of the lack of credibility of the user who dropped the link.

i can't see myself using it personally but it will be fun to see them being used. probably could be quite useful for things like deciding on venues and activities for meetups.

took a while to dig around and find the problem. it's partly related to the fact that the event and tag unmarshaler doesn't copy memory (which makes it faster) but this also makes concurrency cause funny problems.

what was literally happening was that an event was being decoded, and then the buffer holding the memory where an event was sliced out of, was then overwritten by the next incoming event from the relay the client was connecting to, and by the time the event was being saved to the database it had already been mangled. i think also the event ID, signature and pubkeys were being overwritten as well, because those also are zero copy operations.

lesson learned: zero copy codecs must be paired with fresh buffers from the network transport. otherwise you get data races.

now, i'm getting more in the frame of mind to think straight, and this is because i had a can of red bull. which in combination with the allergy messing with my brain suggests that eliminating the allergens will help me quit these bad habits. probably nicotine is also suppressing allergy symptoms on my brain. my brain is literally swelling and this is messing with my thinking, reducing my IQ dramatically.

glutens are the worst, second is caseins and especially caseins that have been ultrapasteurised, most likely unpasteurised natural milk would not do this. but it's what did it to me today. my brain has felt like mush.

so anyhow, next, i guess, to figure out how i need to write this publisher implementation for the single-listener design i have come up with. and then, with that, i think i can call the HTTP API an MVP. there is other methods i could optionally add, but i just want to put it to bed with a feature complete - compared to the websocket API, set of methods. import and export are orthogonal to this, but are essential features for administration. the event publish, filter search and subscription mechanisms make basic nip-01 feature parity.

i kinda promised myself that by the end of this month i would be starting on the job hunt for real. so, hopefully i can get this subscription system done in the next three days. preferably today, but with a mushy brain i'm probably not gonna get there that soon.

so, i think i have found it. it's a buffer being reused in the client library, this is why it didn't appear before, it's been some time since i was using the websocket client library.

the fix was simple: just stop reusing the buffer, make a new one for every received message. the end.

it was particularly affecting follow lists. it was also causing a race condition because the buffer was being used concurrently. with this one tiny change, allocating a new buffer for each message, the race condition has gone away and so has the mangled tags.