Making no comment here about how Scorbit is designed, but I will say that Serverless is not a buzzword (any more than any tech name is a buzzword). Whether you approve of the name or not, it's an official name for a type of cloud compute where the developer need not worry about any details regarding how the code is executed. Sure, there is obviously a collection of servers that run the code, but the developer never sees it.

With a serverless design, a developer says "execute this code" with these inputs when a condition occurs. The provider of the serverless platform (like Google or Amazon) deal with the farm of servers to run it, whatever operating system is being used, ensuring everything is networked together, and ensuring the runtime library(s) to execute the code are up-to-date (NodeJS, Python, Etc.)

So it is Serverless from the developers perspective. Generally speaking the developer is billed not by now many servers/VM are instantiated (and their memory and hard drive characteristics plus number of vCPUS), but rather how many times the code is executed and how long the execution takes.

Is Scorbit working today?

I finally got some time to try the new hog / auto claim mode. However, the app (iOS) just hangs on the “Loading Session…” screen after scanning the QR code.

Tried force quitting it as well as deleting and installing again, but no difference.

Update 1: Now it’s just showing a spinning star-like thing and not showing anything where it previously said loading session.

Update 2: seems to work if I don’t use the QR. Selecting pin from list worked and auto claim even worked after that.

iOS Build 1.3.2 (1057)
iPhone 13 Pro Max

Yes it is.
I don’t know if it was a temp problem.
I’ll try again tonight hopefully.

Well, I cannot explain it --- but all is working well today. Figured it was your backend when the QR didn't work but the iPhone App "click on the game" did. But who knows.

Auto claim is a awesome feature.

Just some unorganized thoughts on this whole situation

1. I didn't hear exactly what was said on the Godfather live stream
2. IMHO portions of Scorbits "announcement" bordered on unprofessional
3. Scorbit+JPP (the combo) was terribly unrelaiable for a year+ after JJP released the functionality, at least for me
4. With the recent JJP betas and, especially, the hog mode from Scorbit, it was very nice -- so it's rather unfortunate it goes away shortly after working well
5. (removed)
6. It was stated in the Scorbit "announcement" that there has never been any contractural agreement between JJP and Scorbit. This is exactly the type of thing that occurs when companies work together yet decide to hold off any formal Master Service Agreements, etc. Either party can walk away and the other shouldn't be upset.
7. I am interested in any legal exposure JJP might have given people purchased these games advertised with this feature. Would need to read the fine print somewhere.
8. For me, the best parts of JJP+Scorbit integration were just 2 things: automatic name/initials for high scores and, to a much lesser extent, achievements.
9. One other thing, partners like Scorbit have unique insight into the internals of a company like JJP. The info they inherently glean, such as number of machines sold, how often they are played, general locations, etc. is valuable. JJP might have decided to keep they don't want 3rd party knowing this, as part of their decision to move away. Of course, NDAs and requirements around keeping this information proprietary would have been addressed in a MSA, if one had been performed.

EDIT NOTE:
I've removed item 5. I wrote it after having found GNR wouldn't connect to Scorbit on the night all this information came to light. This made me believe that Scorbit had disabled JJP games. Turns out the inability to connect was a temporary fluke and JJP GNR can still connect to Scorbit, at least for the time being. The original text is below, for reference.

5. Let's be clear here, at least from what I can tell, Scorbit decided to cut off JJP yesterday. I personally feel Scorbit could have handled this much better (not saying JJP couldn't have either). It was an opportunity for Scorbit to own the message, make it clear that the functionality stopped when the customer installed a newer JJP release. Focus the feature removal on JJP. Instead, the message is Scorbit has turned off the functionality yesterday.

I turned on GNR last night after all this discussion and it didn't connect to Scorbit.
I just turned it on now, and it did connect. Not sure why, glad it did connect. Was it briefly disabled or was it a fluke?

I've edited this post because the info above changed what I thought had occured. I thought Scorbit was already disabled for JJP.

What is the timeline for JJP games no longer being able to connect to Scorbit?

Thanks.
I was incorrect on my #5 point. Or at least it was based on a data point that was inconsistent. I'll edit that post to acknowledge this.