Last Notes
I see no faults in that plan 😂
Imagine believing in democracy
#nevent1q…ecn0
Perhaps https://nostrvpn.org/
WORD5 #752 3/6* (Hard Mode)
⬛🟪🟧🟧🟧
🟪🟪🟧🟧🟧
🟪🟪🟪🟪🟪
https://otherstuff.ai/word5/
This has been my theory as well.
Thumbs up for taking extra care of onboarding 👍
https://blossom.ditto.pub/c38727fd98ed9002fe214c8b86578adab369933110cf1b5c8e70f93835f98ab7.gif
You say that, but people will beg for gifts, bits or imaginary currency from other platforms.
I don’t think zaps are a problem, but we maybe lack a proper onramp and stop calling it bitcoin.
You know the fossil industry is behind this pointless push for hydrogen
Try integrating with crowdin, they have a free tier for open source.
I agree we should probably let it rest for now, but as for the merge miners being invested in the security of rootstock, it seems like they don't have to lose all that much if something goes awry with rootstock as they don't incur any real marginal cost from mining it and the payments they get are I believe also not all that significant. In any event, this has been an interesting discussion and it's entirely possible that my views on this will change as I learn more about it.
Also on the scalability: that makes packs future proofed. Right now the few clients that do support custom emojis display them at line height, what happens when a client decides to make them display bigger? Some people have just assumed they would always be tiny so may have made their bitmaps in accordance to that.
Honestly JPEG XL is the saner option for bitmaps going forward, since it supports progressive decoding you can download a file partially, with just enough resolution, but that’s beyond the point.
1. If we play the holier than thou card we get nowhere. Nostr (today) doesn’t work without the permission of many gatekeepers, and yet we not only seem to be ok with that (for the reasons of pragmatism) but we also made sure to spec out some ICANN DNS cocksucking with NIP-05 and stuff. As for your server being a middleman, that assumes the implementation would be server sided, that wouldn’t be an issue if the tool ran on the client side
2. That is the same argument lobbyists use to push for censorship of applications that “could be used for piracy”. Also nobody is concerned about IP theft over memes
3. That is why I suggest that client devs add support for TGS. It is a based, vector animation format built around lottie. I can not stress enough how little bandwidth it uses, how smooth it makes animations and how high quality they look
As for using animated webp, any bitmap based animation format will look like garbage and/or waste bandwidth in comparison. TGS is the only format that is widespread enough that artists actually care about and have made content for.
I guess we could reinvent the wheel and create a vector based “NEF” (nostr emoji format), but that would be just NIHS (Not Invented Here Syndrome).
Wisp safety filters blocked the quoted note
https://24242.io/af08222ec39fd101bf9214c8e730116a40a9035848bec12c7816b9128bafb54b.png
What fucking timezone is #word5 in??
WORD5 #751 4/6* (Hard Mode)
⬛🟧🟧⬛🟪
🟧🟪⬛⬛🟪
⬛🟪⬛🟧🟪
🟪🟪🟪🟪🟪
https://otherstuff.ai/word5/
Se vc olhar no nip-05 daquele npub vai ver que termina em mastodon-social.mostr.pub, daí é garantido que a nota não vai chegar até ele.
Mas sendo outro domínio é provável que a mensagem chegue.
Existem várias instâncias do mastodon, a maioria consegue comunicar de boa com a gente, é que algumas como a mastodon.social baniram a instância onde a bridge roda.
Bots are multiplying faster than manual blocking is able to keep up. Also so much random bullshit gets posted every second on the major relays…
Acho que o mastodon.social não recebe os posts da ponte
Merge mining also isn’t a new concept nor is it tied specifically to sidechains. Many altcoins and shitcoins get a huge hashrate from merge mining because it is literally extra, free money for the same effort, it doesn’t really matter what the actual market value of the merged coin is.
If RBTC traded at 50 cents while Bitcoin is at 80k, this would presumably mean that people think there's something seriously wrong with the bridge. The value of RBTC just seems to reflect people's view of the integrity of the pegging mechanism and the trustworthiness of the pegnatories. By contrast, the value of Bitcoin or Ethereum reflects people's view of the security, usefulness and future of the chain itself. It feels like, in the case of Bitcoin and Ethereum there's more overlap between those who are defending these chains and those who have their economic interests bound up in them, and there's less of a single point of failure, but I guess I'll need to look into this more. Also it's of course perfectly fair to predict that things will get better in the future with BitVM, but the prediction doesn't substitute for what it presently is.
https://www.zonaautonoma.org/bludit/vigilancia-financiera-monero-sin-lugar-en-el-ecosistema-financiero-tradicional
Monero camino al no-kyc permanente.!!!
https://image.nostr.build/24463cff188d3f3344cb79717cf5899127b9169c03ea797e6f376f3f8a159e73.jpg
Se estiver procurando outros brasileiros, tente a hashtag #bostil
Moaning, if you have time, check out my very serious client proposal #nevent1q…ls9u
Another reason to adopt TGS: since the vector file is so small, you could probably get away with embedding the stickers into the pack event instead of relying on a blossom server to serve the media.
Also pictured: ditto (like many clients) not verifying the checksum of images and displaying nostr.build 404 placeholders
https://blossom.ditto.pub/a35986687a7a7ed286877e2165c612bba120f43cd4aa7fcbc58157af8a692460.jpg
#nevent1q…x38p
Same, but the sticker format + sheer number of existing packs is something worth stealing IMO
https://blossom.ditto.pub/39a1e0269addf6f89dcbf14f2b3c5cea7c62929fb4debc86e091df7fbc55e4e0.gif
I have two very serious proposals for nostr client devs:
1. Add support for TGS (telegram sticker format). Because it is a widespread, animated, vector format
2. Give us some tool to import Telegram sticker packs into nostr by their URL (i.e. https://t.me/addstickers/honka_animated)
#asknostr
I think I've never met a plumber. I wonder if they are nice people.
Google Maps is the reason I got a smartphone 14 years ago. I saw it on a friend's phone and thought oh it would be useful to have that. As far as I know, it's the only distinctive product Google ever made.
With rootstock, I guess the main discomfort really does come from the fact that its funding isn't endogenous, its being pegged to Bitcoin. Looking into this a bit further, it seems like the pegnatories aren't anonymous happily, but it's still unclear why one would want to trust a handful of companies with peg-outs. This feature makes it seem rather fragile.
Unable to fetch the quoted note.
I suppose they have sent a delete request and relays honored it, which is great.
However, how can a client distinguish between a deleted note and a missing note?
Ja pode começar a mandar “oi sumido” pros monerobros…
But the bot is hotlinking the reddit url instead of posting from the blossom mirror
I mean the “unstable” name is almost misleading, it is close to the stability of a rolling release distro.
But the point I wanted to make is that you can always cherry pick one very specific thing from unstable or some other alternative nixpkgs repository and bolt on top of a system based on a stable, tagged release.
Suppose there’s this PR with a newly packaged piece of software, you can add that branch/repo as an second nixpkgs input (if you are using flakes) or channel and use overlays to “integrate” the thing you are looking for, without conflicting with anything else you have on your system.
Reddit mods are retarded.
What if the bot tried downloading the image? It could discard the post when that fails and/or re-upload it to blossom and link that instead.
Somehow I missed this part of the thread.
> FIPS was interesting to me because it at least claimed to be for replacing the current internet (by which I mean it is supposed to work on top of physical links)
And so does Yggdrasil and CJDNS before it. The idea is to replace BGP entirely.
> although now I see people treating it just as an overlay network like Tor, which is sad.
That’s perhaps because of the aggressive approach to bootstrapping taken by the FIPS project.
Conversely, automated clearnet peering is highly frowned upon in both Yggdrasil and cjdns, because that can indeed masquerade protocol inefficiencies: instead you are encouraged to find the closest public peer and set only your node closest to your internet gateway to peer with that, maybe have a second node for redundancy.
It is made expressly clear that an internet peering is analogous to a virtual ethernet cable which exists solely for the purposes of bootstrapping the network globally.
But on the other hand, that makes the process of joining the network a bit more involved, if you don’t know what you are getting into.
> As far as I know all the mesh networks in the world are sadly much less ambitious than I want: they're all happy to just be a local thing. And in some cases they clearly state that their routing algorithms don't scale at all (they're either based on a centralized supernode, or nodes flooding the network with packets, or on everybody keeping a routing table of the entire network locally).
This may apply to cjdns to a certain degree, given that it is source routed and the routing table is distributed via DHT, but it is far from true for both Yggdrasil and FIPS. You may find this post interesting: https://yggdrasil-network.github.io/2018/07/17/world-tree.html
> Projects like Meshtastic are just a stupid psyop.
I agree. Feels designed to give ham operators hardons, requires specialized hardware and software needs to be tailor made, ignoring existing infrastructure entirely.
> I think my method above works, and it is not magic because it has this important tradeoff: you can't route only with keys, i.e. your address can't be just your key like all these other projects do
You have basically described the coordinates system Yggdrasil (and FIPS I presume) uses for routing. No single node needs to keep the whole tree in memory, you only need to care about your immediate peers. You forward the packet to whoever of your peers seems to be closer in the coordinates to the destination, so routes are not guaranteed to be perfectly optimal on the first packet, but it is guaranteed not to get lost in routing loops or other bullshit.
> addresses would be much bigger than even IPv6 can support
Here’s the trick cjdns and Yggdrasil do: they take the public key and trim it so the IPv6 address is composed of the first ~128 bits of entropy from the public key, which means collisions are unlikely but not impossible (also you can brute force stronger keys if you want). FIPS does something else, it seems like it uses the npub.fips DNS query to lookup the destination, so maybe IPv6 collision is not an issue there. Still, that seems like a small price to pay for backwards compatibility.
Sure, but what I really wanted to know is if Amethyst is mutating a user’s mute list in the background.
That sounds like redundant bloat, regardless of the cries of censorship.
I don’t think you understand what “let it crash” means.
@npub1rzg…kxve have you considered mirroring the images from these posts into blossom? Seems like half of the posts the nostr bot is forwarding are deleted.
If you want to be even more bleeding edge, you can import the latest kernel from nixos-unstable.
And if for whatever reason you feel like you need to have an alternative kernel/system configuration readily available, there’s specializations.
Yeah I don’t think I have the means to verify that. My computer is dead and my phone is a useless piece of Apple.
As opposed to the other clowns, who only break shit without crying censorship 🤣
That is not how Web of Trust works. And it is a pointless waste of resources and an abuse of mute lists to automatically fill them with random bullshit.
@npub1gcx…nj5z does Amethyst behave like he described?