I think a "coding for Gemini" or "setting up Gemini" subspace would be beneficial. I remember @tomasino having some good intro videos. this might be a good place to discuss? I'd make it but I'm not a coder nor have time to moderate.

🍀 gritty

2023-05-17 · 1 year ago · 👍 skyjake, Addison, deathbyindierock

5 Comments ↓

👻 sirwilburthefirst · 2023-05-17 at 17:19:

There is a Gemini subspace already. I think this type of content would be great to go there.

🍀 gritty [OP] · 2023-05-17 at 17:22:

@sirwilburthefirst true but there's going to be a lot of philosophical discussions about Gemini in there that don't deal with coding or setup/maintenance of a capsule or service... e.g., specification changes. but I agree, could be a good place to start.

👻 sirwilburthefirst · 2023-05-17 at 17:31:

@gritty Yeah I understand. It's always hard to figure out how to best structure message boards. You want to avoid too many boards which causes each board to feel empty. But you also don't want discussions to be buried because a board is too broad.

I think it's best to start with more general boards and then split them up when/if it gets too noisey. I could definitely see a /r/HowToGemini being a thing.

Of course this is all just my opinion.

🕹️ skyjake [...] · 2023-05-17 at 19:13:

Yeah I think s/Gemini should nicely for both developer topics and capsule setup & maintenance. With the DIY-ness of Gemini it's usually a bit of both.

I'll update the description to mention this, since I left the purpose a bit vague when creating the subspace.

🐵 cquenelle · 2023-05-18 at 05:25:

There is a little voice in the back of your head @gritty. It says: But it would be better to organize the topics correctly from the start, otherwise when things change you’ll have topics split in different areas. I have that voice too. But it’s not your friend. :-) Social behavior is wildly dynamic and unpredictable. The Good lies in a system that fluidly manages the stream of new topics and threads and reacts to what people want in the moment.