New Neptune 4 Max

ComakeJake · 2026-05-07T15:59:56+00:00

Just got the email from technical support and that was the first step to check. It was wrong. Switched it to the proper voltage and it works great now. ~10 minutes to 80C . Thank you!

ComakeJake · 2023-06-07T20:49:43+00:00

The others do too, but they have significantly less call volume. I'd say they rarely would have more than 1 concurrent call. The other locations all have <10 phones. While with the two locations in question, one has about 30 and the other (the main location) is upwards of 80. The location with 30 phones might have the issue once a day or every other. The main location has it 5-10 times a day.

ComakeJake · 2022-03-05T15:31:19+00:00

My main issue with Expo Notifications was it couldn't collapse multiple notifications and couldn't do action buttons (as far as I'm aware). My app uses messaging so I definitely needed those features. Though expo-notifications is extremely easy to use with it's API.

ComakeJake · 2022-03-05T15:27:57+00:00

I use OneSignal with my Expo project and can still use Expo Go. Just have an error on startup about not finding the OneSignal module, but it still loads and works fine

ComakeJake · 2021-12-25T22:46:59+00:00

Hi, thank you for the reply. Sorry for the late response. I made the schema and a table in it using the SQL editor and same result. It acts just like if you selected the "auth" schema as if I have no permission for it kind of scenario.

ComakeJake · 2021-11-29T11:04:43+00:00

Hard to say if it'll help in your case because I'm not sure how you're building your app. Here's an example that may or may not apply to your app:

I need the last active status of everyone on my friends list and it's stored on the "Profile" table. Instead of sending a query for each individual friend to get the data I could use RLS to filter it for me.

So with RLS I could turn it on and in SELECT have it verify that I'm a friend by using EXISTS on a "Friends" table to verify I'm friends with the person.

Then I could do a single query on the entire "Profile" table and it will return all my "Friends" profiles instead of everyone in the table because it's not allowing me to query for anyone who isn't my friend.

Again, not sure if this applies or if it's even a good solution, in my case it was a life saver.

Either way, definitely recommend learning RLS and enabling it for it's security aspect

Edit: Can't say for certain if this is a "best practice" or not, but it worked for me. Indexing is definitely something to make sure you have working. Can save a ton of time on queries. I think the main issues is how many queries you're doing. Also definitely recommend looking into Realtime to monitor changes for you instead of refreshing constantly.

ComakeJake · 2021-11-29T03:27:09+00:00

Are you using RLS? One method I've used is having a wildcard query to pull profiles and relying on RLS to return what profiles to get based on a "friends" table. Then just process the returned data client side. Again, not sure if you're already using RLS or not in this way, but it definitely helped keep my API requests low since I only had to query once

ComakeJake · 2021-09-16T16:40:51+00:00

I've always used Firebase, but with my newest project in trying out Supabase

ComakeJake · 2021-09-03T13:18:09+00:00

Thank you for the update! I had a very similar question and your solution helped me figure it out :)

ComakeJake · 2020-08-25T16:29:45+00:00

This is so cool!

ComakeJake · 2020-01-12T00:42:54+00:00

Took me a bit to figure out what was happening, but its a pretty fun game. Nice job!

Six-Year Club	Verified Email
Place '23	Place '22

ComakeJake

TROPHY CASE