gmnprada / wanbioner Goto Github PK

Build A Development Enviroment to connect into PI Account

https://www.arin.net/reference/research/statistics/address_filters/

We re here to develop some new protocol so see the best practice memo above.

ISSUES

PITM should use loop back only for the recursive stamp of network links to internal so the address 127.0.0.1 is reserved if it's detect from same host machine.

PITM should only assign public gateway that directly accessible on the global ip address to the net by confirming through api call and os interface the ip match before added into the collective networks stamps.

Private and Public separation should be clear to prevent leakage and misuse of the network not according to its goals.

Alot of goes into waste,

The project should go renamed into

Wanbioner

Need to secure fqdn first but I just did not want spend another time waste discuss it here

Web Socket

• web socket its designed for a short timeout so it not the best way to use at interval that so fast under 30ms

Tcp

• we didn't not know yet if we should do PITM opcode in this protocol, as it's has much overhead than udp, probably will disable Nagle algorithm like many fast game transfer packet do. Also tcp maintain two way connection syn and ack. Piwan opcode more like a warship in the ocean which we didn't know which ships is nearby without mapping it with some tools like tracert or measure rtt and ttl.

The best current available protocol is udp if it's on public space, for its round robin algorithm contests in later plan of the milestone. The fastest one who deliver the packet to peers is the one recorded on ledger of auditor.

Many web based environment and browser did not support udp protocol yet there is some implementation on quic protocol the latest I know the info about.

Till that is determined by developer and engineer this issues will keep be open.

If we re running in not a browser environment we should prioritize to use udp as the first class protocol available in public gateway.

And prioritize any available data link, or basicly we call a wire on local machine and private internal networks if it's running the PITM and piwan code also.

as a need on security and vulnerability assesment on securing the networks should we allow each machine run a protocol differ from wanbioner port?

as example a legit node should only open this port if we make its strictly exclusive , need to be differentiate strictly exclusive as more secure than a machine running and serving other protocol.

agreeing on same port also make the protocol easily identified by some networks tools as wanbioner will not verify its a legit node if its run on custom port its a must on auditor process on not behind nat networks.

-ssh (optional)
-http
-https
-36123 (WBTM)
-36980 (Wanbiorner-udp/Wanbioner-tcp)

for development environment purpose

• 36981 (wanbioner-udp/wanbioner-tcp)
• 8080 (http web development)
• 8443 (https based web development)

thats what i design as maintainer and owner of this project ,

see docs/logo/wanbioner-social.jpg , its need to be changed like 4 sentences maximal on project description at brainstorm address. make sure the information is same across platform on brainstrom apps , and on website

The definition and abbreviation is already written on /docs in latest update .

make sure to separate it according to /docs/readme.md to be implemented on specific programming language

Im on my birthday so taking day off and open this repository
whoever you are joining piwan team on brainstrom app see what i capable do alone in 2 months ,

Business Team need to think how to create the presentation video

the video of mid submission of how its about

https://www.youtube.com/watch?v=VcpLBHSWEgM

the final presentation ? too early to say its final as i dont satisfied with the result yet
sincere GMNP

Code Of Conduct

is needed to keep things organized in this digital workplace . there is no IT Technical Debts under the hoods we make it very open for everyone to contribute for changes in the future of Wanbioner development.

Guidelines On Submitting Issues use the Label to tags what category the issues about.

use [ ] for name spacing or scoping which division, unit , or person must in charge to resolve the issues in the title if you know it ahead of times. for easily forward and cc and disposition message through email or other available transport , forwarding to the right person via email or instant messenger such as Telegram, WhatsApp, WeChat , Kakao, Line, Discord Etc. don't submit and issues outside of working hours, person in team who mark the phone with do not distrupt also will not forwarded an email or message to keep enjoying their holiday if they did not want to work on the project. for convenience solving a burnout problem.

example making issues

[Designer, Security, Developer] Need to Rework The Logo and Display it on Website
 
label it as it should on the issues what it about , and enhancement , feature request , change of substantial core functionality on system design , or business models and dependency problem.

as we work to make everything organize till then this issues will keep open and put into the docs of source code main repository. github is not the only git platform in the world so make everything clear ahead of times more good than doit later.