disgusting terrsts of foreign gypsies foreign terrorst grp/cult

 yep never been a makefile nor cmake expert ever in all the time i coded c or cpp :D

nice that the compilation does not have alot makefile but rather visual studio conversion method (for webrtc cpp library) 

for unreal side also compilation does not have makefile/cmake.  (or the least windows compilation side does not have such compilation mechanism) 

hmm for presence layer would use some mechanism alike some webrtc nodejs library. 

hmm i decided to also add other servers integration for since gamers to create matchs with selecting their friends on game servers with connecting oauth authentication so that they could create matches with their friends there. 

but maybe this should be a second feature.  yep not to develop now. 

yep. 

i mean for gamers to run a discord server and their app to be able to authenticate to so that they can create presence in presence layer of nodejs server with oauth info from discord. and friends info from discord.  (ephemerally) to setup battles with their discord teams. 

hmm but i decided to postpone this feature.  or not implement at all. 

yep.

first lets develop a basic presence layer with nodejs webrtc tech so that they receive temporarily each running desktop app generates a presence uuid and battle creation capacity from webrtc signalling layer info being ephemerally present there to people to create /join battles. 

somewhat steam also i think follows this approach. maybe not exactly. but i think steam also has this webrtc aloke layer to fix this null online system's NAT issue.

aha but checking here, maybe adding such feature to use discord features  from nodejs side per user session there seems not hard to implement. 

Using discord oauth2. A simple guide and an example nodeJS app | by Anton Orlov | Medium

hmm lets implement. seems easy to implemtn on nodejs side. 

hmm but i would need to check js knowledge. had not coded js for a very long time. 

 

hmm so this webrtc based null system project has two components mainly:

one is client side plugin development (cpp)

one is this presence layer with nodejs (webrtc signalling layer)

so it wont be hard to extend the nodejs layer with this connection to platforms. maybe discord/and social media platforms etc. to be able to receive friends knowledge at nodejs based session  layer to ephemerally retrieve users friends data, to publish battle info to friends. so that they could create e.g. ephemeral battle1 context which they can publish info to and then people can search and enter to battle. 

e.g. 

hmm but this i think could be later added features. 

lets first implement the basic feature of nodejs which provides a presentation layer where users can share battles and people can join battles.   

hmm wondering if apache db big data technologies is required on the server side

i think in this basical initial version, its not required.

e.g. users session in nodejs can publish the battle in the server  and such server could hos t an interim inmemory db  and then people in such server search battles from same server. yep. db is costly. i think this hmm basic architecture would work for initial this presence layer nodejs server. 

I mean geographically distributed  nodes and they have inmemory db and basic nodejs server logics and provide peerjs similiar presence layer but some also null plugin battle concept. 

there would be no relay servers initially for webrtc. (to reduce server costs) 

but the nodejs server side would be coded very good architecturally so that in future it could fastlybe added modules/features. 

hmm client null plugin side architecture already has that framworks.  but to server side e.g. it should be easy to change in memory db with an apache db in future or so. or else to add oauth modules integrations to presence and battle frameworks there in nodejs to be coded.

hmm so i would need to study js again since this requires some programming paradigms to do these. 

hmm possibly i wont use functional paradigm.  but standard usual object oriented paradigm. to an extendable session/presentation framework with nodejs. which does not provide by itself any authentication but later in future can oauth2 wise get connected to other platforms. just a basic session/battle setup layer and webrtc discovery protocol/share/ consensus layer.