<unnamed>

Public Key

npub1wh2hpen9ud23de6rm2t2d0gm8f7j5vck4zy7p7yw3lpzdyzz3husm2rdcf

Profile Code

nprofile1qqs8t4tsuej7x4gkuapa494xh5dn5lf2xvt23z0qlz8gls3xjppgm7gpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qqfrrz7

Publishing to

relay.mostr.pub

Last Notes

2025-11-27 07:22:13 GMT

- reply

that would require changing specs of kinds 0, 1, 20 etc.
"images should be only loaded from HTTP servers that return Content-Length HTTP header or specify Content-Length in imeta metadata"

2025-11-27 06:41:18 GMT

- reply

make Content-Length mandatory in spec. make clients ignore images that do not follow spec.

2025-11-27 06:17:52 GMT

32B llm model is now better than human average on one of the most difficult benchmarks. i think we are starting go to the exponential growth territory. despite previously commercial models being able to do the same, commercial models are not scalable. when reasonable sized open source models beat human capabilities we are starting to see scalable exponential growth. these models can be deployed in millions.
https://redlib.privadency.com/r/LocalLLaMA/comments/1p7d97m/opensource_just_beat_humans_at_arcagi_716_for_002/

2025-11-27 05:52:17 GMT

#dev, why are you scrollbar racist?

2025-11-27 05:46:57 GMT

- reply

although in reality, you load profile picture once, you can save whatever quality variant of it in local storage.
if someone wants to waste your bandwidth, they can post single post with 100x 500 MB gifs anyway.
you could add soft recommendations of picture sizes in spec for all images, as well as bandwidth saving setting which prevents automatic loading of images past specified size.
also it could still be beneficial to have two image qualities for all image posts. often its not necessary to load 8K image in feed, but photographer may still want to publish original high quality image.

2025-11-27 05:40:13 GMT

- reply

its possible to specify in kind 0 spec that picture value cannot point to image larger than specific size. its also possible to change spec to specify two images: small and full size.

2025-11-27 05:33:43 GMT

- reply

first they make their html pages so heavy (on the client side, because we dont use php server side processing anymore), then they cant serve 5 MB html blob pages anymore after 5 responses to same ip. but it seems they are so broke 25 MB traffic per ip is definitely killing big tech servers.

2025-11-27 05:31:15 GMT

- reply

have you seen that cool unicorn rate throttling github html page requests after 5 page loads...
big tech is killing itself intentionally

2025-11-26 18:07:27 GMT

- reply

probably flac and opus

2025-11-26 17:11:24 GMT

- reply

nsec simply works, but some popular clients decide not to implement simplest possible #nostr login.
its as secure as anything else when its http://localhost

2025-11-17 13:03:45 GMT

most of #nostr is #ethereum. its a #pos model, which is a trust model equal to #wot model. both are social trust models, rather than computational trust models.
social trust model is a model where network peers must trust existing peers to provide valid network state, whereas computational trust model is where only computation needs to be trusted. latter is called #pow model.

2025-10-30 15:33:27 GMT

- reply

if you want nostr based, fork plebs.app
https://plebs.app/
https://github.com/Spl0itable/plebs-app
it probably has some features you dont like but its relatively easy to adjust.
if you want fedi based, there is peertube

2025-10-30 09:28:47 GMT

- reply

i mean. this is not really the case.
its not necessary that the past chain is vulnerable to do a double spend attack. you can rewrite the chain after accepted transaction.
all you need is enough fake blocks for someone to accept transaction as complete. 10 blocks? 30 blocks?

2025-10-30 09:20:39 GMT

- reply

thats possible if nodes still validate the pow chain. but this would mean the security diminishes as the pos chain grows longer

2025-10-25 10:04:40 GMT

ask this from your llm. it will output only bullshit.
proof of stake is based on circular reasoning: the participants with most stake validate network, however those who validate network decide who have the most stake.
how does ethereum node decide who are the validators?