2025 is getting close; here is what's in store for the new year!

Thanks for the info brother :pray:t2::heart:

My three main to-do’s right now are:

  • Upgrade core to 3.3 - This is major because there is a huge leap in tech from 3.2. Basically ALL our customizations had to be rewritten from scratch, and there is a lot of them (hence working since August).

  • Our 3.2 version is holding back many improvements we could implement in an hour, so 3.3 is first.

  • SpyTool is ready, just waiting for 3.3. This will greatly improve how business is made.

  • And last, seller success ratio. This needs to be done ASAP.

Once those things are finished (I predict one month, max), then we can start on everything else.

2 Likes

Consider Upwork (it’s free). But there’s lots of spam/ai replies. This is what I do:

At the end of the job listing, I add five qualifying questions:

  1. On a scale from 1-10, how would you rate your skills in (whatever your main programming language is)

  2. How many hours per day are you available?

  3. Are you ok with a starting salary of 250,000 PKR/month?

  4. We do not allow manual time. Are you ok using Upwork or a 3rd party service to track hours and have your screen monitored while working?

  5. In an effort to weed out bots and spam, please search “Developer” on Google, take a screenshot, and attach it to your message.

First, I weed out anyone who didn’t attach the screenshot. Next, I eliminate candidates who can’t work 8 hours a day. Finally, I filter out anyone who’s not okay with screen monitoring, and so on.

For applicants that look good, I hop on a call via their Zoom feature, hand them a quick test task (via google docs) without mentioning how long it should take, ask them to estimate the time needed, and then filter out anyone who says it’ll take more than a few hours or doesn’t do it correctly. Some will say “5 days or 10 days” when in reality it’s a 30 minute task.

Sometimes, but most of the time ticket numbers are not included and the text is vague. These are some from your profile:


Furthermore - as an example - you have 163 feedbacks, where only 43 have ticket numbers (26%). Therefore, a dedicated and required ticket number field should be included in the future :slight_smile:

1 Like

Admin feedbacks are completely irrelevant. Users like leaving them to us for managing their tickets at times, which is unnecessary but appreciated.

4 Likes

That doesn’t work for me. I have a feeling it doesn’t work for many others too, as I have heard of other users having the same problem I have when trying to copy the ticket number.

The ticket number is included in the subject of the ticket, and no where else. When I try and select the ticket number, it automatically selects a bunch of other text instead of just the ticket number. I’ve attempt this multiple times. I will be glad to screen record a video if you would like me to show you what I’m referring to.

I understand exchanges count as feedback, but maybe they could be labeled as Exchange Feedback, and not the same as Buyer/Seller Feedback… as essentially a new user could do a bunch of $20 - 30 exchanges, put privacy on their stats so it only shows the number of feedbacks left… and to a new buyer, they would appear as a trusted seller.

Not all buyers are aware they need to deep research the sellers they work with to ensure they’re suitable for whatever service they’re planning on buying, and will purchase just based on seeing that the person has multiple 5 star reviews.

1 Like

2 Likes

Users keep saying how annoying it is to copy ticket numbers. We all know where they are, but copying and pasting them isn’t easy. Even I struggle with it, and I’m on a computer most of the time—it always grabs extra words, which is super frustrating.

Why not have the bot include the ticket number in its final message on a separate line when it reminds users to leave feedback? It’d make things way simpler. No one wants to scroll through tens of messages to find the ticket number in the beep beep boop boop message :slight_smile:

2 Likes

Main USA exchange is Coinbase and they don’t support TRC.

We used to have binance.us but that got banned so not really a good option for TRC.

@enoz @immortals @GOAT

Struggled copying the ticket number for years until I discovered this trick.

Posted a guide below too along with videos :raised_hands:

4 Likes

Damn now I understand why many of my clients don’t use TRC.

1 Like

Thanks mate.

Crazy that is the first time I’ve seen the ticket number located there, despite all the times I’ve quickly looked it over. Thanks for visually pointing it out, as I even looked it over again after @Alpha mentioned it was there and still didn’t see it, which is my own fault for not thoroughly reading it.

It might not be a bad idea to put it in a paragraph by itself, or also in another location where it stands out more… and is also easy to copy, as I’m not the only person who has overlooked it in it’s current location… so it’s a probability other users who don’t read this, might continue to have the same problem in the future… as even @charizard said he struggled for years copying it.

Thanks for taking the time to create the guide along with videos… that was a nice gesture.

4 Likes

Would you be able and willing to incorporate the calculator as a widget on this page?

2 Likes

That’s a great idea :bulb:

2 Likes

Yas.

2 Likes

79 unread chats jeezeeeee :joy: my ocd is going boinkers

1 Like

Man is the goat on-site and doesn’t respond to some new rats or chicks trying to come along

3 Likes

Amazing suggestion @GOAT

1 Like

Haha. Told the exact same thing to someone else.


And, I agree with @enoz It’s hard to notice. Maybe, The Bot text need a revamp with the message somewhat changed to like…

“Beep beep, boop boop! Your ticket no is #123456 and I am the SWAPD Checkout BOT.”

2 Likes