I hereby claim:
- I am blueben on github.
- I am blueben (https://keybase.io/blueben) on keybase.
- I have a public key ASCYDYKwZoWIKDG-qzGebKIaucXh0zTHnDVNeaZzHMDd_Qo
To claim this, I am signing this object:
Hi! I don't work for VRC, I'm just a player. But I do want to address some of the issues relating to the elimination of VRChat client mods brought up in the VRChat feedback system. This is a direct response to this post: https://feedback.vrchat.com/open-beta/p/eac-in-a-social-vr-game-creates-more-problems-than-it-solves | |
Firstly, I think it's important that people know that you (knah) maintain a large repository of VRC mods. I don't think anyone would consider them malicious, but it is important for folks to be aware of your bias in this matter. Anti-cheat will make a lot of the work you've done obsolete and that has to be a hard pill to swallow. | |
================================ | |
* Most games that use EAC (or other anti-cheats) still have cheaters. For VRChat, this means that malicious mods will still exist and be used to annoy people in publics. | |
================================ | |
This is technically correct. It is also irrelevant. Of course there will always be cheaters. The goal isn't to make cheating imposs |
# table: svs_events | |
event_id: uniq | |
event_name: "name" | |
event_start: UTC datetime | |
event_end: UTC datetime | |
# table: event_teams | |
team_id: uniq |
Unity | |
Blender | |
Materialize | |
Meshroom | |
Instant Meshes | |
FBX2glTF | |
Substance Painter | |
Meshlab |
So my template tools for world building in Unity are now: | |
# Free | |
WorldCreatorAssistant: https://github.com/Varneon/WorldCreatorAssistant | |
VRWorldToolkit: https://github.com/oneVR/VRWorldToolkit | |
UdonSharp: https://github.com/vrchat-community/UdonSharp | |
UdonToolkit | |
CyanEmu | |
PostProcessing | |
ProGrids |
I hereby claim:
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
A | |
Application: also stack | |
A collection of services which provides a unified set of functions to an end user, possibly in the form of an API or a User Interface. | |
Availability: | |
A measure of the uptime percentage which includes downtime for any reason, including faults and planned maintenance. | |
Availability Zone: also AZ | |
A collection of network resources, hosts and the services they provide which share no infrastructure with other availability zones. The purpose of an AZ is to be a fundamental unit upon which resilient services can be built. A failure in and of one Availability Zone should never impact another Availability Zone. Should probably be called a Failure Zone given that it attempts to encapsulate failure inside of it. |
This is a lot so I’ve starred the biggest impact stuff. Ultimately, the elevator pitch is that DevOps is really “From Business to Development to Operations”. Eliminate as much friction possible so that The Business can go from ‘Having an idea’ to ‘developing the idea’ to ‘deploying the idea so we can measure the results’ smoothly and quickly. The end outcome is shorter, faster deployment cycles, the ability to try more ideas more quickly, better feedback, and agility when responding to market pressures. | |
# DevOps Resources # | |
The origins and principles of DevOps | |
http://itrevolution.com/the-history-of-devops/ | |
http://itrevolution.com/devops-culture-part-1/ | |
http://itrevolution.com/devops-culture-part-2/ | |
http://itrevolution.com/the-convergence-of-devops/ | |
http://rewrite.ca.com/us/articles/devops/a-short-history-of-devops.html |
Videos showing motorcycle rear-end collisions that might have been avoided by sharing