Oddbean new post about | logout
 If you're writing something a bit high-brow or "unpopular" (in the literal sense, of requiring expertise of specialization to interpret) -- either because it's very academic or technical, or written in a more literary style -- don't feel bad, if you don't get many responses to it.

Your audience here, as everywhere, is a tiny subset of the overall population. Think more about targeting that audience with "discovery aids", like hashtags, or publishing to a relay where a lot of such people read, like devs.nostr1.com or theforest.nostr1.com.

#Economics
#Technology
#Literature 
 ty, fren  :3 
 Another easy thing you can do, is to publish it in a different event kind and then just promote the event in a kind 01 note, or publish it to a website.

People who can #Name10Books tend to browse the articles, including from people they don't follow. Eventually, this subset of users will be entering Nostr primarily over the various long-form and OtherStuff, like they currently do with Medium, Substack, GitHub, or SimplyRecipes, so make sure that you have your notes up there.

nostr:note10nr2y540u79prfk56q4s695a740hn7f3j888nz7h3y872tcuxzaqwffxsl  
 On that note, @OceanSlim your relay is throwing me an error. 
 Says it could not connect to the database, but I think it might just be rejecting a duplicate upon broadcasting. You might want to return a more informative message, in that case. 
 That is probably the case. I'll have to look more closely at it. Trying to make this video on the code base before I make more changes. Thank you for the report though! Keep em coming.  
 Best would probably be, if it didn't return an error, as nothing actually went wrong and there is no further need to act. Like the info Cloudfodder returns here.

Just FYI.

https://image.nostr.build/ad2352c20d728fb04617da8b5c406e8a0ddcf0348d3a71828586f52c5510a7b5.png 
 Awesome. I will add this to the list to fix in the next release.  
 Says it could not connect to the database, but I think it might just be rejecting a duplicate upon broadcasting. You might want to return a more informative message, in that case. 
 That is probably the case. I'll have to look more closely at it. Trying to make this video on the code base before I make more changes. Thank you for the report though! Keep em coming.  
 Best would probably be, if it didn't return an error, as nothing actually went wrong and there is no further need to act. Like the info Cloudfodder returns here.

Just FYI.

https://image.nostr.build/ad2352c20d728fb04617da8b5c406e8a0ddcf0348d3a71828586f52c5510a7b5.png 
 Awesome. I will add this to the list to fix in the next release.