For the record

Greg Loring and GSL Design: a dated record.

Published by CoreShift Technologies LLC. CoreShift is not affiliated with GSL Design.

Every message on this page is quoted word for word from the original message threads, which are preserved in full. The screenshots are unedited except where email addresses, the client’s details and attached images were blacked out.

Exhibit index
  1. 01Jul 7, 2026 · his question and CoreShift’s reply
  2. 02Jul 7, 2026 · “you can go fuck yourself!”
  3. 03Jul 7, 2026 · “complete piece of shit”
  4. 04Jul 7, 2026, 4:44 PM · “when I see you in person”
  5. 05Jul 14, 2026 · the FieldPins name
  6. 06Aug 7, 2026 · group thread (content warning)
  7. 07Aug 10, 2026 · about the client (content warning)
  8. 08Sep 30, 2026 · “shady ass mother fucker”
  9. 09Sep 30, 2026 · “see your ass in person”
  10. 10Sep 30, 2026, 5:16 PM · “You’re begging for it”
  11. 11Sep 30, 2026, 5:07 PM · contact-form submission

01 · Background

Why CoreShift was brought in

CoreShift originally built the infrastructure these websites run on: the server, nginx, WordPress and the hosting stack. GSL Design then deployed a theme on top of it.

The websites belong to CoreShift’s client, Dr. Baig: Baig Medical Group, RF Supplements and RFS·RX. When the client declined to let his developer dictate the direction of his own website, Greg Loring still held the WordPress administrator account. In effect, the client could not change his own website without his developer’s permission.

Requests the client had made were answered with “no, that’s impossible.” Those things are now live.

The client sought CoreShift out. CoreShift built a new server, migrated the sites onto it intact and cut DNS over. Greg Loring was still on the site’s administrator account in August, when he asked to be taken off it (exhibits 06 and 07).

02 · The work

What was there when CoreShift took over, and what was fixed

Before

  • Contact forms that saved nothing, so there was no record of a single inquiry.
  • Bots posting to checkout, running up failed orders and Authorize.Net fees.
  • A REST API publishing administrator names and login slugs.
  • Import files and WooCommerce logs containing customer order data, downloadable by anyone.
  • A 2.22 MB homepage image.
  • Mobile menu links nobody could see.
  • Store emails and the PayPal receiving address still pointing at the former vendor.
  • The store’s base location set to Arizona instead of California.

After

  • A hardened server with nightly backups.
  • A scrubbed staging copy for safe changes.
  • A full redesign of every page.
  • A store connected to a custom operations system: every form submission becomes an inquiry, and shipping labels and product edits are done from it.
Most serious finding · closed Sept 22

Import files and WooCommerce logs containing customer order data could be downloaded straight from the website by anyone who knew where to look. CoreShift found it and closed it on September 22, six days after taking the site over.

The work on rfsupplements.com, by date, since CoreShift took it over:

Server and backups

Security

Staging site

Design, all live

SEO and AI discoverability

Email and store settings

Connected to the operations system

RFS bot

What we have changed on our side

These three sites had been labelled as website builds on the CoreShift showcase. They are now labelled for what they are: Website Handover. The theme they started from was his. The server, the migration, the data, the systems behind them and every feature added since are CoreShift’s.

03 · August 7 and August 10, 2026

The slurs he sent our client

In August, Greg Loring was still on the website’s administrator account and was receiving its automatic notices. These two messages were sent while he asked to be taken off it. Both screenshots contain a racial slur or racially directed abuse and are behind a warning.

Exhibit 06Fri, Aug 7, 2026 · group thread: Greg Loring, the client, Darrin Abell

Can either of you two dip shits figure out how to take me off of the admin account so I don’t get these anymore?

Sent with a forwarded WordPress error notice. After the client replied, he wrote “Fuck off” and sent a dark-skin-tone middle-finger emoji.

Contains a racial slur and abusive language. Select to view the screenshot.

August 7, 2026. The client’s details and reply are blacked out.
Exhibit 07Mon, Aug 10, 2026 · 9:17 AM and 3:47 PM

Get your shit together and remove me from the admin.

Sent at 9:17 AM. After he had been removed, he wrote about Dr. Baig, in a thread Dr. Baig was on. The message is in the screenshot behind the warning below, and it is exactly what the warning says.

Contains a racial slur and abusive language. Select to view the screenshot.

August 10, 2026. Two attached images are blacked out.

04 · July 7 and September 30, 2026

The threats

His position

Greg Loring has since said he never threatened anyone. The messages are below, as he sent them.

Exhibit 04Tue, Jul 7, 2026 · from 4:44 PM · his thread with the client

I hope you’re this cocky when I see you in person. My guy

He had demanded payment (“Pay me what is owed to me.”). The client answered that the check had been mailed the week before. This was his reply. His next message began “Fired? Give me a break. You’re such a dumb fuck.”

Text thread between Greg Loring and the client, July 7, 2026. Greg Loring: “You are sadly mistaken if you think for one second I’ll allow you to fuck me over on this project. I’m gonna ask you nicely one more time. Pay me what is owed to me.” The client: “Your check was put in the mail last week my guy”. Greg Loring: “I hope you’re this cocky when I see you in person. My guy”. The client: “If calling somebody ‘my guy’ was cocky, that must be why you got fired”. Greg Loring: “Fired? Give me a break. You’re such a dumb fuck. You weren’t a paying customer. You were a tight ass trying to get everything for free. Keep that same energy though. I like it.”
July 7, 2026, from 4:44 PM. Messages in blue are the client’s.
Exhibit 11Wed, Sep 30, 2026 · 5:07 PM · CoreShift contact form

