Karliss
Joined 11 years ago
Joined 11 years ago
Once you open corresponding panel in Rumble it shows you all the information you need to copy paste in single place with convenient copy to clipboard buttons.
Platforms with "builtin support" require same amount of configuration minus the server url. But since the server url is provided in the same place as stream key, copy pasting 2 instead of 1 value hardly makes a difference. It probably takes less time to copy server url than trying to find it in dropdown containing 70+ other services.
Google stadia had special builds, very well could have been DRM-free.
Other streaming services like G-force now are closer to renting a virtual machine with some automation scripts on top. Where after connecting you use a slightly modified version of steam to install games (which publishers allowed to be streamed) almost like you would install them locally. Those definitely aren't DRM-free (except a portion of indie titles which are DRM free everywhere). While G-force now tries to limit access to underlying OS, surface is too large to trust the platform with DRM free builds especially if it allows installing multiple games and steam workshop mods. It's a bit more complicated as g-force now also has "ready to play" games which provide more stadia like experience with better integration.
So overall it means 2 cases: * special builds/game specific integration scripts from streaming platform -> requires extra work and agreement between streaming platform and developer/publisher, introduces uncertainty of how streaming platform limits account sharing (compared to the DRM publisher uses) * no extra work, just single checkbox in steam developer panel -> potential conflicts with finger printing, DRM and anticheat systems
Neither of 2 are no brainer free money. Either it's extra work and bureaucracy to negotiate, prepare and configure special build. Or it's conflicting with DRM systems.
It's trivial only for smaller indie devs who are uploading DRM free builds to steam anyway.
For DRM and ban avoidance detection this means either false positives (which is bad rep) or if it's tuned to ignore those signals on specific service provider hardware makes it easier to do account sharing (and thus not buying the game).
Which leaves user space drivers embedded in the app as more or less only option. I am a bit surprised Apple allows enough low level thunderbolt access to implement this at all. On a desktop you could implement a user space driver in a shared library so that it can be used by multiple apps, but that's not really an option on iOS either.
Such approach is hardly rare. Many niche hardware products do something similar. Either implement driver/interface for generic data transfer device (like a serial port), or use the slots for vendor specific data within HID, bluetooth interfaces and implement a custom protocol on top of that. Almost any bluetooth device which requires vendor app for configuration, many smartwatches, gamer keyboards/mice which require custom app for configuring RGB lights (often HID based), even MCU programmers and other serious electronics development tools often show up as USB serial ports.
Based on that I would expect that if you advertise in small town newspaper, the job needs to be located in that small town. Want them to work in your big office next to big city, then it must be a newspaper widely distributed in that city not a small town on the opposite side of continent.
The effects in some of the demos simply kill any video encoder, only way to properly experience them is by running or emulating locally. Not that crystal sharp upscaled square pixels on modern display or poor quality CRT filters are very representative either, but it's likely better than blurry mess you get when video encoder tries to deal with high frequency details or random noise from procedural effects.
And almost any practical routing system will have a mechanism for tradeoffs of different aspects. Often there is a distance/time tradeoff which directly relates to speed on corresponding segments. But the tradeoff can also be in the form of "on average x seconds spent waiting green light in each intersection or time to stop before railroad crossing. So there is no reason for a system optimizing grade to completely ignore all other factors, it's just a question of weights and curves of each of them.
Another interesting pattern I saw while browsing around was increased level next to every fancy cast iron light fixture along a specific bridge. The bridge was made mid 20th century so I don't think they are old enough to have used thorium gas light mantles.