@a5gard/asgard 0.0.1

package/.vscode/ntrsync/10015_APP IDEA - Onlyfans.md

@@ -0,0 +1,293 @@
+<<<<<<< HEAD:10003_APP IDEA - Onlyfans.md
+# APP IDEA - Onlyfans
+
+- to ensure user interaction is not burdened to much by onlyfans stupid practices it might be best to use a browser ap to create the order with the client wihle they are on the same page, that sends the data to the offsite dashbaord to be used for later the only down side is that they would have to manually data over to the broswer app but... this would be the most effeicnt way for the content creator because they wouldnt have to open any other programs or websites, this allows the creator to contiunue selling through only fans but widening the product offerings  
+
+- so it fits the content creation schedule while at the same time not breaking onlyfans tos
+You're absolutely right! Using a browser-based app that integrates seamlessly with OnlyFans while the creator is on the platform is a great way to minimize friction and ensure compliance with OnlyFans' TOS. This approach allows creators to manage custom orders efficiently without leaving OnlyFans or breaking any rules.
+
+- Here's how you can design this system:
+
+- Key Workflow
+- Creator and Client Chat on OnlyFans:
+
+- The client sends a custom order request via OnlyFans chat.
+
+- The creator uses the browser app to log the order details while staying on the OnlyFans page.
+
+- Order Creation in the Browser App:
+
+- The creator inputs the client’s username, order details, and price into the browser app.
+
+- The app sends this data to the off-site dashboard for tracking and queue management.
+
+- Creator Sends Locked Message:
+
+- The creator sends a locked message to the client on OnlyFans with the price and instructions for payment.
+
+- The client pays upfront to confirm the order.
+
+- Order Fulfillment:
+
+- The creator works on the custom content and sends it to the client as another locked message or post.
+
+- The creator updates the order status in the off-site dashboard.
+
+- Benefits of This Approach
+- No Additional Programs or Websites:
+
+- The browser app runs alongside OnlyFans, so creators don’t need to switch between platforms.
+
+- Compliance with OnlyFans TOS:
+
+- All payments and content delivery happen within OnlyFans.
+
+- Efficient Order Management:
+
+- The off-site dashboard keeps track of orders, so creators can focus on content creation.
+
+- Tech Stack
+- Browser App:
+- Framework: Use a browser extension or a bookmarklet (a small JavaScript app that runs in the browser).
+
+- UI: A simple popup or sidebar that overlays the OnlyFans page.
+
+- Data Storage: Send data to your off-site dashboard via an API.
+
+- Off-Site Dashboard:
+- Frontend: Remix-run (as you're already using it)
+
+- Backend: Node.js with Express or Remix’s built-in server capabilities
+
+- Database: PostgreSQL or MongoDB (for storing orders and queue data)
+
+- ORM: Prisma (for database management)
+
+- Authentication:
+- Remix-auth: For handling creator login and authentication.
+
+- Hosting:
+- Platform: Vercel, Netlify, or AWS for hosting the dashboard.
+
+- Implementation Steps
+- Build the Browser App:
+
+- Create a browser extension or bookmarklet that overlays the OnlyFans page.
+
+- The app should include a form for logging order details (e.g., client username, order description, price, etc.).
+
+- Use JavaScript to send this data to your off-site dashboard via an API.
+
+- Off-Site Dashboard:
+
+- Build a dashboard where creators can view and manage their orders.
+
+- Use a database to store order details and queue data.
+
+- API for Data Transfer:
+
+- Create an API endpoint to receive order data from the browser app.
+
+- Store the data in your database and update the dashboard in real-time.
+
+- Pre-Written Templates:
+
+- Provide creators with pre-written templates for locked messages to streamline communication with clients.
+
+- Testing and Deployment:
+
+- Test the browser app and dashboard with a small group of creators.
+
+- Deploy the dashboard and make the browser app available for download or installation.
+
+- Example Workflow
+- Client Requests Custom Content:
+
+- Client sends a message on OnlyFans: "Hi, I’d like a custom video for $50."
+
+- Creator opens the browser app and inputs the order details.
+
+- Order Creation:
+
+- The browser app sends the order data to the off-site dashboard.
+
+- The dashboard adds the order to the creator’s queue.
+
+- Creator Sends Locked Message:
+
+- Creator sends a locked message to the client: "Thanks for your request! Please pay $50 to unlock this message and confirm your order."
+
+- Client pays upfront to confirm the order.
+
+- Order Fulfillment:
+
+- Creator works on the custom content and sends it to the client as another locked message: "Your custom video is ready! Please pay $50 to unlock it."
+
+- Creator updates the order status in the dashboard to "Completed."
+
+- Compliance with OnlyFans TOS
+- Ensure that all payments and content delivery happen within OnlyFans.
+
+- Do not scrape data from OnlyFans or automate interactions programmatically.
+
+- Future Enhancements
+- Real-Time Sync:
+
+- If OnlyFans ever releases a public API, you can sync order data automatically between the browser app and the dashboard.
+
+- Analytics:
+
+- Add analytics to the dashboard to help creators track revenue, order volume, and client engagement.
+
+- Mobile Support:
+
+- Develop a mobile-friendly version of the browser app for creators who use OnlyFans on their phones.
+
+- This approach ensures a seamless experience for creators while keeping everything compliant with OnlyFans' TOS. Let me know if you need help with specific parts of the implementation, such as building the browser app or setting up the API!
+=======
+# APP IDEA - Onlyfans
+
+to ensure user interaction is not burdened to much by onlyfans stupid practices it might be best to use a browser ap to create the order with the client wihle they are on the same page, that sends the data to the offsite dashbaord to be used for later the only down side is that they would have to manually data over to the broswer app but... this would be the most effeicnt way for the content creator because they wouldnt have to open any other programs or websites, this allows the creator to contiunue selling through only fans but widening the product offerings  
+
+so it fits the content creation schedule while at the same time not breaking onlyfans tos
+You're absolutely right! Using a browser-based app that integrates seamlessly with OnlyFans while the creator is on the platform is a great way to minimize friction and ensure compliance with OnlyFans' TOS. This approach allows creators to manage custom orders efficiently without leaving OnlyFans or breaking any rules.
+
+Here's how you can design this system:
+
+Key Workflow
+Creator and Client Chat on OnlyFans:
+
+The client sends a custom order request via OnlyFans chat.
+
+The creator uses the browser app to log the order details while staying on the OnlyFans page.
+
+Order Creation in the Browser App:
+
+The creator inputs the client’s username, order details, and price into the browser app.
+
+The app sends this data to the off-site dashboard for tracking and queue management.
+
+Creator Sends Locked Message:
+
+The creator sends a locked message to the client on OnlyFans with the price and instructions for payment.
+
+The client pays upfront to confirm the order.
+
+Order Fulfillment:
+
+The creator works on the custom content and sends it to the client as another locked message or post.
+
+The creator updates the order status in the off-site dashboard.
+
+Benefits of This Approach
+No Additional Programs or Websites:
+
+The browser app runs alongside OnlyFans, so creators don’t need to switch between platforms.
+
+Compliance with OnlyFans TOS:
+
+All payments and content delivery happen within OnlyFans.
+
+Efficient Order Management:
+
+The off-site dashboard keeps track of orders, so creators can focus on content creation.
+
+Tech Stack
+Browser App:
+Framework: Use a browser extension or a bookmarklet (a small JavaScript app that runs in the browser).
+
+UI: A simple popup or sidebar that overlays the OnlyFans page.
+
+Data Storage: Send data to your off-site dashboard via an API.
+
+Off-Site Dashboard:
+Frontend: Remix-run (as you're already using it)
+
+Backend: Node.js with Express or Remix’s built-in server capabilities
+
+Database: PostgreSQL or MongoDB (for storing orders and queue data)
+
+ORM: Prisma (for database management)
+
+Authentication:
+Remix-auth: For handling creator login and authentication.
+
+Hosting:
+Platform: Vercel, Netlify, or AWS for hosting the dashboard.
+
+Implementation Steps
+Build the Browser App:
+
+Create a browser extension or bookmarklet that overlays the OnlyFans page.
+
+The app should include a form for logging order details (e.g., client username, order description, price, etc.).
+
+Use JavaScript to send this data to your off-site dashboard via an API.
+
+Off-Site Dashboard:
+
+Build a dashboard where creators can view and manage their orders.
+
+Use a database to store order details and queue data.
+
+API for Data Transfer:
+
+Create an API endpoint to receive order data from the browser app.
+
+Store the data in your database and update the dashboard in real-time.
+
+Pre-Written Templates:
+
+Provide creators with pre-written templates for locked messages to streamline communication with clients.
+
+Testing and Deployment:
+
+Test the browser app and dashboard with a small group of creators.
+
+Deploy the dashboard and make the browser app available for download or installation.
+
+Example Workflow
+Client Requests Custom Content:
+
+Client sends a message on OnlyFans: "Hi, I’d like a custom video for $50."
+
+Creator opens the browser app and inputs the order details.
+
+Order Creation:
+
+The browser app sends the order data to the off-site dashboard.
+
+The dashboard adds the order to the creator’s queue.
+
+Creator Sends Locked Message:
+
+Creator sends a locked message to the client: "Thanks for your request! Please pay $50 to unlock this message and confirm your order."
+
+Client pays upfront to confirm the order.
+
+Order Fulfillment:
+
+Creator works on the custom content and sends it to the client as another locked message: "Your custom video is ready! Please pay $50 to unlock it."
+
+Creator updates the order status in the dashboard to "Completed."
+
+Compliance with OnlyFans TOS
+Ensure that all payments and content delivery happen within OnlyFans.
+
+Do not scrape data from OnlyFans or automate interactions programmatically.
+
+Future Enhancements
+Real-Time Sync:
+
+If OnlyFans ever releases a public API, you can sync order data automatically between the browser app and the dashboard.
+
+Analytics:
+
+Add analytics to the dashboard to help creators track revenue, order volume, and client engagement.
+
+Mobile Support:
+
+Develop a mobile-friendly version of the browser app for creators who use OnlyFans on their phones.
+
+This approach ensures a seamless experience for creators while keeping everything compliant with OnlyFans' TOS. Let me know if you need help with specific parts of the implementation, such as building the browser app or setting up the API!
+>>>>>>> b306f3955273a5ba5e7561a24194ec677a12018b:10015_APP IDEA - Onlyfans.md

package/.vscode/ntrsync/10016_notes repo url.md

@@ -0,0 +1,3 @@
+# notes repo url
+
+https://github.com/8an3/mynotesrepo.git

package/.vscode/ntrsync/10504_adhd symptom.md

@@ -0,0 +1,3 @@
+# adhd symptom
+
+It's like you had a copy of yourself and they had all the same reasoning and thought processing and all that like you usually do but they just didn't have the actual content of the events itself, like you missed the second part of the update that contained the memories themselves so when it's happening you stay calm analytical, and reason through whatever u need to, so the answers themselves will be different but you don't get mad, upset or confused like someone with Alzheimer's

package/.vscode/ntrsync/10505_APP IDEA - GMAIL.md

@@ -0,0 +1,39 @@
+# APP IDEA - GMAIL
+
+how do i make a gmail add on, i wanted to make an add on that when you click sign in on the service you want, it vists the page, hits reset password and puts your email in, when the new reset password emails comes in it takes the link and generates  30 character password auto matically, changes your password to that and and then opens a new window and logs you in but never records the password so your account would be cirually impossible to crack
+
+
+3. Steps to Build the Gmail Add-on
+a. Set Up Google Workspace Add-on
+Go to the Google Apps Script dashboard.
+Create a new project and select "Gmail Add-on."
+Define the appsscript.json file with metadata for your add-on.
+b. Build the Add-on Interface
+Use the Card Service API to create UI components.
+Design a card where users can:
+Choose a service (e.g., dropdown menu).
+Enter their email address.
+c. Integrate Gmail API
+Request access to read incoming reset password emails.
+Parse the reset password email to extract the reset link.
+d. Automate Password Reset
+Use a backend service (like Node.js with Puppeteer) to:
+Visit the password reset page.
+Enter the user’s email and submit the form.
+Wait for the reset email and process the link.
+e. Generate Secure Passwords
+Use a cryptographic library (e.g., crypto in Node.js) to generate a 30-character random password.
+f. Change Password and Log In
+Automate the password change process using web automation.
+Open a browser window with the new login session.
+g. Security Best Practices
+Do not store passwords or sensitive user information.
+Use secure APIs and encrypted communications (e.g., HTTPS).
+Ensure the add-on only operates with user consent.
+h. Publish the Add-on
+Test the add-on thoroughly to ensure it works as intended and complies with policies.
+Submit the add-on for review through the Google Workspace Marketplace.
+Challenges
+Third-Party Website Restrictions: Many websites have anti-bot mechanisms like CAPTCHAs.
+Security Risks: Handling sensitive data like reset links and passwords can be risky.
+Policy Compliance: Automating actions like password resets may lead to the rejection of your add-on.

package/.vscode/ntrsync/10506_container home - build mats.md

@@ -0,0 +1,18 @@
+# container home - build mats
+
+Mini split system 8000 installed
+Shipping containers 4000 each
+ Build your own kitchen 
+Counters, flooring, cabinet doors,  do same as desk but with no color and proper burner
+Pot lights for lighting 
+On demand water heater 5000 
+Electrician 4000
+Meral studs or wood studs
+Foundation 5000
+
+Ideas 
+Kitchen and bathroom downstairs that way all water is on in one container with living bedroom upstairs
+Dark natural stone for shower and sink 
+Japanese burn method for floors counter tops stairs cabinet doors with polyurethane instead of swing doors do barn doors with same style 
+
+Can we get away with solar panels as far as cost goes? 

package/.vscode/ntrsync/10507_cleint facing site meta and loader function.md

@@ -0,0 +1,25 @@
+# client facing site meta and loader function
+
+client_facing_site_meta_and_loader_function
+import  { type LoaderFunction, type MetaFunction, json } from '@remix-run/node';
+import { dealerSelection, fullUserSelection } from '~/utils/loader.server';
+import { prisma } from '~/libs';
+
+export async function loader({ request, params }: LoaderFunction) {
+    const d = await prisma.dealer.findUnique({ where: { id: 1 }, select: dealerSelection });
+    const URLS = { page: 'About Us' };
+    return json({
+        data: {
+            d: d,
+            URLS: URLS
+        }
+    });
+}
+
+export const meta: MetaFunction<typeof loader> = ({ data }) => {
+    const { d, URLS } = data;
+    return [
+        { title: `${URLS.page} - ${d.dealerName}` },
+        { name: "description", keywords: "Automotive Sales, dealership sales, automotive CRM, Service Center, Parts Department, Accessories Department, CRM, Dealership.", content: d.metaDesc, },
+    ];
+};

package/.vscode/ntrsync/10508_Sabaak VSCode 1-8 players - private teams, solo q, duos q.md

@@ -0,0 +1,11 @@
+# Sabaak VSCode 1-8 players - private teams, solo q, duos q
+
+- 1-8 players
+- match sizes 2, 4, 6, 8
+- private, invite only match servers
+- queue to play with random users from vscode
+- solo q
+- explorer views
+  - friends list
+  - create private 
+  - find public game 

package/.vscode/ntrsync/10509_schema dump.md

@@ -0,0 +1,80 @@
+# schema dump
+
+model Script {
+  id       String  @id @default(cuid())
+  name     String?
+  email    String?
+  content  String?
+  category String?
+  subCat   String?
+
+  createdAt DateTime @default(now())
+  updatedAt DateTime @updatedAt
+}
+
+model SalespersonSched {
+  id               String    @id @default(cuid())
+  createdAt        DateTime  @default(now())
+  updatedAt        DateTime  @updatedAt
+  day              String?
+  start            DateTime?
+  end              DateTime?
+  salespersonEmail String?
+  userEmail        String?
+  title            String?
+  resourceId       String?
+  userName         String?
+  userId           String?
+  name             String?
+}
+
+model DealerTasks {
+  id        String   @id @default(cuid())
+  createdAt DateTime @default(now())
+  updatedAt DateTime @updatedAt
+  dealerId  String? // DEV-1
+  title     String?
+  status    String?
+  priority  String?
+  userName  String?
+  userEmail String?
+  dept      String?
+  label     String?
+
+  DealerTasksUpdates DealerTasksUpdates[]
+}
+
+model DealerTasksUpdates {
+  id            String   @id @default(cuid())
+  createdAt     DateTime @default(now())
+  updatedAt     DateTime @updatedAt
+  update        String?
+  userName      String?
+  userEmail     String?
+  dealerTasksId String?
+  status        String?
+  priority      String?
+  label         String?
+
+  DealerTasks DealerTasks? @relation(fields: [dealerTasksId], references: [id])
+
+  @@unique([dealerTasksId])
+}
+model Automation {
+  id           String  @id @default(cuid())
+  userEmail    String?
+  type         String?
+  financeId    String?
+  clientfileId String?
+}
+
+model WorkOrderNotes {
+  id          String     @id @default(cuid())
+    createdAt   DateTime   @default(now())
+  updatedAt   DateTime   @updatedAt
+
+  body        String?
+  userName    String?
+  userEmail   String?
+
+}

package/.vscode/ntrsync/10510_APPT BEACONHILL_reminder.md

@@ -0,0 +1,7 @@
+# APPT BEACONHILL
+
+DUE: 2025-05-22 09:00
+
+613-580-2424 23855
+613-604-5183
+3222107414 may 22 09am beaconhill

package/.vscode/ntrsync/10512_clipboard very usefull should use asap within all apps.md

@@ -0,0 +1,101 @@
+# clipboard very usefull should use asap within all apps
+
+source https://github.com/remix-pwa/monorepo/blob/main/packages/client/lib/clipboard.ts
+import { errorBlock } from './utils.js';
+
+export const copyTextToClipboard = async (text: string): Promise<boolean> => {
+  try {
+    if (navigator && navigator.clipboard) {
+      await navigator.clipboard.writeText(text);
+      return true;
+    } else {
+      return false;
+    }
+  } catch (err) {
+    console.error(err);
+    return false;
+  }
+};
+
+export const readTextFromClipboard = async (): Promise<{
+  ok: boolean;
+  message?: string;
+  text: string | null;
+}> => {
+  try {
+    if (navigator && navigator.clipboard) {
+      const text = await navigator.clipboard.readText();
+      return { ok: true, message: 'Read text successfully', text };
+    } else {
+      return { ok: false, message: 'Read Text API not supported', text: null };
+    }
+  } catch (error) {
+    return { ok: false, text: null };
+  }
+};
+
+export const copyImageToClipboard = async (imgURL: string): Promise<boolean> => {
+  try {
+    if (navigator && navigator.clipboard) {
+      const data = await fetch(imgURL);
+      const blob = await data.blob();
+
+      await navigator.clipboard.write([
+        new ClipboardItem({
+          [blob.type]: blob,
+        }),
+      ]);
+
+      return true;
+    } else {
+      return false;
+    }
+  } catch (error) {
+    return false;
+  }
+};
+
+export const readFilesFromClipboard = async (): Promise<{ ok: boolean; message: string; files: File[] | null }> => {
+  try {
+    if (navigator && navigator.clipboard) {
+      const files = [] as File[];
+      const items = await navigator.clipboard.read();
+
+      for (const item of items) {
+        for (const type of item.types) {
+          const blob = await item.getType(type);
+          const file = new File([blob], 'clipboard-file', { type });
+          files.push(file);
+        }
+      }
+
+      return { ok: true, message: 'Read files from clipboard successfully', files };
+    } else {
+      return { ok: false, message: "Clipboard API not supported! Can't read files", files: null };
+    }
+  } catch (error) {
+    return { ...errorBlock(error), files: null };
+  }
+};
+
+export const clipboardSupported = async () => {
+  return navigator && 'clipboard' in navigator;
+};
+export function errorBlock(err: unknown) {
+  if (typeof err === 'string') {
+    return {
+      ok: false,
+      message: err,
+    };
+  } else if (err instanceof Error) {
+    return {
+      ok: false,
+      message: err.message,
+    };
+  } else {
+    return {
+      ok: false,
+      message: 'Unknown error',
+    };
+  }
+}