Opinion:
Any article that starts with "Opinion:" is not journalism, its a blog.
That's why flake is the bomb diggity
Its Rubin time and I'm gonna Rubin all over you
Read the comments. I noticed that mistake after the edit timeout window.
What is the future anyway? nostr:note1xz02fldlltlp7cgv5n5n73x3jlfvnw2hmqn7lxzttq58n26hd60qk9qlwe
The pocket computer is a useful tool, but its usefulness has been subverted with addictive distractions and psychological manipulation. Sometimes that psychological manipulation is targeted ads, but its also what you see and don't see in the normal content. The creepy constant tracking and analytics merely serve to that end.
I have a pocket computer that has been defanged of these things and yet I decided to buy a Nokia for days when I want to test exactly how free I am.
Its like I'm living in the past and the future at the same time lmao
Can't speak for yonle, but very often its because an attacker can see the vulnerability and will become frustrated that people aren't protecting themselves.
Sometimes the best way to get someone to learn how to protect themselves is to attack them. At least you can let up if they aren't handling it very well
Okay got a quick read. I would say kinda? Its a store and forward system, but I think its important to point out that not building DTN protocols from scratch here, just the rules around naming conventions for a userbase I have in mind.
https://en.m.wikipedia.org/wiki/Delay-tolerant_networking
https://www.nasa.gov/technology/space-comms/delay-disruption-tolerant-networking-overview/
Would you be interested in learning more?
So these posts are my thought process behind why I started going in this direction
https://stacker.news/items/330735/r/nerd2ninja
This is a video series on NASA's HDTN which they use for satellite communication where the next hop won't show up until certain orbital paths align
https://www.youtube.com/playlist?list=PLVPcuBdh7z6cmKgVHniVXneiEztHSiZzL
They changed the name from ION to HDTN. Gave me trouble trying to find the most up to date software.
This is another DTN implementation I've been playing with. Thinking about the different tradeoffs of the implementations so I can think about the most effective real world use.
And yeah when I'm done I'm thinking of setting up a post office address to receive DTN packets and forward (for a limited time) not because that's too useful, but just because it might get people interested in it and maybe one of those people ends up supporting a country with ID requirements to use the internet and/or censorship or power outages or what have you.
Okay got a quick read. I would say kinda? Its a store and forward system, but I think its important to point out that not building DTN protocols from scratch here, just the rules around naming conventions for a userbase I have in mind.
https://en.m.wikipedia.org/wiki/Delay-tolerant_networking
https://www.nasa.gov/technology/space-comms/delay-disruption-tolerant-networking-overview/
Would you be interested in learning more?
All these underground protocols I keep digging up. Hold on, going down a rabbit hole real quick
Thinking about Delay Tolerant Networking.
I'm thinking there should be two types.
Global addresses for long haul routing
"Local" as in region wide addresses.
I'm thinking it may be good to have a onion style packet routing in that a packet addressed to a region address would exist encrypted inside the globally addressed packet.
You could even have a packet encrypted inside of that one which goes to an even smaller region address.
But how would you deconflict global address names between random DTN router operators who might want the same name?
I believe the answer is by social construct. Just agree that all global names must be dtn://hemisphere-timezone/ and reject names that don't fit that scheme. If two nodes want the same name within that area, they can create region addresses for each other within their contact plans. This could mean sharing the same decryption key for that region or it could mean including two different embedded packets depending on which node receives the packet.
A destination node should know their full path to global which makes their full destination DTN address so that this fluidity in addressing isn't problematic. Additionally it stands to reason that if a node moves between regions it will have multiple DTN addresses. Which might mean multiple independent packets being sent to the same intended endpoint. This can be useful for confusing an interceptor from fully understanding where a packet is going without confusing routers.
Oh and if you're thinking "man these sound like some big packets" that's because they can be. Sure a long haul through UHF, Ham radio or any radio band really won't like it very much, but physical delivery methods with SD cards such as post office mail, drone delivery (farry net), pigeon carrier, or any of those other large packet size, but potentially long delivery time methods should be perfectly happy with it.
I managed to figure that out lol. I've posted some LNHance information on stacker news since I posted this question to you.
Ah, that's the name of the app. First part of the video went a bit quicker than I was keeping up with
Culture shock? Lol.
Think of your phone not as a phone at all, but rather a desktop computer. A pocket computer.
Side loading? That's just called installing a program.
Welcome to Android OS.
Can't wait to see you trying out an Android Open Source Project fork that doesn't have google play installed.
Please dont zap this post. This is written by me (Vic), not the real Vitor Pamplona. The intention was to demonstrate how easily an impersonation can be performed by simply setting the name and avatar to the target. People following the impersonator can be tricked into thinking they are seeing a message from the impersonatee.
Solutions to this aren't easy, and may come in layers.
1. I really would like to see Nostr clients do what Phone and Email clients have done, and add some kind of support akin to contact list and address books where the owner of the book (you using the client) is defining labels, attributes, names etc, and not solely relying on what the owner of the discrete identifier (phone number, email address, pubkey) is publishing as their name
2. The historical check that nostr:npub1lrnvvs6z78s9yjqxxr38uyqkmn34lsaxznnqgd877j4z2qej3j5s09qnw5 referenced.
These or others are implemented in various game clients (e.g. Steam) and it's worked well through the years. Client side labels would go a long way for personal context as well.
I love this community that just social engineers each other for fun lmao.
BTW, my client didn't update your information so I still know its you. I was going to ask what app you've made that you wanted to implement those features into.
The blue check he's talking about
&f=1&nofb=1&ipt=18ea0d711a6c43ce23a6ab75f251bfaab642489c1416901b4c026a0d8b2b5fc2&ipo=images
"Why can't I pay LN invoices from it"
And of course on a technical level you could, but the UX for that usecase is intentionally shit. Its designed for you to withdraw to self custody. Its two button clicks then copy and paste invoice (or lnurl-withdraw) it doesn't show you a dollar balance for your account and it has a max deposit amount of 250k SATs which they plan to reduce over time until a complete transition to fully self custodial can be made.
To keep this on the topic of culture building, what's the transition plan to fully self custodial look like for e-cash applications? What UX decisions are made to discourage payments for goods and services and to only e-cash in platform until withdrawn?
SN makes a point of making sure their in store credit is only used as in store credit (or self custodially withdrawn) and NOT used as a wallet.
The culture you build around your applications can do more than the purely technical realities around it.
So I found this website (via junkmail please judge me) called "next-door" its sort of Twitter/Facebook style posts but from everyone with the radius of the zip code you set.
It has a marketplace section (so this is specifically a local marketplace) it has local business pages it has a concept of a "help map" so if you can help during winter storms or other emergencies you can put yourself on that map and it has pages for local meetup groups.
The only problem with it, is its not a nostr app! Nostr apps are very Twitter like right now and this platform is much closer to that Facebook feel.
I think someone should make a nostr app based around the idea next-door is going for which may involve extending the protocol to include zip codes so that users only receive posts close to their zip code. I believe this will also be good for Bitcoin circular economy growth. nostr:note1gcdfpa4z80c2c65dcn0ct45amlvkufqqtuectcyv0q8r9rfmcclstyn7d5
