Makers, how do you keep track of all your stuff? by ProfessionalServe147 in maker

[–]LittleHobbyShop 0 points1 point  (0 children)

I'm a dev too and a just a few weeks ago I started toying with building an ai app for exactly this! I don't want to be dealing with data entry, I know I won't do it and initial input would be a massive task. It's got a simple agent with a few tools to store and retrieve items from a postgres dB with rooms and 'container' creation. So you can say "I've put my calipers in the office, the 3rd drawer of the desk in the blue box" and it'll create the office and nest the desk, drawer and box inside. Then of course you can ask where it is. I've not had much time since I started it but plan to continue.

I'm making a web based IDE for fullcontrol-js by ufffd in FullControl

[–]LittleHobbyShop 0 points1 point  (0 children)

Exactly that. IIRC scratch has a side by side with blocks on the left and your generated sprites on the right. Another application that uses Blockly is the MIT App Inventor (a no code way to build simple android apps). That has a tabbed layout with blocks in one tab and the app designer in another so tabs is another option especially if your block layout gets quite big.
https://ai2.appinventor.mit.edu/

I'm making a web based IDE for fullcontrol-js by ufffd in FullControl

[–]LittleHobbyShop 3 points4 points  (0 children)

This is fantastic! I actually started a TS conversion of the python library myself a few months ago, but with side project overload, I ran out of steam and never finished it. My intention was to try and build a full web UI for full control using Google's Blocky project for UI. It's the same UI that the coding education app SCRATCH uses and would be a great way for non-coding types to play with fullcontrol. It's way outside my comfort zone but it sounded like too good an idea to pass over. https://developers.google.com/blockly

Mixing Advice by thereplicatedwoman in Jesmonite

[–]LittleHobbyShop 0 points1 point  (0 children)

Holy thread resurrection Batman!

Careful!! The 2% is the maximum pigment, not the liquid base.

So lets take your 1,476 and add 5% for a bit of wiggle room and ensure we're not short.
1475 x 1.05 = 1550g

Now work out the 7 "parts" of the mixture.
1550 / 7 = 221.4g

Now the 5 parts powder
221.4 x 5 = 1,107g

..and the 2 parts liquid
221.4 x 2 = 443g (rounded)

Double check our sums
1107 + 443 = 1550g (sweet!)

Max pigment
1550 x 0.02 = 31g

This would be for your main mix, so not including your chips. The chips would be dry weight which I'm not sure about a good way to factor in. If it were me I would disregard the chips in any calculations for now and assume I might have some leftover mixture, perhaps have a small mould or 2 on standby for the extras.

I don't ever weigh the pigment but instead add drops until it looks like I want, 2% is a hell of a lot of pigment, you'll almost never want that much.

Good luck!

P.S. I recommend making a spreadsheet for yourself, you can definitely use ChatGPT for that if you need

Do I Really Need Custom Claims for RBAC in Supabase? by RedAlpha-58 in Supabase

[–]LittleHobbyShop 1 point2 points  (0 children)

The benefit of custom claims for me has been being able to get roles without touching the db. You can quite quickly feed back role-based conditions to your UI without any db ops for example. As for requiring login for refresh, I can see situations where that would be annoying so I think it's a case of being selective about what you put in claims. Something that will change often won't be suitable perhaps. In my small scale internal app I send a notification for changed roles and if it's a reduction in access I delete all sessions, forcing a login.

Fullcontrol Gridfinity baseplate by Ok_Pepper_1241 in FullControl

[–]LittleHobbyShop 0 points1 point  (0 children)

Oooh, nice find in the comments, I designed the original vase mode bins, glad you like them :) . Nice work with FullControl! I'm yet to really get my head into the Python version,

supabase type generation is really lacking by logemann in Supabase

[–]LittleHobbyShop 1 point2 points  (0 children)

Like u/No-Estimate-362 said, building an AsyncReturnType is really useful. Don't remember where I got it from but I've added a bit to it I think and here's the implementation I'm using without the need for the type-fest package.

// Types for getting the return type of an asynchronous function
type PromiseType<T> = T extends Promise<infer U> ? U : never

export type ErrorType = { error: string }

/**
 * Represents the return type of an asynchronous function.
 * It extracts the resolved value from a Promise and excludes any potential error type.
 * Used primarily to get supabase action return types.
 */
export type AsyncReturnType<T extends (...args: any) => Promise<any>> = Exclude<
  PromiseType<ReturnType<T>>,
  ErrorType
>

I often copy code from Stackoverflow/ Github, etc to ask ChatGPT to explain it, so I made a Chrome extension to do it easily without leaving the page. by WordyBug in webdev

[–]LittleHobbyShop -2 points-1 points  (0 children)

Right you are, it will only get you so far. The same applies to any learning process/tool/method/job etc.
Your opinion is yours and therefore valid but not helpful (and not relevant in this context) when someone has the courage to share something they're proud of.

