Remote development between civy PCs to save on HW/SW costs

I'm orienting myself on the game/OS-modding world, and have a few questions: Do you think the following proposition could work? >modders/sw devs need access to specific software and/or hardware to test their mods and sw for a broad userbase >this is expensive, UNLESS >they remote into other people's stuff (legally) and dev/test on other people's stuff >this could be rewarded with a "thank you" note in the mod/sw credits This is pretty risky by itself, although I imagine some would tolerate the risk, it can be mitigated to some extent: >VM with SSH >VM only has SSH tunnel into it, no Internet access >pass hw through to VM, OR >install Steam, put in Offline Mode/prepare other software >give coder access to one-time or single-purpose SSH credentials into VM What do you think? I'm thinking this could open up a lot more modding and coding to people with scarce resources, AND let (semi-)tech illiterate or rich but time-poor people have fun contributing to projects in their own way. One reason for this is that if you want to make mods that work with Steam games, you normally would have to own them on Steam while it may be much more practical to mod the CD or GOG or other fixed-version you have. (Steam games do not let you have access to old versions this is horrible for "deep"/low-level mods.) It could also be a lot of fun for low-level coders that otherwise would have no way to run their weird assembly codes etc. on real hardware. >USER CHANGED THE OP PICTURE OR WAS SOMETHING ELSE THE ISSUE

>>32385 >mechanical pencils are good because they last forever >proceeds to buy a ton of mechanical pencils anyways >they are all cheap soykaf Reddit everyone.

This CIA / NSA shil* is not giving up, you've gotta give him that... No, I don't think many Lainchan users are interested in using somebody else's proprietary devices and in doing so losing a portion of their freedoms.

>>32419 >lacks reading comprehension >replies with soykafpost without even acknowledging actual thread >>32385 Regardless of if devs would find it useful, I doubt anybody with the wanted hardware would actually go through the trouble of setting it up. Tech-ignorant enough would find it too difficult. Tech-savvy enough would be too wary to let strangers onto their machine+network only to gain fuarrrk all. >no way to run their weird assembly codes etc. on real hardware If you have a way to access the remote PC you already have real hardware. Used old computers are inexpensive, you don't need anything fancy for learning programming and messing with ASM. Somebody tech interested enough for that wouldn't be stuck with just a phone.

>>32421 Your previous thread was borderline spam and your OP pic is literally a Reddit screen cap. Consider yourself lucky to get a pity reply.

>>32419 >>32420 >>32422 :^D >>32421 I'm evaluating if it'd be worthwhile to make a tech-illiterate-proof toolkit for this. The point isn't "access to any hardware", it's access to "real systems you don't (want to have to) own". I don't want to fill my house with 5 models of Mac computers, 3 Windows boxes or laptops, 200 Android phones, 3 BSD and 5 Linux boxes, 2K embedded plaforms and 100K pieces of proprietary software. I see two main topologies being useful: >star, devteam to user testers, with a TeamViewer-like application to make setup easy >pre-configured or ad-hoc mesh (kinda like Git), for dev teams that distrubute testing/dev hardware and software (e.g. only one dev owns a Mac but a few test on it, or one modder owns the GOG version of a game and another the Steam version) to get optimal testing coverage without having to make a centralized build/remote dev system As for applications/incentive structures: >mod development and other cross-platform dev; specifically to increase testing coverage >embedded and retrocomputing (e.g. coding clubs; so that each member could have like 1-5 devices and yet fiddle around with 10-50 devices) to save on space and initial hw investment, or to share access to obscure hardware