can you tell it's been too long since mii day? it's about time i get up to some stupid (respectful) shit in vr again. i yearn for a new bit to commit to
replacement fan delayed ðŸ˜
my chipset shall burn a day or two longer.
to make the syncing look more real-time when someone finishes submitting a new ornament they also send a network event to others in their instance to force reload the tree now so it shows up ASAP instead of having to wait for the next minute refresh.
I got a PS2 not long ago! If it suits your fancy, I recommend getting a HDD bracket and setting up PSBBN. It's like getting a glimpse into an alternate history straight from the Y2K depths.
...of that ornament. there is one more trick to it: when the user places their ornament they're asked to enter a confirmation code. i present this like a captcha but what the user is actually doing is entering the position of where they placed their ornament on the tree (thinking of the tree as...
...requests we can mitigate this at the cost of time
idea: make a vr jazz bar and act myself as an NPC bartender in it, the kind that leans in a cool fashion against the bartop while polishing a glass and offering sage advice.
then when i see a public i sneak in, lock into character, and replace the npc and see how long it takes for people to notice
...a cylinder, we encode the position as a matter of degrees and radius, then bitpack that into another integer). we send these two URLs back-to-back and correlate them to log one new ornament with look, message, and position in the database.
i hope that's a cohesive explanation. if you have any questions or intend to implement a similar system let me know and i'd be happy to help. right now the biggest limiting factor is we can only encode 18 bits max of info in one request, which limits precision, but by correlating multiple...
...holding a big array of all possible URLs so whatever integer for the ornament we need can be conveniently grabbed by index. by asking the user to modify the URL they can append their message to the end and then the act of "loading" that URL gives the server end info about the look and message...
