The author’s point is that, even if you are correct 100% of the time, fighting every battle is toxic to yourself and everyone around you.

They are saying to look past the fact that you might be right and consider that it’s not worth the effort anyway.

Now, I will attempt to put down my phone and not respond to any replies I get to the contrary.

Sweating intensifies…

The IM portion was simple logic but the real-time voice was a challenge back then because audio compression was in its infancy. The few real-time compression libraries that existed were expensive to license and some even required royalties. Way out of my league.

At the same time, writing a compression algorithm myself was beyond my abilities. There weren't any VHS courses on that topic yet haha.

My solution was to use the recording control that came with VB6. I couldn't set the audio bitrate with that control but, if I had the recorder append the recording to an existing file, it would use the bitrate defined in that existing file.

So I created a teeny tiny wave file with 0 seconds of audio, included it with the program binary, and used a copy of it to seed & set the bitrate of each conversation.

Since they weren't compressed, the file integrity was very forgiving. I was able to pull out a chunk of data from anywhere in the audio file, put it into its own file, and it would play the extracted chunk of audio just fine.

So, that's what I did. I used the VB6 recording control with my low bitrate seed file to record their voice, had my code grab 1 second chunks of audio from that file, "stream" it to the other end of the line, write the data to disk, and use another VB6 control to play it for the recipient.

Surprisingly, the sound wasn't choppy at all. The audio quality was low, since the bitrate was in the low dozens but the conveyer belt of 1 second wave files being played back to back to back was not noticeable at all.

Ended up selling a bunch of copies.

Fun times =D

One day, I happened to read an article that said they were given a free copy of VB6 to review for the magazine.

My 17yo mind was blown! Hundreds of dollars worth of software given away for free? Just for writing an article?! I could do that!

Having nothing to lose, I called Microsoft's PR department and requested a copy. Told them I published a newsletter about computers and was based in Queens, NY. Their only question? Where should they send the software lol

It was literally that easy. A single phone call with zero verification about me, my newsletter, and my so-called publishing company.

And it was Enterprise edition which retailed for over $1,000. For little 17yo me!

Naturally, I kept calling for more software. Office, Windows 98/NT, Encarta... you name it.

I even started calling other companies and published a single edition of the newsletter, in case anyone asked for a copy but no one ever did. All they wanted to know was where they should send the software.

One of my favorite free items was course on VB which came on 6 VHS cassettes. The lessons I learned from those tapes built the foundation of my programming carrier.

Of course, older me understands the economics of sending people a few bits of plastic & paper in exchange for press coverage but the joy I felt getting that software in the mail still hasn't left my mind.

Good times =D

https://en.wikipedia.org/wiki/Reduced-gravity_aircraft

I occasionally get spam from people who took the time to create gmail accounts. Based on this advice, the honey pot email address would get spam from a Gmail account and your script would block Gmail servers.

At low levels, playing is ABC simple and mostly about following basic strategy for starting hands and pot adds for chasing. Don’t get fancy and keep your temperament steady and you’ll win.

To a slight degree, you can do better with reading players and identifying them in broad ways (wild, conservative, confused, etc.) but don’t let that allow you to get fancy. Stick to the basic fundamental strategy for hands, position, and pot odds to crush lower level games.

With regards to the software, it is open source but OP is only providing the code to customers who receive the end product. In part, OP is acting as a distributor of the software and is charging a fee for that distribution.

If anyone else gets their hands on that software, they can choose to become a distributor and make it publicly available. It’s their freedom to do so.

A overly simple way to look at is is that OP is choosing (as a small part of their business) to charge for the distribution of the source code but not the source itself.

In reality, it’s unlikely that OP will have a customer who only wants the source code and is willing to pay a fee for the distribution of it. Their customers are coming to them for the service and support.

Bill pay sends a bank check which is covered by the immediate withdrawal of funds from the customer’s account. In most cases, the customer would be fine with that or even prefer it, to ensure they don’t accidentally bounce a check.

However, I’m wondering if another customer base can be someone who has bank bill pay but wants to float the funds until the check is cashed. Maybe they don’t have the actual funds yet but want to write a check against funds they expect to have soon (risky but people do it).

Do you restrict writing checks that are for an amount greater than the current account balance?

Lastly, I’m wondering how you handle deliberate check fraud. Victims will try to sue all associated parties. How does your liability work in those cases?

Things that are considered small can still have variations in the extent of their smallness.

-GP

> The point GP is making is that DJI does not indiscriminately upload every video.

-You

That seems to be exactly what GP is claiming could be happening.

They were concerned about “every second of video” which would fit the definition of “indescribably”.

I checked your source and it didn’t back up this claim.

I’m not a networking specialist but isn’t it possible to detect if something is transmitting a massive amount of data (such as video) to an undetermined destination?

seems like this type of blatant data export would be easy to detect and subsequently ban the device doing it.

I’m just a simple software developer, so the network stuff can go over my head sometimes (heh), but the claim that such a large amount of data is being transmitted in a way that couldn’t be confirmed enough to ban the product seems dubious.

They’re chipped, cracked, and bent. That’s anything but happy.

I bet the balloon and, more importantly, the payload would indeed faze it.

It’s tough to share many of the other steps I’ve taken on a public forum. Honestly, I doubt they’d be as helpful as my previous comment because they’re so personal. Because they are so specific to me.

However, I can share that group therapy is the main resource I used to take those steps. I highly recommend it.

What’s nice about group is that I get to hear various perspectives on a situation. Everyone there has gone through somewhat similar struggles but their interpretations of those struggles are different.

As each person speaks, I find a nugget of wisdom that I can use. A bit of insight that I wouldn’t realize on my own. A phrase that finally helps a concept click in my head.

Of course 1-on-1 therapy is helpful too but group is a treasure trove of insight for personal growth.

The conversation is imaginary but the emotions are real.

I used to think my ability to deep dive situations was a superpower but it’s really a curse.

Thankfully, I’m learning to shed the worst of it.

Hope you can too.

I’d often think about social interactions ahead of time. My brain would create countless situations that I’d play out. Once I exhausted one situation, I jump into analyzing the next possible situation. On and on I’d go.

I’ve only recently been able to quiet down my beehive brain a bit thanks to a few realizations I came to about the damage it was doing to me:

- Even after analyzing 100 different possibilities, reality would often be much different than the scenarios I thought about.

- When the situation didn’t play out exactly as I’d imagined, I’d still react instantly without thinking through the new variances. In my foolishness, the unexpected scenario seemed close enough to the ones I had already thought about, so I’d respond off the cuff.

In reality, things were different enough that a pause to think would’ve been better.

- Thinking through 100 different scenarios also meant going through the emotional baggage that came with them. In my mind, sometimes people reacted positively and sometimes negatively.

Imagining all the negative ways someone could react would lead me to attributing negative feelings to them, even though they haven’t responded negatively.

On the flip side, if I attributed a specific positive outcome to someone that didn’t live up to my exact interpretation, I’d end up feeling disappointed with an outcome I should’ve been happy with.

- Lastly, I’d push to resolve a situation immediately because I didn’t want to go through another beehive of scenarios while waiting to continue the conversation another time.

Sometimes that push to resolve the conflict resulted in a positive breakthrough. However, other times the person would agree to a certain resolution due to sheer exhaustion which leave us with an unsustainable outcome.

Of course, there were other things that helped calm my brain down. Things that helped me take a step towards these realizations and act on them.

Hopefully, my comment can be one of those steps for someone else.