Friday, May 5, 2023

Error converting content: marked is not a function

- practice/accent
- Arghhh- #log🪵/alwaysbelooking - so irked by Message Bird interview. Made me feel shallow. Fucking SMS infrastructure what not. Let' fucking do deep into the stack! #TrialAndError.AI
- Build protocol mofo - like VIVOXVANI - it ain't hard. Just deep in the stack - and less "blog posts" about it.
	  collapsed:: true
  - #thanksChatGPT
  - Building an SMS infrastructure from scratch is a complex task and requires a deep understanding of telecommunications protocols, programming, and hardware. Here's a high-level overview of the process:
  - Research and understanding:
			  Before you start, gain a good understanding of the SMS infrastructure and its components. Learn about the Short Message Service Center (SMSC), SMS gateways, and protocols like SMPP, HTTP, and SS7.
  - Choose the technology stack:
			  Select the programming languages, frameworks, and databases for building your SMS infrastructure. Common choices include Python, Java, Node.js, and frameworks like Django, Spring Boot, or Express.js.
  - Acquire necessary hardware:
			  Set up servers and networking equipment needed for your infrastructure. You may also choose to use cloud-based solutions like AWS, Google Cloud, or Azure to host your infrastructure.
  - Obtain access to mobile network operators:
			  To send and receive SMS messages, you need to have access to mobile network operators (MNOs). You can either negotiate agreements directly with MNOs or partner with an aggregator who already has connections.
  - Implement SMSC and SMS gateway:
			  Develop the core components of your infrastructure - the SMSC and SMS gateway. The SMSC is responsible for storing, routing, and delivering SMS messages, while the SMS gateway acts as an interface between your infrastructure and external systems.
  - Implement protocols:
			  Implement the necessary protocols to communicate with MNOs and external systems. Common protocols include SMPP for communication with MNOs and HTTP/REST for APIs exposed to external systems.
  - Develop APIs for external systems:
			  Develop APIs to allow third-party systems to integrate with your SMS infrastructure. These APIs should enable sending, receiving, and managing SMS messages.
  - Implement security measures:
			  Ensure the security of your infrastructure by implementing encryption, authentication, and access control. Secure your APIs with authentication methods like OAuth or API keys.
  - Test and debug:
			  Thoroughly test your SMS infrastructure to ensure it is functioning correctly and efficiently. Debug and fix any issues that arise during testing.
  - Deploy and monitor:
			  Deploy your SMS infrastructure and monitor its performance. Set up monitoring tools to track metrics like message throughput, latency, and success rates.
  - Scale and optimize:
			  As your SMS infrastructure grows, you may need to scale it to handle increased message volumes. Optimize your infrastructure for performance and cost-efficiency.
  - Maintain and update:
			  Regularly maintain and update your infrastructure to ensure it remains secure and up-to-date with industry standards and best practices.
			  
			  Building an SMS infrastructure from scratch is a significant undertaking. If you're looking for a simpler solution, consider using existing SMS APIs or platforms like Twilio, Plivo, or Nexmo, which offer pre-built infrastructure and APIs for sending and receiving SMS messages.
- Ego - The Tool
- You need the ego
  - Athlete
  - - You are an artist of you can make someone feel something different and unexpected- @Miles Fisher
- Vidoes goes viral not because everyone just gets it. It’s because some people watch it over and over and over again.
- Ideas are like fish. You catch them
- Success - story is unique, they never quit
- Became a fan of this guy listening to him speak. First impression - on this podcast  - {{video https://youtu.be/jnNQEiPs5r0}}
- - #projectidea he mentioned speaking with Thomas Jefferson - could collaborate? For vitality
- Still Head
- Don’t move
- Moment
- Text completion API
- Notebook
- Plan
- Log
  - Next action
  - Observe
  - Plan
  - Log again
  - Change
  - Complex task done
- -