@ 5a261a61:2ebd4480

Let’s be real—sticking to *anything* for 90 days is like trying to herd cats on espresso. You start strong, then **life happens**: kids, chores, or that *one* glass of wine that makes you forget foot rubs (#relatable). But here’s the thing: 90-day challenges aren’t about perfection. They’re about bribing your lizard brain with rewards and scaring it straight with punishments. ## **The Game Plan** First, pick a thing—something that makes you feel like a devoted servant or a slightly frazzled superhero. Daily foot care? Chores with a side of #FLR flair? Cool. Now, break it into chunks: 30 days (survival mode), 60 days (grind phase), and 90 days (victory lap). Keeping up something for so long is no joke. That's why you need those little checkpoints along the way. Each milestone should feel special—30 days deserves celebration, 60 days something more meaningful, and 90 days? That's your victory dance moment. Reality check: some days will suck, and you'll want to skip. **That's where having everything planned out helps.** When your brain is foggy and you're tired, you don't want to be negotiating with yourself about what counts and what doesn't. The hardest part isn't even doing the thing—it's remembering to do it every single day, until it feels wrong NOT to do it. ## **Why It (Maybe) Works** Three months is long enough for habits to stick, short enough to see the finish line. Plus, tying it to power exchange? Genius. Every foot rub or denied cum becomes a ritual, proof you're leveling up as a sub/human/slightly-messy adult. And let's be honest—nothing fuels devotion like a mix of structure, desperation, and the occasional humiliating punishment. ## **Current run** My current challenge is to get my wife/godess/object of my insatiable kinky thoughts/partner feet massaged with special cream. It's for making evyrthing soft, help nails and yadayadayada. Basically preping her feet for more instensive worshiping. She doesn't know my hidden agenda and I am not sure if I would really be into it, since I am more into being her devout toy than having foot fetish, but I think it will be all the same if I put myself juuust right. So for my rewards I have planned these? - **30 days**: Tiny dopamine hit. *(making little photoset of Her feet playing with my hardon… for science.)* - **60 days**: Mid-tier flex. *(cleaning mushed banana split off Her toes tongue only)* - **90 days**: Go nuclear. *(a tiny foot spa whirpool because She deserves it, damn it :D and it will create more opportunities for... you know )* As for the hhip part of the sugar duo... It was easy having one for my shaving rutine, but here? Not sure and it's bad that I ave started challenge without having them prepared... May be that warrant more punishment? ## **TL;DR** 90-day challenges are the BDSM of self-improvement: **consensual, slightly painful, and weirdly addictive.** Fail? Reset, adapt, try again. Win? Congrats, you’re now 10% more disciplined and 100% more bumptious on Nostr. #90days #FLR #LostCauseButStillTrying #femdom

@ 5a261a61:2ebd4480

The idea of the **Bean Bag Game** is quite ingenious. I read about it on a BDSM-positive blog. Here’s how it works: 1. **Setup**: - Take a small cloth bag and add **10 white beans** (rewards/pleasure) and **10 black beans** (punishment/discomfort). - When it’s time to play, draw **two beans**: - **First bean** (the *tone*): Determines if the activity will be **pleasant** (white) or **uncomfortable** (black). - **Second bean** (the *task*): Decides whether you get a **reward** (white) or **punishment** (black). --- ### **Combination Interpretations**: - **Black + Black**\ *"No fun, just work."* - Boring/challenging tasks you’d normally postpone: **window cleaning**, **scrubbing bathroom tiles**, **polishing shoes**. - Could also mean **no playtime** (e.g., "Go straight to bed"). Pure duty – no pleasure, only discipline. - **White + Black**\ *"Work with a twist."* - Punishment or chores, but with a *kinky edge*: - Clean the bathroom **wearing a vibrating butt plug**. - Wash dishes **with nipple clamps**; add a clothespin to your body for every minute over the time limit. - Still **no orgasms** – the black bean ensures denial. - **Black + White**\ *"Pleasure with pain (or humiliation)."* - Mix stimulation and discomfort: - Ride a dildo **with weighted nipple clamps**. - Give a "lap dance" to a teddy bear with a strapon. - Chat online as a "perfect plaything" for others **without touching yourself**. - Again, **no orgasms** – the black bean overrules the white. - **White + White**\ *"Lucky draw… but denial is optional."* - Freedom to indulge, though I often choose **self-denial** anyway. Examples: - Edge for 30 minutes, then ask permission to climax (50% chance). - Use toys freely, but end the session frustrated. --- ### **The Dynamic Ratio Twist**: - The starting **10:10 ratio isn’t fixed**. Adjust it based on behavior: - **Good deeds?** Swap a black bean for a white one. - **Mistakes?** Replace a white bean with a black one. - Single beans can also decide smaller stakes, like: - *"Should this edge turn into a ruined orgasm?"* - *"Do I deserve dessert tonight?"* --- ### **Why It Works**: - **Control**: The beans dictate your fate, but you tweak the odds through obedience. - **Flexibility**: Use pairs for major tasks, single beans for quick decisions. - **Psychological tease**: Even "white + white" can mean denial – because *you* choose the rules.

@ 5a261a61:2ebd4480

It was late afternoon, and Tom hoped the lunchtime crowd had already returned to work while the after-school rush was still thin. A quick glance under the stalls as he strode through the mall’s large restroom confirmed he was alone. He hurried into the last stall, checked his watch—two minutes to go. What could go wrong? He unzipped his backpack and tore a hole in the small paper package inside. A few strips of skimpy fabric tumbled into his hand, along with a note: WEAR ME. A chill ran down his spine. It was the first handwritten note from her. That alone was enough to unnerve him, but what truly sent shivers through his body was the clothing itself: a black-lace G-string, a flat-chest bra, and purple-black striped knee socks. Beep. His watch jolted him from his trance. Shit. It's 1:00 PM already. He stripped quickly, pausing only to listen for any signs of company. Satisfied with the silence, he dressed, obeying her command dutifully, despite the trembling in his hands. When he was done, he unlocked his phone and took a selfie—neck down, body framed just enough to show his obedience, the stall’s background confirming where he was. The G-string barely contained him. The thin pouch was already failing as his arousal grew. Standing there, dressed like a slut, waiting for the telltale three dots of her typing status—it only made him harder. Maybe, if he completed this task perfectly, she would deem him worthy of the cage. Finally. His phone vibrated with her response: "Good slut. Bad angle. Try harder." He snapped another picture. Then another. His desire to please her overrode everything else. He tried to be more "artistic," offering different angles, better framing, careful lighting. He submitted each for her approval. Her only response: a frowning emoji. "It looks like a bitch, acts like a bitch, but it has something no bitch should have. Disappointed." He scanned the images again. She had a point. But he was so unbearably horny. Five days of orgasm denial had left him painfully sensitive. Even his nipples strained against the sheer fabric of the bra. "Are you going to fix it, or should I consider this your final submission?" His mind raced. Then—an idea. Slipping off his shoe, he unthreaded the lace and, through a mixture of pain and precision, crafted a tight, effective tucking shibari. He took a photo of his bound, darkening flesh and sent it. "Would that be enough?" A reply came instantly: a grinning emoji, followed by a meme of Jeff Goldblum captioned, "Life Finds a Way"—edited to say, "Bitch Finds a Way." Then another message: "Hurry up, or I won’t need a cage to keep you soft forever, and there is no fun in that." "You have two minutes. No mistakes this time." His chest tightened. Sometimes, he wished he could fall at her feet and kiss her toes for everything she did to him. His fantasies mercifully ignored the fact that he didn't even know her shoe size. Or what colour skin his tongue should be worshipping. Shame fueled his arousal as he continued his photoshoot. He posed, exposing his chest, arching his back, spreading his legs to make himself more accessible. The phone holder with suction-cup he’d brought made certain angles easy. Finally, he sat on the closed toilet, knees hooked over his arms, presenting himself as thoroughly as possible. The two-minute deadline might have passed, but he didn’t notice. He selected the best shot from each pose and sent them one by one. The last one nearly didn’t make the cut—his shibari work was visible—but he’d unconsciously parted his lips, doll-like, as if ready to be fucked. He sent it. Her response was immediate. "Good girl." His stomach twisted with pride. "Get rid of the shibari. Keep the bitch uniform. Get dressed and text me when you leave the stall." Was that all? Disappointment prickled at him, but she sounded almost content. That was good… right? His train of thought derailed as blood rushed back into his tortured cock, sending a wave of sharp pain through his core. It took him a moment to breathe through it, to compose himself enough to leave. The G-string left him utterly exposed. Every step sent shivers up his spine as his pants caressed his bare ass. Outside, he sent the message. Her response came instantly: "Go to the photo kiosk and wait." Wait? Confused, but knowing better than to question her, he obeyed. "Pick up order XYZ." Oh no. Dread churned in his gut as he typed in the pickup code. Bzzz. The printer spat out five photos of him. At least his face was covered—emoji stickers distorted his expressions—but still. Another message: "Buy a disposable SIM, write the number on the back of the photos, and distribute them. Then, you can go home. But keep the bitch uniform on for the night. I’ll check in on you in the morning. Have fun, my sweet boy." Tom exhaled shakily. It was going to be a long night.

@ a39d19ec:3d88f61e

This week's functional 3d print is the "Dino Clip".  ## Dino Clip I printed it some years ago for my son, so he would have his own clip for cereal bags. Now it is used to hold a bag of dog food close. The design by "Sneaks" is a so called "print in place". This means that the whole clip with moving parts is printed in one part, without the need for assembly after the print.  The clip is very strong, and I would print it again if I need a "heavy duty" clip for more rigid or big bags. Link to the file at [Printables](https://www.printables.com/model/64493-dino-clip-mechanical-cam-chip-clip-print-in-place)

@ c4f5e7a7:8856cac7

Best viewed on [Habla](https://habla.news/u/nathan@btcmap.org/2uBWmmKOqd-09vQVMH8X0), [YakiHonne](nostr:naddr1qvzqqqr4gupzp384u7n44r8rdq74988lqcmggww998jjg0rtzfd6dpufrxy9djk8qq2nya2z2akk6j60w9jz6vpeweg4vn2g8pvrq6c73gs) or [Highlighter](nostr:naddr1qvzqqqr4gupzp384u7n44r8rdq74988lqcmggww998jjg0rtzfd6dpufrxy9djk8qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qq2nya2z2akk6j60w9jz6vpeweg4vn2g8pvrqzwws2x). # TL;DR This article explores the links between public, community-driven data sources (such as [OpenStreetMap](https://www.openstreetmap.org)) and private, cryptographically-owned data found on networks such as [Nostr](https://nostr.org/). The following concepts are explored: 1. **Attestations**: Users signalling to their social graph that they believe something to be true by publishing Attestations. These social proofs act as a decentralised verification system that leverages your [web-of-trust](https://en.wikipedia.org/wiki/Web_of_trust). 2. **Proof of Place**: An oracle-based system where physical letters are sent to real-world locations, confirming the corresponding digital ownership via cryptographic proofs. This binds physical locations in [meatspace](https://en.wiktionary.org/wiki/meatspace) with their digital representations in the Nostrverse. 3. **Check-ins**: Foursquare-style check-ins that can be verified using attestations from place owners, ensuring authenticity. This approach uses web-of-trust to validate check-ins and location ownership over time. The goal is to leverage cryptographic ownership where necessary while preserving the open, collaborative nature of public data systems. [Open Data](https://en.wikipedia.org/wiki/Open_data) in a public commons has a place and should not be thrown out with the Web 2.0 bathwater. # Cognitive Dissonance Ever since discovering [Nostr](https://nostr.org/) in August of 2022 I've been grappling with how [BTC Map](https://btcmap.org/) \- a project that helps bitcoiners find places to spend sats \- should most appropriately use this new protocol. I am assuming, dear reader, that you are somewhat familiar with Nostr \- a relatively new protocol for decentralised identity and communication. If you don’t know your nsec from your npub, please take some time to read these excellent posts: [Nostr is Identity for the Internet](https://hivemind.vc/identity/) and [The Power of Nostr](https://www.lynalden.com/the-power-of-nostr/) by [@max](nostr:npub18lzls4f6h46n43revlzvg6x06z8geww7uudhncfdttdtypduqnfsagugm3) and [@lyn](nostr:npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a), respectively. Nostr is so much more than a short-form social media replacement. The social features (check-ins, reviews, etc.) that Nostr unlocks for BTC Map are clear and exciting \- all your silos are indeed broken \- however, something fundamental has been bothering me for a while and I think it comes down to data ownership. For those unfamiliar, BTC Map uses [OpenStreetMap (OSM)](https://www.openstreetmap.org) as its main geographic database. OSM is centred on the concept of a commons of objectively verifiable data that is maintained by a global community of volunteer editors; a Wikipedia for maps. There is no data ownership; the data is free (as in freedom) and anyone can edit anything. It is the data equivalent of FOSS (Free and Open Source Software) \- FOSD if you will, but more commonly referred to as [Open Data](https://en.wikipedia.org/wiki/Open_data). In contrast, Notes and Other Stuff on Nostr ([Places](https://github.com/nostr-protocol/nips/pull/927) in this cartographic context) are explicitly owned by the controller of the private key. These notes are free to propagate, but they are owned. How do we reconcile the decentralised nature of Nostr, where data is cryptographically owned by individuals, with the community-managed data commons of OpenStreetMap, where no one owns the data? # Self-sovereign Identity Before I address this coexistence question, I want to talk a little about identity as it pertains to ownership. If something is to be owned, it has to be owned by someone or something \- an identity. All identities that are not self-sovereign are, by definition, leased to you by a 3rd party. You rent your Facebook identity from Meta in exchange for your data. You rent your web domain from your DNS provider in exchange for your money. Taken to the extreme, you rent your passport from your Government in exchange for your compliance. You are you at the pleasure of others. Where Bitcoin separates money from the state; Nostr separates identity from the state. Or, as [@nvk](nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8) said recently: ["Don't build your house on someone else's land."](nostr:nevent1qqsf493dryeqzrsfjq938hpjg3jf3yd8cv70a9ggzlts5p29tasawkqpz9mhxue69uhkummnw3ezuamfdejj7q3qaz9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgsxpqqqqqqzajen2k). https://i.nostr.build/xpcCSkDg3uVw0yku.png While we’ve had the tools for self-sovereign digital identity for decades (think PGP keys or WebAuthN), we haven't had the necessary social use cases nor the corresponding social graph to elevate these identities to the mainstream. Nostr fixes this. Nostr is PGP for the masses and will take cryptographic identities mainstream. # Full NOSTARD? Returning to the coexistence question: the data on OpenStreetMap isn’t directly owned by anyone, even though the physical entities the data represents might be privately owned. OSM is a data commons. We can objectively agree on the location of a tree or a fire hydrant without needing permission to observe and record it. Sure, you could place a tree ‘on Nostr’, but why should you? Just because something can be ‘on Nostr’ doesn’t mean it should be. https://i.nostr.build/s3So2JVAqoY4E1dI.png There might be a dystopian future where we can't agree on what a tree is nor where it's located, but I hope we never get there. It's at this point we'll need a [Wikifreedia](https://wikifreedia.xyz/) variant of OpenStreetMap. While integrating Nostr identities into OpenStreetMap would be valuable, the current OSM infrastructure, tools, and community already provide substantial benefits in managing this data commons without needing to go NOSTR-native \- there's no need to go [Full NOSTARD](https://fountain.fm/clip/48noGYA7bRXNP96dqsOP). H/T to [@princeySOV](nostr:npub1hghnjjpnvkz8t6gkszuf37d7puwc2qtxc65rnklqsngzv6kkug9qhhfyz2) for the [original meme](nostr:nevent1qqst7609zyuy92q655mzls5trdv8u6h8d4v7myjc3t6gvxs68qrtp6cpr9mhxue69uhhyetvv9ujuam9d3kx7unyv4ezumn9wszka25g). https://i.nostr.build/ot9jtM5cZtDHNKWc.png So, how do we appropriately blend cryptographically owned data with the commons? If a location is owned in meatspace *and* it's useful to signal that ownership, it should also be owned in cyberspace. Our efforts should therefore focus on entities like businesses, while allowing the commons to manage public data for as long as it can successfully mitigate the [tragedy of the commons](https://en.wikipedia.org/wiki/Tragedy_of_the_commons). The remainder of this article explores how we can: 1. Verify ownership of a physical place in the real world; 2. Link that ownership to the corresponding digital place in cyberspace. As a side note, I don't see private key custodianship \- or, even worse, permissioned use of Places signed by another identity's key \- as any more viable than the rented identities of Web 2.0. And as we all know, the Second Law of Infodynamics (no citation\!) states that: > "The total amount of sensitive information leaked will always increase over time." This especially holds true if that data is centralised. Not your keys, not your notes. Not your keys, not your identity. # Places and Web-of-Trust [@Arkinox](nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w) has been leading the charge on the [Places NIP](https://github.com/nostr-protocol/nips/pull/927), introducing Nostr notes (kind 37515\) that represent physical locations. The draft is well-crafted, with bonus points for linking back to OSM (and other location repositories) via [NIP-73 \- External Content IDs](https://github.com/nostr-protocol/nips/blob/744bce8fcae0aca07b936b6662db635c8b4253dd/73.md) (championed by [@oscar](nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2) of [@fountain](nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5)). However, as Nostr is permissionless, authenticity poses a challenge. Just because someone claims to own a physical location on the Internet doesn’t necessarily mean they have ownership or control of that location in the real world. Ultimately, this problem can only be solved in a decentralised way by using [Web-of-Trust](https://en.wikipedia.org/wiki/Web_of_trust) \- using your social graph and the perspectives of trusted peers to inform your own perspective. In the context of Places, this requires your network to form a view on which digital identity (public key / npub) is truly the owner of a physical place like your local coffee shop. This requires users to: 1. Verify the owner of a Place in cyberspace is the owner of a place in [meatspace](https://en.wiktionary.org/wiki/meatspace). 2. Signal this verification to their social graph. Let's look at the latter idea first with the concept of Attestations ... # Attestations A way to signal to your social graph that you believe something to be true (or false for that matter) would be by publishing an Attestation note. An Attestation note would signify to your social graph that you think something is either true or false. Imagine you're a regular at a local coffee shop. You publish an Attestation that says the shop is real and the owner behind the Nostr public key is who they claim to be. Your friends trust you, so they start trusting the shop's digital identity too. However, attestations applied to Places are just a single use case. The attestation concept could be more widely applied across Nostr in a variety of ways (key rotation, identity linking, etc). Here is a [recent example](nostr:nevent1qqsx8qu64xpnqaqkcqtrm4ly4l6xdqk9g2wkcaxxm3hzcc2p3hcz2ugzyr4tpe6k6v4cp0x5vneas39cqspsxp66z04tcdve5a3vntr6hy057y5k93z) from [@lyn](nostr:npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a) that would carry more signal if it were an Attestation: https://i.nostr.build/lZAXOEwvRIghgFY4.png Parallels can be drawn between Attestations and transaction confirmations on the Bitcoin timechain; however, their importance to you would be weighted by clients and/or [Data Vending Machines](https://www.data-vending-machines.org/) in accordance with: 1. Your social graph; 2. The type or subject of the content being attested and by whom; 3. Your personal preferences. They could also have a validity duration to be temporally bound, which would be particularly useful in the case of Places. [NIP-25 (Reactions)](https://github.com/nostr-protocol/nips/blob/master/25.md) do allow for users to up/downvote notes with optional content (e.g., emojis) and *could* work for Attestations, but I think we need something less ambiguous and more definitive. **‘This is true’** resonates more strongly than **‘I like this.’**. https://i.nostr.build/s8NIG2kXzUCLcoax.jpg There are similar concepts in the Web 3 / Web 5 world such as [Verified Credentials](https://developer.tbd.website/docs/web5/verifiable-credentials/what-are-vcs) by [tdb](nostr:npub10ckt8dne8lahkwxwevtxf3rlvgttf2lvqrqc4rg7h8mdhsx6rcpqsg7muq). However, Nostr is the Web 3 now and so wen Attestation NIP? https://i.nostr.build/Cb047NWyHdJ7h5Ka.jpg That said, I have seen [@utxo](nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8) has been [exploring ‘smart contracts’ on nostr](nostr:nevent1qqswm26c4s4h56zwkk47w40mhsqqn66jk6lfas8r07w67h69474kkfgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg5waehxw309aex2mrp0yhxgctdw4eju6t0qgsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36c0kd565) and Attestations *may* just be a relatively ‘dumb’ subset of the wider concept Nostr-native scripting combined with web-of-trust. # Proof of Place Attestations handle the signalling of your truth, but what about the initial verification itself? We already covered how this ultimately has to be derived from your social graph, but what if there was a way to help bootstrap this web-of-trust through the use of oracles? For those unfamiliar with oracles in the digital realm, they are simply trusted purveyors of truth. Introducing *Proof of Place*, an out–of-band process where an oracle (such as [BTC Map](https://btcmap.org/)\) would mail \- yes physically mail\- a shared secret to the address of the location being claimed in cyberspace. This shared secret would be locked to the public key (npub) making the claim, which, if unlocked, would prove that the associated private key (nsec) has physical access to the location in meatspace. One way of doing this would be to mint a 1 sat [cashu](https://github.com/cashubtc) ecash token locked to the npub of the claimant and mail it to them. If they are able to redeem the token then they have cryptographically proven that they have physical access to the location. Proof of Place is really nothing more than a weighted Attestation. In a web-of-trust Nostrverse, an oracle is simply a npub (say BTC Map) that you weigh heavily for its opinion on a given topic (say Places). In the Bitcoin world, Proof of Work anchors digital scarcity in cyberspace to physical scarcity (energy and time) in meatspace and as [@Gigi](nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc) says in [PoW is Essential](https://dergigi.com/threads/pow-is-essential): > "A failure to understand Proof of Work, is a failure to understand Bitcoin." In the Nostrverse, Proof of Place helps bridge the digital and physical worlds. [@Gigi](nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc) also observes in [Memes vs The World](https://dergigi.com/threads/memes-vs-the-world) that: > "In Bitcoin, the map is the territory. We can infer everything we care about by looking at the map alone." https://i.nostr.build/dOnpxfI4u7EL2v4e.png This isn’t true for Nostr. In the Nostrverse, the map IS NOT the territory. However, Proof of Place enables us to send cryptographic drones down into the physical territory to help us interpret our digital maps. 🤯 # Check-ins Although not a draft NIP yet, [@Arkinox](nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w) has also been exploring the familiar concept of [Foursquare](https://foursquare.com/)\-style [Check-ins on Nostr](nostr:naddr1qvzqqqr4gupzp68dx7vvdlltl7sg2qdv8838ze3tl5tq76y0jnz966fdsana6dz6qqxnzde3xqungv3jxq6ngvp52f3mja) (with kind 13811 notes). For the uninitiated, Check-ins are simply notes that signal the publisher is at a given location. These locations could be Places (in the Nostr sense) or any other given digital representation of a location for that matter (such as [OSM elements](https://wiki.openstreetmap.org/wiki/Elements)) if [NIP-73 \- External Content IDs](https://github.com/nostr-protocol/nips/blob/744bce8fcae0aca07b936b6662db635c8b4253dd/73.md) are used. Of course, not everyone will be a Check-in enjoyooor as the concept will not sit well with some people’s threat models and OpSec practices. Bringing Check-ins to Nostr is possible (as [@sebastix](nostr:npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefe) capably [shows here](nostr:note1wjf6x9a5xehzr3z0hm8fgdyenznf6hxlmswldhmhsgk7fc9e86cscmsnve)), but they suffer the same authenticity issues as Places. Just because I say I'm at a given location doesn't mean that I am. Back in the Web 2.0 days, Foursquare mitigated this by relying on the GPS position of the phone running their app, but this is of course spoofable. How should we approach Check-in verifiability in the Nostrverse? Well, just like with Places, we can use Attestations and WoT. In the context of Check-ins, an Attestation from the identity (npub) of the Place being checked-in to would be a particularly strong signal. An NFC device could be placed in a coffee shop and attest to check-ins without requiring the owner to manually intervene \- I’m sure [@blackcoffee](nostr:npub1dqepr0g4t3ahvnjtnxazvws4rkqjpxl854n29wcew8wph0fmw90qlsmmgt) and [@Ben Arc](nostr:npub1c878wu04lfqcl5avfy3p5x83ndpvedaxv0dg7pxthakq3jqdyzcs2n8avm) could hack something together over a weekend\! Check-ins could also be used as a signal for bonafide Place ownership over time. # Summary: Trust Your Bros So, to recap, we have: **Places**: Digital representations of physical locations on Nostr. **Check-ins**: Users signalling their presence at a location. **Attestations**: Verifiable social proofs used to confirm ownership or the truth of a claim. You can visualise how these three concepts combine in the diagram below: https://i.nostr.build/Uv2Jhx5BBfA51y0K.jpg And, as always, top right trumps bottom left\! We have: **Level 0 \- Trust Me Bro:** Anyone can check-in anywhere. The Place might not exist or might be impersonating the real place in meatspace. The person behind the npub may not have even been there at all. **Level 1 \- Definitely Maybe Somewhere:** This category covers the middle-ground of ‘Maybe at a Place’ and ‘Definitely Somewhere’. In these examples, you are either self-certifying that you have checked-in at an Attested Place or you are having others attest that you have checked-in at a Place that might not even exist IRL. **Level 2 \- Trust Your Bros:** An Attested Check-in at an Attested Place. Your individual level of trust would be a function of the number of Attestations and how you weigh them within your own social graph. https://i.nostr.build/HtLAiJH1uQSTmdxf.jpg Perhaps the gold standard (or should that be the Bitcoin standard?) would be a Check-in attested by the owner of the Place, which in itself was attested by BTC Map? Or perhaps not. Ultimately, it’s the users responsibility to determine what they trust by forming their own perspective within the Nostrverse powered by web-of-trust algorithms they control. ‘Trust Me Bro’ or ‘Trust Your Bros’ \- you decide. As we navigate the frontier of cryptographic ownership and decentralised data, it’s up to us to find the balance between preserving the Open Data commons and embracing self-sovereign digital identities. # Thanks With thanks to [Arkinox](nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w), [Avi](nostr:npub1hqaz3dlyuhfqhktqchawke39l92jj9nt30dsgh2zvd9z7dv3j3gqpkt56s), [Ben Gunn](nostr:npub1lt8nn8aaa6qa63wjwj8gz2djf5nlhg3zfd0v6l45v8zhvuyh0p3s5zzt5y), [Kieran](nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49), [Blackcoffee](nostr:npub1dqepr0g4t3ahvnjtnxazvws4rkqjpxl854n29wcew8wph0fmw90qlsmmgt), [Sebastix](nostr:npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefe), [Tomek](nostr:npub1t30xvk4f3h86lhxazadwx6f2namer9yzgl70kfljfhr556g7su0qwg0lmp), [Calle](nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg), [Short Fiat](nostr:npub1md39ua3h2s7204a7v5p9sdxmxx9qc7m4kr3r6naeuwfznad6d7nsxpctp9), [Ben Weeks](nostr:npub1jutptdc2m8kgjmudtws095qk2tcale0eemvp4j2xnjnl4nh6669slrf04x) and [Bitcoms](nostr:npub18s6axkw94d57sg438rp7pzf94vn8la4axyvd5f6wnjrgudtw54ps53eqxk) for helping shape my thoughts and refine content, whether you know it or not\!

@ 1b0706e7:ec11b9b3

Happy New Year Bitcoiners!  It's 2024. The having is about 4 months away. I created a new logo. It's a photo of a painting I have in my office overlapped onto a Riverside Bell Sticker sitting on top of my S9 heater. If you look at the photo closely, you can see the S9. I also My new year's resolution is to automate the meetup schedule. We will meet at Mt. Rubidoux the first Saturday of each month at 08:00 a.m. I will be by the sign in the picture. The location is here. We will start hiking at about 8:30 a.m. https://what3words.com/echo.robots.informs Here is a picture of the sign we will meet at: https://i.nostr.build/6PoP.jpg We will also meet at Cheeba Hut the Third Saturday of the mont from 6 p.m till 8 p.m. They have sandwiches, beer and cool vibes. The main reason I want to hold the bitcoin meetup here is because they allow grafitti artists to stick their stickers on napkin holders and soda fountains. Bitcoin rocks is a grafitti artist who pays people to put his bitcoin grafitti stickers in highly visible areas. A couple of months agom I saw this sticker at one of the meetups I held. https://i.nostr.build/zn6z.jpg The next Cheeba Hut will be on Satruday January 20th from 6-8, but I plan on being there at 5 because the traffic sucked last time. Park at the Hampton Inn. I didn't know that last time and it took me a half hour to find parking because of the Festival of Lights. That should not be an issue this month. I'll be in the patio, wearing some bitcoin gear or maybe a nostr hat. https://what3words.com/spark.stored.blocking By the way, I didn't put those stickers there. I don't know who did. Bitcoin.rocks is nostr only now. The man or woman who put the sticker there is probably on nostr. I plan to grow nostr and grow the riverside bitcoin meetup by strategicly placing stickers around town where Bitcoiner's are likely to see them. I'll place some at Cheeba Hut because I have permission to do so. I also want to want to place a QR code that links to the Riverside Bitcoin Meetup Calender at Bitcoin ATM's. Stickers are ideal because they can be easily removed and do not do permenant damage to property. I'm not sure if this is technically legal, but if the Bitcoin ATM owners don't want people promoting the use of bitcoin on their ATM's, what are they in business for? I also plan on writing a newsletter once a week and I have talked to another pleb about making a podcast. The idea is to create a [beacon in cyberspace](https://twentyone.world/concept) that speaks the language of the community of Riverside. Riverside is a community that speaks many languages. I speak mostly English, but many people in our community speak Spanish and we have a large deaf population because of the California School for the Deaf is located in the heart of the city. If you know any of these languages, please reach out. I could use your help. I could also use some help painting this town orange(putting bitcoin stickers up). I know at least one person near me is willing to do this. :) [Onward](nostr:note1368g8mqek46tg5qnfdsgyu59narx4w4t3zu59z8zzfxzea7nlt8s9qrufh) The Riverside Bitcoin Meetup The Riverside Bitcoin Meetup is a meetup group based in Riverside, California. Our mission is to create an online beacon of local bitcoiners who promote the use of bitcoin in our local community through education and outreach. **Want to help?** Let's talk. [Onward](nostr:note1368g8mqek46tg5qnfdsgyu59narx4w4t3zu59z8zzfxzea7nlt8s9qrufh) [฿logging฿itcoin](https://bloggingbitcoin.pages.dev/) [800,420](https://timechaincalendar.com/en) US Debt Clock [Calendar](nostr:naddr1qqyx2ve48qukzwtyqy8hwumn8ghj7mn0wd68ytnddaksygqmqurwwsmmhhya50waf7md8y92yp4ywng9q97hz7td4a7wcydekvpsgqqq0j6qyx42zz) Support by zapping, sharing, [shopping](https://habla.news/u/riversidebtcmeetup@nostrplebs.com/riverside-online-farmers-market), and subscribing. Let's build an online [community](nostr:npub1rvrsde6r0w7unk3am48md5us4gsx536dq5qh6utedkhhemq3hxesehc89n) Want to sell something in the Riverside Online Farmer's Market? Let me know.

@ 7f5c2b4e:a818d75d

## What is Obsidian? [Obsidian.md](https://obsidian.md/) is a versatile and powerful note-taking and knowledge management application that's gained immense popularity among users seeking a robust digital tool for organizing their thoughts, ideas, and information. #Obsidian boasts an array of features and benefits that can't all be covered in a single article. Instead, this #guide focuses on a unique, yet potent use case that has recently emerged - the ability to publish #Nostr notes and long-form posts directly from the app. This capability has been made feasible through the complementary nature of Obsidian and Nostr. Obsidian is an open-source software with a thriving community and extensive support for custom plugins. On the other hand, Nostr is an open protocol with a rapidly expanding suite of tools, simplifying the integration of Nostr across various corners of the Internet. The plugin I will cover in this guide is called Nostr Writer. > Obsidian link: obsidian://show-plugin?id=nostr-writer > > GitHub: https://github.com/jamesmagoo/nostr-writer > > Developer: nostr:npub10a8kw2hsevhfycl4yhtg7vzrcpwpu7s6med27juf4lzqpsvy270qrh8zkw But before we dive in, let me share some thoughts on why should one use Obsidian to publish long-form posts (and potentially even short notes) on Nostr. ## Why post with Obsidian? This is a question that naturally comes to mind: "Why use Obsidian to publish on Nostr when the legendary Nostr developers have already set up all the necessary infrastructure for browser-based publishing?" Well, there are several reasons: 1. **Native Markdown Support:** To begin, Obsidian employs plain text Markdown formatting for notes, just like all Nostr-based blogging platforms. This makes it an ideal choice for creating, formatting, and editing Nostr posts. 2. **Illustrative Preview:** While other blogging platforms offer preview tools, Obsidian has perfected this feature. It provides a beautifully customizable preview window that can be positioned anywhere in your workspace, allowing you to visualize how formatting, media, and embeds will appear in the published post[^1]. 3. **State-of-the-Art Flexibility:** Since 2020, Obsidian has continuously improved the way writers interact with it. What sets it apart is not only the dedicated team but also its thriving community, all contributing to its refinement. Obsidian supports an extensive array of plugins, shortcuts, and hotkeys, offering unparalleled flexibility and customization. Comprehensive [documentation](https://help.obsidian.md/Home) and a ton of [videos](https://www.youtube.com/results?search_query=obsidian) and even [courses](https://youtu.be/WqKluXIra70?si=3ZlnOZA9o3xXys8M) on YouTube provide a wealth of information to tailor Obsidian to your preferences. 4. **Boosted Productivity:** The Nostr Writer plugin is a game-changer for power users of Obsidian. If you're already using Obsidian for note-taking, employing this tool to publish your notes on Nostr is a no-brainer. If you haven't explored it yet, I strongly recommend giving it a try. It has the potential to transform how you think, plan, and structure your ideas for the better. Trying it for broader objectives will help you appreciate how well it complements Nostr. 5. **Distraction-Free Composition:** While you may disagree, browsers can be a significant source of distraction, with constant alerts, notifications, and blinking extensions. Composing within Obsidian offers a tranquil, clutter-free experience, fostering focus and productivity. 6. **Local Record Keeping:** Thanks to Nostr Writer, Obsidian keeps a local record of events you published to Nostr in a JSON file on your computer. Your long-form posts are also securely stored in the `.md` format on your machine, just like all the Obsidian notes you create. 7. **Drafts You Can Count On:** Drafts are often a weak point in long-form platforms. Even though Nostr developers have addressed some of these concerns, the "vanishing drafts problem" still lingers. Obsidian, designed with data safety in mind, stores all your notes locally on your device. Whether you open your laptop tomorrow or in a year, your files will be there, safe from external disruptions. For added redundancy, consider using Obsidian Sync, which encrypts and synchronizes your notes across your chosen devices. While there are more benefits to utilizing Obsidian for both Nostr publishing and in your general workflow, these reasons should provide a solid understanding. Now, let's shed some light on the Nostr Writer plugin. ## Nostr Writer I stumbled upon Obsidian not too long ago, all thanks to nostr:npub1zvvv8fm7w2ngwdyszg3y6zgp6vwqlht8zrr8wcmjaxjecrvpjfwsd0zs7w. He's also the one who introduced me to the Nostr Writer plugin. Until recently, I primarily used Obsidian "as intended" - for documenting my thoughts and writing articles. What I found especially convenient was using it to compose long-form Nostr posts. And then, the revelation came when I discovered the Nostr Writer plugin - it transformed the experience. No more copy-pasting and meticulous adjustments were required; I can simply compose, add a cover image and description, and publish - it's as straightforward as that. As I mentioned earlier, Obsidian boasts a vast library of community-driven plugins. To begin using Nostr Writer, simply install the plugin from the "Community plugins" section and navigate to the plugin settings to set up your publishing workflow.  > You can install the plugin by clicking [this link](obsidian://show-plugin?id=nostr-writer) while having Obsidian open on your device, or by going to the "Community plugins" tab in the settings and typing "Nostr" in the search field. Once the plugin is installed, you'll need to customize it to enable publishing your Obsidian notes to Nostr.  Primarily, you'll need to paste your private key (`nsec`) into the corresponding field. Additionally, I recommend configuring your relays to ensure the widest reach for your posts. If you're unfamiliar with Nostr relays or wish to enhance your understanding, you can explore my relay guide [here](https://habla.news/tony/relays). Many Nostr users naturally have concerns about sharing their private keys with apps. In this case, worry not. Your private key is stored exclusively on your local device and never leaves it. More details can be found [here](https://github.com/jamesmagoo/nostr-writer#security-notice). Even if you use Obsidian sync to keep your notes updated across multiple devices, all information is locally encrypted and safeguarded by the password of your choice. Neither the Obsidian developers nor the plugin developer have access to your files. For additional information, you can refer to the "[Security and privacy](https://help.obsidian.md/Obsidian+Sync/Security+and+privacy)" section of the Obsidian documentation. As you can see in the screenshot above, Nostr Writer also provides the option to post short notes. By toggling the corresponding slider, a pencil icon will appear on the sidebar, allowing you to post short notes without leaving Obsidian:  While I wouldn't claim that the plugin surpasses any of the "Twitter-like" Nostr clients, it can prove handy if you're already working within Obsidian and wish to share a quote or any other snippet of information you've come across in your notes. ## Publishing Publishing posts with Nostr Writer is straightforward. If you're already familiar with Obsidian, composing and formatting will be a total breeze, and the actual posting process is no different from posting with [Habla](https://habla.news/), or any other Nostr-native blogging platform. > The only thing that may differ from some Nostr platforms is that Nostr Writer does not provide a specific field for adding hashtags when publishing. Instead, you should incorporate them directly into your text. Once you've finished crafting your blog post, simply click on the upload icon in the side menu to specify the title, add a summary, and attach a cover image.  When you're ready, click "Confirm and Publish."  Another point to note is the relays indicator in the bottom-left corner. Relay connection may get interrupted if left inactive for a while, but a simple click on the widget will reconnect you to Nostr in no time.  ## Practice makes perfect As I mentioned earlier, I find this approach to publishing long-form posts on Nostr the most efficient and convenient. Moreover, there are [numerous improvements](https://github.com/jamesmagoo/nostr-writer#coming-soon) in the pipeline for the plugin, which is nothing short of exciting. With that said, it's worth visiting Habla after publishing your post to double-check that everything appears as intended. Initially, you might encounter some formatting peculiarities that you'll need to get accustomed to, but with practice, you'll effortlessly master them. Soon, you won't even have to worry about how the article looks in Nostr clients because you'll be able to visualize every single aspect of your post in your mind. --- I hope you found this guide useful and consider utilizing Obsidian for both publishing Nostr posts and elevating your overall productivity. If that's the case, please show your support for nostr:npub10a8kw2hsevhfycl4yhtg7vzrcpwpu7s6med27juf4lzqpsvy270qrh8zkw' [work](https://github.com/jamesmagoo/nostr-writer). > Please feel free to share your thoughts and suggestions—I'm always eager to hear from you! Don't forget that my Habla [blog page](https://habla.news/tony/) contains a ton of Nostr guides, so you can find answers to almost any Nostr-related questions. If there are specific topics you believe I should cover, do let me know. _See you on the other side of the Nostr rabbit hole._ _Tony_ --- P.S. This post was composed, formatted and published to Nostr from Obsidian. No Nostr-related blogging platform was used. [^1]: Nostr-native syntax, including tagging and Nostr-events embeds, is an exception here. Not all platforms on the Internet currently support Nostr syntax standards like tagging users with their npub, as in `nostr:npub10awzknjg5r5lajnr53438ndcyjylgqsrnrtq5grs495v42qc6awsj45ys7`, so it may not be available for preview. However, tags and embeds will be displayed on [Habla](https://habla.news/). You can learn more about Habla's features in my previous guide [here](https://habla.news/tony/habla-features).