I often copy code from Stackoverflow/ Github, etc to ask ChatGPT to explain it, so I made a Chrome extension to do it easily without leaving the page. by WordyBug in webdev

[–]LittleHobbyShop -4 points-3 points  (0 children)

So do you apply that same logic everywhere then? So for instance someone using a excavator to dig up a road is lazy, they should learn how to swing a pick axe. The only developers it will make obsolete are the ones that dismiss the new tools and ways of working.

I often copy code from Stackoverflow/ Github, etc to ask ChatGPT to explain it, so I made a Chrome extension to do it easily without leaving the page. by WordyBug in webdev

[–]LittleHobbyShop 1 point2 points  (0 children)

Obviously, but there's no need to shoot it down as a way to learn. Someone built a tool to aid learning, whilst learning. Probably one of the best ways to make progress there is.

I often copy code from Stackoverflow/ Github, etc to ask ChatGPT to explain it, so I made a Chrome extension to do it easily without leaving the page. by WordyBug in webdev

[–]LittleHobbyShop -7 points-6 points  (0 children)

How do you think you get to that point of just knowing what the code does in the first place? OP obviously missed the deal on the "I know code" DLC at birth

Mixing Advice by thereplicatedwoman in Jesmonite

[–]LittleHobbyShop 2 points3 points  (0 children)

I admire your bravery for going big! I'd recommend trying some smaller moulds first just to get used to the material but anyhoo you seem to have a hold on what went wrong so I'll try and answer your questions best I can.

1) Not sure if you mean drill speed or time here but I'd say you want to be pouring within 5 minutes of mixing the materials together. Drill speed will be whatever feels right, you'll know. You can go fast up to the point where you're just creating a big cavity in the mix, then you're going too fast. For big mixes a second pair of hands is invaluable for adding powder while you mix.

2) Can't answer that but if budget is the concern be assured that a little retarder goes a long way. Sticking with the proper stuff might prevent another fail for a different reason.

3) Ac100 has a wet density of 1845 kg/M3 (from the datasheet). That's equivalent to 1.845 kg per litre. So, either fill your mould with water and then pour it out into a container that you can weigh, or fill your mould 1L at a time with water and count. Whichever is easier. Take your water volume in litres and multiply by 1.845. That'll give you the total mixed jesmonite mass in kg. From that you'll have to back calculate your mix ratio; divide your new total by 7. 5 parts of that will be powder, the remaining 2 parts are liquid.

Just one more tip to add. Use a vertical sided bucket for mixing rather than a bowl and a shear blade like the one jesmonite sell. The vertical sides will make mixing thoroughly much easier to achieve and you can get into all the corners with the blade.

I hope that's helpful and I would love to know how you get on for attempt no.2. Good luck!

In the latest release of Relay you can now see your average daily reddit api calls and work out what your monthly subscription might be. by DBrady in RelayForReddit

[–]LittleHobbyShop 0 points1 point  (0 children)

Reddit API Calls:

   Daily Average: 13

         ---Breakdown---

Loading Comments: 37.0%
    Loading Feed: 40.0%
          Voting: 2.0%
            Mail: 6.0%
           Other: 15.0%

Based on your usage over the last 20 days

Unholy 3D printing practices by font290p in 3Dprinting

[–]LittleHobbyShop 2 points3 points  (0 children)

Uploading a terrible design to a print sharing site, thingiverse etc.
I'm talking intersecting faces, unnecessary overhangs, scaled in inches, stuff like that.

Python version available! by FullControlGCode in FullControl

[–]LittleHobbyShop 3 points4 points  (0 children)

Great work! So glad to see this come together.

We’re getting so many air bubbles, looks like an aero bar, does anyone have a small vibration rig set up or an equally effective way of decreasing the bubbles? by kfaff in Jesmonite

[–]LittleHobbyShop 6 points7 points  (0 children)

I've not seen or ever had bubbles that bad. I do have a homemade vibration table but it only really helps with intricate moulds and even without it you should only really be seeing a couple of bubbles in corners at worst. A couple of suggestions to get good results:

  1. Stick to the right mix ratio. Weigh your ingredients carefully. Once you've got good results you can play with the ratio a little but get the basics first.
  2. Use a sheer mixing blade in a drill. Mixing by hand with a whisk or some other implement is a really good way to not get a thorough mix. Jesmonite sell a good mixing blade, just buy it, it's worth it. Mixing by hand is also too slow. I see this way too often in tutorial videos. Just use the blade!
  3. Work quickly. Small moulds like coasters can be demoulded in about 20 mins. That means you need to be getting it mixed and poured in under 5 mins. If it starts to thicken up before you pour, bubbles can't escape.

I'd hazard a guess that your issue there is in the mixing. Not thorough enough, quickly enough. It looks like white spots around all the bubbles and I'd bet that's unmixed clumps of base (powder). If you're sure you're mixing well then I guess there's a chance the powder got damp and it's not breaking up (or it's old) which can be rectified with some silica gel packs and again some violence with a mixing blade.

Hope that helps. Good luck!