Looks awesome

Good job

Have you considered force carbonating? Its always consistent.

Great looking carbonation

That sounds yummy and I bet it would come out a beautiful color

I’ll be watching for your post!

Get the pulp and make it! It’s really unique

I do just mango a lot, its one of the best.

https://buchabrewers.com/spiced-apple-pie-kombucha/

I usually use real fruit but not with ginger

I used a juice extract for this one so i can’t give you a great answer

Not too much you want it to be in the background versus the foreground.

I followed this recipe:

https://buchabrewers.com/pumpkin-spice-kombucha-recipe/

I made only a half batch incase i didn’t like it. I followed the recipe exactly and wouldn’t change anything BUT let me warn you, you will need to filter when pouring into a glass to drink, and it blocked my filter making this a little difficult due to the pumpkin puree. I do not strain any kombucha but it was needed to drink this properly.

I let them go for 1-2 weeks before refrigeration which seems to be longer than most people, but i like strong carbonation so i aim to over do it vs under do it.

6.75 bottles

Looks good, how sweet versus tart was it?

Do it and share it with friends and family! You will never regret it. Once you start and get the hang of things it’s easy and flexible.

Ok thank you!

Im a little knowledgeable with this stuff but i do not know how to see the “handshake” itself, but maybe this is synonymous with what i am doing:

Right click any of the packets (TCP or SSH) > Follow > TCP stream

From there i can see some info about the ssh protocol and connection, as well as the 2 devices communicating (Operating systems used) followed by random gibberish which is the encrypted data.

When I analyze the TCP packet “frames”, they contain data including the motherboard manufacturer, but packets themselves look like its just gibberish.

Thanks by the way for trying to help me :)

It looks like everything is in 1 stream, maybe that answers your question? I am capturing traffic only on port 22 briefly while the rsync is running to look at the packets