100% Apple Native ChatGPT client for OpenAI built using SwiftUI.

Use **your OWN account and API key** and stop paying for crazy markups of other apps.

### Features:
- Use your own OpenAi Account, not ours.
- Unlimited conversations stored locally on your device only.
- Personas: choose from pre-made chat templates
- 100% Native Apple-only
- Universal: works on iPhone and iPad (Mac coming soon)
- Per-chat settings
    - Choose model, system message, custom prompt, creativity (temperature) settings 
- Uses latest APIs from OpenAI (gpt-3.5-turbo, GPT4)
- Choose default settings for new conversations
- Adjust display settings
- Light/dark mode
- Token estimation and more message actions coming soon

Much more to come.

[Get it here](https://apps.apple.com/us/app/chatai-unlimited-ai-chats/id6446180384) 

[![Download_on_the_App_Store_Badge_US-UK_RGB_blk_092917](https://user-images.githubusercontent.com/390996/226219355-7c135ea4-c2fb-458f-85c1-3f351ddad84a.svg)](https://apps.apple.com/us/app/chatai-unlimited-ai-chats/id6446180384)


<p dir="auto">100% Apple Native ChatGPT client for OpenAI built using SwiftUI.</p>
<p dir="auto">Use <strong>your OWN account and API key</strong> and stop paying for crazy markups of other apps.</p>
<h3 dir="auto">Features:</h3>
<ul dir="auto">
<li>Use your own OpenAi Account, not ours.</li>
<li>Unlimited conversations stored locally on your device only.</li>
<li>Personas: choose from pre-made chat templates</li>
<li>100% Native Apple-only</li>
<li>Universal: works on iPhone and iPad (Mac coming soon)</li>
<li>Per-chat settings
<ul dir="auto">
<li>Choose model, system message, custom prompt, creativity (temperature) settings</li>
</ul>
</li>
<li>Uses latest APIs from OpenAI (gpt-3.5-turbo, GPT4)</li>
<li>Choose default settings for new conversations</li>
<li>Adjust display settings</li>
<li>Light/dark mode</li>
<li>Token estimation and more message actions coming soon</li>
</ul>
<p dir="auto">Much more to come.</p>
<p dir="auto"><a href="https://apps.apple.com/us/app/chatai-unlimited-ai-chats/id6446180384" rel="nofollow">Get it here</a></p>
<p dir="auto"><a href="https://apps.apple.com/us/app/chatai-unlimited-ai-chats/id6446180384" rel="nofollow"><img src="https://user-images.githubusercontent.com/390996/226219355-7c135ea4-c2fb-458f-85c1-3f351ddad84a.svg" alt="Download_on_the_App_Store_Badge_US-UK_RGB_blk_092917" style="max-width: 100%;"></a></p>

100% Apple Native ChatGPT client for OpenAI built using SwiftUI.
Use your OWN account and API key and stop paying for crazy markups of other apps.
Features:

Use your own OpenAi Account, not ours.
Unlimited conversations stored locally on your device only.
Personas: choose from pre-made chat templates
100% Native Apple-only
Universal: works on iPhone and iPad (Mac coming soon)
Per-chat settings

Choose model, system message, custom prompt, creativity (temperature) settings


Uses latest APIs from OpenAI (gpt-3.5-turbo, GPT4)
Choose default settings for new conversations
Adjust display settings
Light/dark mode
Token estimation and more message actions coming soon

Much more to come.
Get it here

https://github.com/pbassham/philbassham.com/issues/41#issue-1628108128

published

post

projects

SwiftUI

Done

Personal Project

https://user-images.githubusercontent.com/390996/225727818-66ae0617-6bc4-4315-af69-46cdab9d4fe7.png

philbassham.com

A Native ChatGPT Client for Apple Devices

ChatAi - 100% SwiftUI

## Why Github _Issues_?
I have implemented a unique system that uses GitHub issues as a content management system (CMS) for my website.

Ok, I know that seems like the wrong tool for the job, but hear me out. 

I had several goals for my website:
1. Free to host - this site doesn't make money, so I don't want it to cost.
2. Fast
3. Maintenance free-ish 

I went through several iterations:
1. Wordpress - not fast or free
2. Next.js site + self-hosted Strapi instance. - I have enough to maintain, and I didn't really like Strapi. 
3. Next.js + markdown files directly in the GitHub repo. - It was ok, but I didn't really like having to open up VSCode to edit my site. 
4. Next.js + NetlifyCMS - free, and gave a user interface to writing markdown files, but too clunky and too much rebuilding. And didn't really work on mobile. 
5. Next.js + Obsidian - tried writing and organizing separately in Obsidian, but publishing was still a pain. 
5. Next.js + GitHub issues = 
    - [x] Benefits of a hosted CMS 
    - [x] Unlimited users
    - [x] Edit history of posts
    - [x] Reactions 
    - [x] Comments
    - [x] Project Management tools
    - [x] Create lots of Content views 
    - [x] Visualize Content strategy
    - [x] Free Image Hosting
    - [x] Free


### Project management features
Writing for a site is a project, and I was frustrated with trying to organize my thoughts and writing plans for this site. I wanted the project management features of [Github Projects](https://github.com/features/issues), but didn't want to keep my content and take management in separate places. I didnt just want to write articles in isolation, but have a way to _plan_ out writing and _visualize_ the progress.



#### Sprint Planning
I wrote down a lot of ideas, did some sprint planning for myself, and now I am just working through my current spring.

![Image](https://user-images.githubusercontent.com/390996/212415329-736dd746-cc10-4562-8307-ece7914dbeba.png)


And I also wanted to remove the friction between planning and publishing, and Github Projects lets me write directly on the project board.

I like that I can visualize my content in many different ways, it helps me to focus on one task at a time, but also be able to see the big picture.

For instance, here is how I am writing this post right now. Directly when inspiration hits in the planning phase, and I feel that I have an idea for what I want to say. Just click on an item on the task board, and quickly edit away.


![Image](https://user-images.githubusercontent.com/390996/212206330-996b2652-5bc1-4bae-b39c-b373a10f157f.png)

### Content and actual issues (bugs, enhancements, etc) in one system.

Since this is just my site, having a mix of dev-type tasks and writing tasks makes sense. But could easily keep the separate in a separate project.

One of the great benefits of using GitHub issues as a CMS is that I can create different views in the project platform, effectively making task management and content management the same thing, eliminating friction in the publishing process. This allows me to easily visualize and organize the work of writing, making sure that everything is communicated effectively. I can also use custom fields in the project software for metadata of the post, like adding a post title, author, and post date for example.


### Publishing
This website is built using Next.js, and utilizes incremental static regeneration (ISR). This means that it is a static site (fast) and is only built and rebuilt when I edit the theme or functionality, not on every little page edit.



### Metadata

Another advantage of using GitHub issues is that I can use labels as tags. This means that I can easily categorize and organize my content, making it easy for me to find and update specific pages.

I can even view it in table view to make sure every post has all of the fields it is supposed to.
![Image](https://user-images.githubusercontent.com/390996/212421668-e78774d6-7cce-4e7f-849f-2b36a37c99da.png)

### Image Hosting
Finally, I also addressed the issue of image hosting. By using GitHub's built-in image hosting capabilities, I am able to host all of our website's images directly on the platform, eliminating the need for a separate image hosting service.

Overall, using GitHub issues as a CMS has been a great solution for me. It has not only streamlined my content management process, but it also allows me to easily brainstorm and plan information.


## How it works

You can read more on the [README of the GitHub repo](https://github.com/pbassham/philbassham.com), but in summary:

1. Next.js that generates a static, server-side rendered page.
3. [Github Action that makes slugs for issues](https://github.com/pbassham/slugify-issue) - Auto-runs on every New or updated issue to make sure the slugs are always up-to-date (there are no slugs for issues)
  4. [Cloudflare Key-Value Store](https://www.cloudflare.com/products/workers-kv/) - Allows fetching the GitHub issue by a slug without a rebuild 
5. Hosted on Vercel 
6. Custom fields from a Github Project are available to use as page/post metadata. Can also be overridden with front matter, but I dont like front matter and wanted to see my metadata in the CMS.  
Fork it on [GitHub](https://github.com/pbassham/philbassham.com) and try it for yourself!




<h2 dir="auto">Why Github <em>Issues</em>?</h2>
<p dir="auto">I have implemented a unique system that uses GitHub issues as a content management system (CMS) for my website.</p>
<p dir="auto">Ok, I know that seems like the wrong tool for the job, but hear me out.</p>
<p dir="auto">I had several goals for my website:</p>
<ol dir="auto">
<li>Free to host - this site doesn't make money, so I don't want it to cost.</li>
<li>Fast</li>
<li>Maintenance free-ish</li>
</ol>
<p dir="auto">I went through several iterations:</p>
<ol dir="auto">
<li>Wordpress - not fast or free</li>
<li>Next.js site + self-hosted Strapi instance. - I have enough to maintain, and I didn't really like Strapi.</li>
<li>Next.js + markdown files directly in the GitHub repo. - It was ok, but I didn't really like having to open up VSCode to edit my site.</li>
<li>Next.js + NetlifyCMS - free, and gave a user interface to writing markdown files, but too clunky and too much rebuilding. And didn't really work on mobile.</li>
<li>Next.js + Obsidian - tried writing and organizing separately in Obsidian, but publishing was still a pain.</li>
<li>Next.js + GitHub issues =
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Benefits of a hosted CMS</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Unlimited users</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Edit history of posts</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Reactions</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Comments</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Project Management tools</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Create lots of Content views</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Visualize Content strategy</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Free Image Hosting</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> Free</li>
</ul>
</li>
</ol>
<h3 dir="auto">Project management features</h3>
<p dir="auto">Writing for a site is a project, and I was frustrated with trying to organize my thoughts and writing plans for this site. I wanted the project management features of <a href="https://github.com/features/issues">Github Projects</a>, but didn't want to keep my content and take management in separate places. I didnt just want to write articles in isolation, but have a way to <em>plan</em> out writing and <em>visualize</em> the progress.</p>
<h4 dir="auto">Sprint Planning</h4>
<p dir="auto">I wrote down a lot of ideas, did some sprint planning for myself, and now I am just working through my current spring.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/390996/212415329-736dd746-cc10-4562-8307-ece7914dbeba.png"><img src="https://user-images.githubusercontent.com/390996/212415329-736dd746-cc10-4562-8307-ece7914dbeba.png" alt="Image" style="max-width: 100%;"></a></p>
<p dir="auto">And I also wanted to remove the friction between planning and publishing, and Github Projects lets me write directly on the project board.</p>
<p dir="auto">I like that I can visualize my content in many different ways, it helps me to focus on one task at a time, but also be able to see the big picture.</p>
<p dir="auto">For instance, here is how I am writing this post right now. Directly when inspiration hits in the planning phase, and I feel that I have an idea for what I want to say. Just click on an item on the task board, and quickly edit away.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/390996/212206330-996b2652-5bc1-4bae-b39c-b373a10f157f.png"><img src="https://user-images.githubusercontent.com/390996/212206330-996b2652-5bc1-4bae-b39c-b373a10f157f.png" alt="Image" style="max-width: 100%;"></a></p>
<h3 dir="auto">Content and actual issues (bugs, enhancements, etc) in one system.</h3>
<p dir="auto">Since this is just my site, having a mix of dev-type tasks and writing tasks makes sense. But could easily keep the separate in a separate project.</p>
<p dir="auto">One of the great benefits of using GitHub issues as a CMS is that I can create different views in the project platform, effectively making task management and content management the same thing, eliminating friction in the publishing process. This allows me to easily visualize and organize the work of writing, making sure that everything is communicated effectively. I can also use custom fields in the project software for metadata of the post, like adding a post title, author, and post date for example.</p>
<h3 dir="auto">Publishing</h3>
<p dir="auto">This website is built using Next.js, and utilizes incremental static regeneration (ISR). This means that it is a static site (fast) and is only built and rebuilt when I edit the theme or functionality, not on every little page edit.</p>
<h3 dir="auto">Metadata</h3>
<p dir="auto">Another advantage of using GitHub issues is that I can use labels as tags. This means that I can easily categorize and organize my content, making it easy for me to find and update specific pages.</p>
<p dir="auto">I can even view it in table view to make sure every post has all of the fields it is supposed to.<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/390996/212421668-e78774d6-7cce-4e7f-849f-2b36a37c99da.png"><img src="https://user-images.githubusercontent.com/390996/212421668-e78774d6-7cce-4e7f-849f-2b36a37c99da.png" alt="Image" style="max-width: 100%;"></a></p>
<h3 dir="auto">Image Hosting</h3>
<p dir="auto">Finally, I also addressed the issue of image hosting. By using GitHub's built-in image hosting capabilities, I am able to host all of our website's images directly on the platform, eliminating the need for a separate image hosting service.</p>
<p dir="auto">Overall, using GitHub issues as a CMS has been a great solution for me. It has not only streamlined my content management process, but it also allows me to easily brainstorm and plan information.</p>
<h2 dir="auto">How it works</h2>
<p dir="auto">You can read more on the <a href="https://github.com/pbassham/philbassham.com">README of the GitHub repo</a>, but in summary:</p>
<ol dir="auto">
<li>Next.js that generates a static, server-side rendered page.</li>
<li><a href="https://github.com/pbassham/slugify-issue">Github Action that makes slugs for issues</a> - Auto-runs on every New or updated issue to make sure the slugs are always up-to-date (there are no slugs for issues)</li>
<li><a href="https://www.cloudflare.com/products/workers-kv/" rel="nofollow">Cloudflare Key-Value Store</a> - Allows fetching the GitHub issue by a slug without a rebuild</li>
<li>Hosted on Vercel</li>
<li>Custom fields from a Github Project are available to use as page/post metadata. Can also be overridden with front matter, but I dont like front matter and wanted to see my metadata in the CMS.<br>
Fork it on <a href="https://github.com/pbassham/philbassham.com">GitHub</a> and try it for yourself!</li>
</ol>

Why Github Issues?
I have implemented a unique system that uses GitHub issues as a content management system (CMS) for my website.
Ok, I know that seems like the wrong tool for the job, but hear me out.
I had several goals for my website:

Free to host - this site doesn't make money, so I don't want it to cost.
Fast
Maintenance free-ish

I went through several iterations:

Wordpress - not fast or free
Next.js site + self-hosted Strapi instance. - I have enough to maintain, and I didn't really like Strapi.
Next.js + markdown files directly in the GitHub repo. - It was ok, but I didn't really like having to open up VSCode to edit my site.
Next.js + NetlifyCMS - free, and gave a user interface to writing markdown files, but too clunky and too much rebuilding. And didn't really work on mobile.
Next.js + Obsidian - tried writing and organizing separately in Obsidian, but publishing was still a pain.
Next.js + GitHub issues =

 Benefits of a hosted CMS
 Unlimited users
 Edit history of posts
 Reactions
 Comments
 Project Management tools
 Create lots of Content views
 Visualize Content strategy
 Free Image Hosting
 Free



Project management features
Writing for a site is a project, and I was frustrated with trying to organize my thoughts and writing plans for this site. I wanted the project management features of Github Projects, but didn't want to keep my content and take management in separate places. I didnt just want to write articles in isolation, but have a way to plan out writing and visualize the progress.
Sprint Planning
I wrote down a lot of ideas, did some sprint planning for myself, and now I am just working through my current spring.

And I also wanted to remove the friction between planning and publishing, and Github Projects lets me write directly on the project board.
I like that I can visualize my content in many different ways, it helps me to focus on one task at a time, but also be able to see the big picture.
For instance, here is how I am writing this post right now. Directly when inspiration hits in the planning phase, and I feel that I have an idea for what I want to say. Just click on an item on the task board, and quickly edit away.

Content and actual issues (bugs, enhancements, etc) in one system.
Since this is just my site, having a mix of dev-type tasks and writing tasks makes sense. But could easily keep the separate in a separate project.
One of the great benefits of using GitHub issues as a CMS is that I can create different views in the project platform, effectively making task management and content management the same thing, eliminating friction in the publishing process. This allows me to easily visualize and organize the work of writing, making sure that everything is communicated effectively. I can also use custom fields in the project software for metadata of the post, like adding a post title, author, and post date for example.
Publishing
This website is built using Next.js, and utilizes incremental static regeneration (ISR). This means that it is a static site (fast) and is only built and rebuilt when I edit the theme or functionality, not on every little page edit.
Metadata
Another advantage of using GitHub issues is that I can use labels as tags. This means that I can easily categorize and organize my content, making it easy for me to find and update specific pages.
I can even view it in table view to make sure every post has all of the fields it is supposed to.

Image Hosting
Finally, I also addressed the issue of image hosting. By using GitHub's built-in image hosting capabilities, I am able to host all of our website's images directly on the platform, eliminating the need for a separate image hosting service.
Overall, using GitHub issues as a CMS has been a great solution for me. It has not only streamlined my content management process, but it also allows me to easily brainstorm and plan information.
How it works
You can read more on the README of the GitHub repo, but in summary:

Next.js that generates a static, server-side rendered page.
Github Action that makes slugs for issues - Auto-runs on every New or updated issue to make sure the slugs are always up-to-date (there are no slugs for issues)
Cloudflare Key-Value Store - Allows fetching the GitHub issue by a slug without a rebuild
Hosted on Vercel
Custom fields from a Github Project are available to use as page/post metadata. Can also be overridden with front matter, but I dont like front matter and wanted to see my metadata in the CMS.
Fork it on GitHub and try it for yourself!

https://github.com/pbassham/philbassham.com/issues/24#issue-1531159848

Visualization

Automation

https://user-images.githubusercontent.com/390996/212197412-76b26bb0-df0c-455c-8702-92213a8ae7d1.png

Free CMS with image hosting, comments, reactions, and more.

Using Github Issues as a Content Management System (CMS)

---
excerpt: Full-featured email client (web-based) for Gmail that provides
  streamlined interface for easily managing Gmail filters and rules. Easily
  screen out senders that you dont want to hear from using the native power of
  Gmail filter rules.

---

Gmail Filter Manager is a web app that makes it easy to manage Gmail filters. The app uses the Gmail API to replicate features of popular email clients, but with a focus on leveraging the native filter features already built into Gmail. With Gmail Filter Manager, users can easily manage their filters and create a more efficient and organized email experience.

One of the key features of Gmail Filter Manager is the email screener. This view places all email from first-time senders in a separate folder, allowing users to easily identify and triage emails from unknown sources. This is particularly useful for avoiding spam and staying organized.

Another useful feature of Gmail Filter Manager is the "focus and reply" view. This view allows users to mark certain emails to reply to, and presents them in a list with the email on the left and reply box on the right. This layout makes it easy for users to quickly work through email replies without distraction.

In addition to these features, Gmail Filter Manager also includes a feed view that auto-expands email to be able to read newsletters and other informational emails like a feed reader. This makes it easy for users to stay up-to-date on important information without having to wade through cluttered inboxes.

Finally, Gmail Filter Manager also includes a filter manager view that provides an easy-to-use interface to see and manage every filter. This view allows users to quickly and easily see all of their filters and make changes as needed.

Gmail Filter Manager is a powerful and user-friendly tool for managing Gmail filters. The app demonstrates skills in web development, API integration, and user experience design.

<hr>
<p dir="auto">excerpt: Full-featured email client (web-based) for Gmail that provides<br>
streamlined interface for easily managing Gmail filters and rules. Easily<br>
screen out senders that you dont want to hear from using the native power of<br>
Gmail filter rules.</p>
<hr>
<p dir="auto">Gmail Filter Manager is a web app that makes it easy to manage Gmail filters. The app uses the Gmail API to replicate features of popular email clients, but with a focus on leveraging the native filter features already built into Gmail. With Gmail Filter Manager, users can easily manage their filters and create a more efficient and organized email experience.</p>
<p dir="auto">One of the key features of Gmail Filter Manager is the email screener. This view places all email from first-time senders in a separate folder, allowing users to easily identify and triage emails from unknown sources. This is particularly useful for avoiding spam and staying organized.</p>
<p dir="auto">Another useful feature of Gmail Filter Manager is the "focus and reply" view. This view allows users to mark certain emails to reply to, and presents them in a list with the email on the left and reply box on the right. This layout makes it easy for users to quickly work through email replies without distraction.</p>
<p dir="auto">In addition to these features, Gmail Filter Manager also includes a feed view that auto-expands email to be able to read newsletters and other informational emails like a feed reader. This makes it easy for users to stay up-to-date on important information without having to wade through cluttered inboxes.</p>
<p dir="auto">Finally, Gmail Filter Manager also includes a filter manager view that provides an easy-to-use interface to see and manage every filter. This view allows users to quickly and easily see all of their filters and make changes as needed.</p>
<p dir="auto">Gmail Filter Manager is a powerful and user-friendly tool for managing Gmail filters. The app demonstrates skills in web development, API integration, and user experience design.</p>

excerpt: Full-featured email client (web-based) for Gmail that provides
streamlined interface for easily managing Gmail filters and rules. Easily
screen out senders that you dont want to hear from using the native power of
Gmail filter rules.

Gmail Filter Manager is a web app that makes it easy to manage Gmail filters. The app uses the Gmail API to replicate features of popular email clients, but with a focus on leveraging the native filter features already built into Gmail. With Gmail Filter Manager, users can easily manage their filters and create a more efficient and organized email experience.
One of the key features of Gmail Filter Manager is the email screener. This view places all email from first-time senders in a separate folder, allowing users to easily identify and triage emails from unknown sources. This is particularly useful for avoiding spam and staying organized.
Another useful feature of Gmail Filter Manager is the "focus and reply" view. This view allows users to mark certain emails to reply to, and presents them in a list with the email on the left and reply box on the right. This layout makes it easy for users to quickly work through email replies without distraction.
In addition to these features, Gmail Filter Manager also includes a feed view that auto-expands email to be able to read newsletters and other informational emails like a feed reader. This makes it easy for users to stay up-to-date on important information without having to wade through cluttered inboxes.
Finally, Gmail Filter Manager also includes a filter manager view that provides an easy-to-use interface to see and manage every filter. This view allows users to quickly and easily see all of their filters and make changes as needed.
Gmail Filter Manager is a powerful and user-friendly tool for managing Gmail filters. The app demonstrates skills in web development, API integration, and user experience design.

https://github.com/pbassham/philbassham.com/issues/12#issue-1527640631

Data

React

https://user-images.githubusercontent.com/390996/211601402-07932d9a-2126-462d-866c-b25f199b5bdf.png

Projects

Some things I worked on building.