pull down to refresh

0 sats \ 2 replies \ @PlebeiusG 24 Mar \ parent \ on: Impacts of Nostr and Lightning on Small Business Operations Design
This idea is so unpolished though. A chatbot is way overkill. Users will be asking the same questions and it will be generating responses for each.
I can imagine for a website with a lot of documentation... or even a city govt website it will be able to look thru the sites content and generate a useful answer... but i what would starbucks need it for? Langchain has a working integration on their site that is money! But most small sites wouldn't need it.
write
preview
43 sats \ 1 reply \ @earthcakes OP 24 Mar
This is kind of where I end up for most use cases. These are kind of some I’ve assembled so far:
  • Internal Private Relay; for internal team communication and collaboration. Something like Notion, Monday, or JIRA.
  • Public Relay; for Release Notes. Crowdfunding ideas or small contracts. Like software forums with feature voting or bug bounties.
  • Paid-Only Relays; for magazines and blogs, tiered memberships, events. An example here might be an AirBnB hosting a private relay on its WiFi with house instructions, local info, transportation tips and fare.
  • A wilder idea here; but say a customer uses a product based relay (let’s use cars as an example). Someone could almost provide their personal data from a vehicles computer; how far they drive, how often they maintenance, maintenance instructions, etc. Either privately with the company, or publicly as a product review. Another analogy might be sharing your data with a software company for performance monitoring and bug enhancements etc - private relays could both report data and collect a kick-back for the data one provides.
reply
0 sats \ 0 replies \ @PlebeiusG 24 Mar
Good ideas!
Sounds like these will need purpose-built clients for almost each use case. I think that's where nostr is headed.
reply