Yo dipshit! You need quit claiming web development on sites you didn’t do, you fucking clown.

Submitted through the contact form on coreshift.technology, signed “Greg”, with the email address greg@punchyoface.com.

Contact-form notification, 5:07 PM: “New lead — coreshift.technology. Greg. email: greg@punchyoface.com. Topic: I’m not sure yet. Name: Greg. Email: greg@punchyoface.com. Anything else: Yo dipshit! You need quit claiming web development on sites you didn’t do, you fucking clown.”
September 30, 2026, 5:07 PM, as delivered by the CoreShift contact form.
Exhibit 10Wed, Sep 30, 2026 · 5:16 PM

What the fuck are you claiming design and development you dumb fuck.

You’re begging for it

Sent beneath a screenshot of the RF Supplements footer.

Text, September 30, 2026 at 5:16 PM: a phone screenshot of the rfsupplements.com footer, followed by two messages from Greg Loring: “What the fuck are you claiming design and development you dumb fuck.” and “You’re begging for it”.
September 30, 2026, 5:16 PM.
Exhibit 09Wed, Sep 30, 2026

i can’t wait to see your ass in person

You cunt

Sent beneath screenshots of three cards from the CoreShift showcase.

Text, September 30, 2026: screenshots of CoreShift showcase cards for RFS·RX, RF Supplements and Baig Medical Group, followed by two messages from Greg Loring: “i can’t wait to see your ass in person” and “You cunt”.
September 30, 2026.

05 · July 7 and September 30, 2026

The abuse

Exhibits 01–02Tue, Jul 7, 2026 · his thread with Darrin Abell

He asked whether his access had been removed before anyone checked that he had been paid. CoreShift replied that it did not want to be in the middle of anything between him and the client, that the client owns and controls his own domain, and that the client said he had paid before any DNS change. This was his answer:

You involved yourself by doing that. I haven’t been paid. And you can go fuck yourself!

Text thread, July 7, 2026. Greg Loring: “Did you remove my access to my own project before checking to see if I was compensated for it?” Reply at 12:01 PM: “I absolutely do not want to be in the middle of anything going on between you and Adil. He has ownership/control over his domain name and dns was updated to point to a different box with the website… he did elect the fact he paid you prior to any dns changes.. as mentioned - I do not want to be in the middle of anything between you two…” Greg Loring replies: “You involved yourself by doing that. I haven’t been paid. And you can go fuck yourself!”
Exhibit 01: his question and CoreShift’s reply. Exhibit 02: his answer. July 7, 2026.
Exhibit 03Tue, Jul 7, 2026 · his thread with the client

The client wrote that a check would go in the mail when he was back in town, that this was his last and final response, and asked not to be messaged again. His reply:

Wow - you’re a complete piece of shit.

Text thread between Greg Loring and the client, July 7, 2026. The client, partly obscured: “…ll put a check in the mail when I get back in town. This is my last and final response. Again, I wish you nothing but the best but please don’t message me anymore.” Greg Loring: “Wow - you’re a complete piece of shit.”
July 7, 2026. The client’s last reply, and his answer. The same afternoon he wrote “You’re such a dumb fuck” (exhibit 04).
Exhibit 08Wed, Sep 30, 2026

His message opened with an offer:

I’m going to give you the opportunity to correct this privately before I address it publicly.

The message that followed it:

You are a shady ass mother fucker.

Text, September 30, 2026, below a highlighted excerpt of website copy. Greg Loring: “I’m going to give you the opportunity to correct this privately before I address it publicly. I have a complete Facebook post ready to go explaining exactly what has happened, including the websites you’re displaying as your company’s work that I designed and developed, as well as the Field Pins material and wording I shared with you during development that is now appearing on your website. Remove those websites from anything representing your web design or development portfolio, or clearly change the wording to accurately state what your involvement actually was, such as website maintenance or modifications. You did not design or develop those websites, and they should not be presented in a way that suggests you did. I also need the Field Pins wording that came directly from the material I shared with you changed so it is not being presented as your original work.” Then: “You are a shady ass mother fucker.”
September 30, 2026.

06 · July 14 and October 1, 2026

FieldPins

Publishing proof of completed jobs, with photos and locations, to a business’s website so that search engines can find it is an established product category. DataPins and others already sell it. Greg Loring’s name for it was FieldPins.

CoreShift built the working pipeline. By June 12, 2026 it ran end to end: job intake, automatic privacy scrubbing of every photo, written descriptions and alt text, a human approval gate so nothing publishes unreviewed, and publication to the client’s website, with ranking measured alongside it.

Exhibit 05Tue, Jul 14, 2026

It’s in your best interest to remove this immediately.

Sent with a search result showing the FieldPins name on fieldpins.m8n1ac.com. CoreShift removed the name.

Text, July 14, 2026: a screenshot of search results with a hand-drawn circle around the listing “fieldpins.m8n1ac.com — FieldPins — [TAGLINE PENDING · copy prompt]”, followed by Greg Loring’s message “It’s in your best interest to remove this immediately.”
July 14, 2026.

CoreShift’s product is JobTrace.

On October 1, CoreShift compared every line of its JobTrace copy against everything FieldPins publishes on fieldpins.io. No sentence was copied. The longest shared run was five ordinary words. A few lines did echo the FieldPins tagline in shape, and CoreShift rewrote them anyway.

07 · Where this stands

The record

Every message on this page is preserved in its original thread. Any further contact should be in writing.

Anyone who wants to see what CoreShift builds is welcome to look at the work itself.

See the CoreShift showcase →