If you see being a #bitcoin maxi as something dumb, and think a layer 1 should be bigger and faster, then you are dumb. Maybe take a few hours or days and think about it. Try running a node.

Bitcoin is the right core layer, we build on top of it. I explained this with great detail in other places before, and many others have explained it as well. So I'm not gonna explain it again here again.

Go learn yourself.

Study #bitcoin.

Learn what money is, and beyond.

Also try to understand systems, how they work and connected. Try to build one yourself.

also the real evil is censored before everyone sees the demons

world didn't become more good. it just we become bigger, louder, noisier, that it has become easier for demons to hide themselves and their victims.

didn't know about blossom before. looks promising.

i think where blossom is strong is its easier to implement in few hours. and more lightweight. more cdn like.

ipfs a bit more complex, but good side is, well-known gateways share content between each-other fast without something like /mirror.

if the hash were compatible/convertable it would have been great. then you can ask for the content on both blossom cdns and ipfs gateways. also blossom cdns can also seed the content on ipfs. and etc.

I mean what I said was just getting content from well connected gateways anyway, or uploading to one, like nostr client providers can have their own default gateways and etc. i wasnt talking about p2p ipfs experience.

anyway I checked blossom, (first time hearing about it).

seems similar to what i was thinking with ipfs.

but instead its a cdn protocol basically, i think. didnt deep dive in it yet.

so i believe its like a normal cdn but hash based and has a known format, endpoints. so you can extract the hash (like i said in ipfs). and then check other blossom compatible cdns.

and of course user can give list of blossom cdns on their profile as well.

tbh blossom looks more lightweight and easier to implement for already existing cdn solutions. i see no problems with it.

seems like a more lightweight solution. i liked it.

i still see no problem with supporting both or more. similarly you can share a media with a https ipfs gateway URL, so it works everywhere.

and then while viewing extract the hash and check multiple other gateways with that hash as well using HEAD method.

which would also make those gateways search for the content. distributing the GET traffic more later when more users ask for same thing.

but yeah blossom looks nice, maybe better.

if i make my own client for nostr, i will not count likes. just show profile pictures of people who reacted with ❤️. maybe at the top of replies.

zapping will be the main counter.

oops didn't realize i replied to the man himself.

i just typed "nostr ipfs" in the search, to find a discussion, and replied.

why do i keep zapping myself?

trying something using multiple clients, trying to understand how things work.

there is a reddit and 4chan like social media protocol on ipfs, its a bit more wild west. it uses pubsubs.

but its nothing like nostr, nostr is more profile based, and a lot more closer to regular social media. just better in general.

and ipfs problematic when you share something alone from your own node, it takes a long while for others to discover it. but sometimes it also works fast, just like that.

i think one problem with nostr right now is all media is just http links to a cdn.

they are not distributed, and link have nothing to do with the content, makes it impossible to verify. so i think sharing a hash instead of some random centralized id makes more sense. and we already have ipfs hash and uri. so if we shared ipfs uri instead of http url i think it would just work.

like relay lists, we can also have ipfs api and gateway lists. clients can ask all of the gateways for the content until finding it at one. ipfs gateways allow HEAD requests, so you can know if the content exists and its size before fetching it.

you can easily backup/pin your own content on another gateway you pay for as well if you want to.

main thing is its hash based, and distributed.

right now if i post a media on primal, they will host it via their cdn, and all of the other nostr clients will fetch it from a url to that cdn. cdn can censor, remove the content, and in the future even cdn itself can shutdown. there is no way to access that content other than that cdn. but and ipfs uri is hash based, so anyone can host if for you. if the content is lost, you can verify it again once you find it, etc. primal can just host an ipfs gateway instead of a regular cdn.

i know not many clients support ipfs, or have a list of ipfs gateways to use. but what you can do is share an a gateway https url, and anyone can still parse, it and say that "its an ipfs url".

ipfs url formats are known, it can be in bafy subdomain type or bafy and Qm type with /ipfs/ pathname prefixes. you can extract the hash from there and try it on multiple gateways. and clients that doesn't support ipfs would still work, because its basically a https url to an ipfs gateway.

i plan on hosting one in the future for nostr, with my own client.

- Fedora Silverblue (or its iterations) will be the OS of everyone, because its just better and simpler.

- Nostr is going to be the social media protocol everyone uses, because its just better and simpler.

- Bitcoin and Lightning will be the wallet and money of everyone, because its just better and simpler.

All natural.

i get stressed, when im not at least 99% in bitcoin

think about it, if you give everyone free money "equally" meaning some amount to everyone, if you give them enough you can make them all poor, because you made ratio between all of them to close to 1.

when a place has lot's of cafes and people walking meetings outside for nothing, you know that place is filled with shallow, unproductive, mindless people.

it would be cool.

i would watch it, they are just chilling for 20 seasons and getting old

what if hank was chill, and cool with it, in breaking bad.

especially after walt quit

anything that is not a bitcoin L2 or not LN, is a scam

TypeScript type system have great potential. One day when I have time, and my other projects are not on the way. I will be making my own systems programming language that gets inspiration from TypeScript type system, scope and ecs based memory safety, and C# syntax (mostly using keywords instead of weird operators).

think about vacuum robots and all those "smart" home things.

imagine they are not connected to the cloud, but broadcasting and taking encrypted commands using nostr.

idc about how you write your code, or if you pay someone else to code it for you, or use ai.

i will just review it and decide what to do with you.

people be like:

"oh i dont know something, so instead of learning, im just gonna live in my illusion"