1. mobesi

The first attempt at writing a web application proxy that is supposed to be used in a team.

(I'm first going to write down some thoughts here, until I'm in a state were I'm confident what I can write a lot of code).

1. mobesi
1.1. Collaboration
1.2. Scenarios
1.2.1. all people in the same network (local)
1.2.2. all people in the same network (VPN)
1.2.3. all people in the same network (Internet)
1.3. Timeline

1.1. Collaboration

When currently looking into a page, all inforamtion is stored locally on your machine. While most tools have embraced collaboration, information isn't shared. Now one could simply install some proxy on a vm somewhere and tell everyone to proxy their traffic through there, this isn't really practical.

In the end, what I imagine would be a proxy that allows you to view the results locally (requests send and so), but for all people of the team. You should still be able to use it in "singleplayer" mode, but should also be able to function as a "shared host" that syncronizes the state of the application with other people.

1.2. Scenarios

There are three scenarios (that I've thought of as of now):

1.2.1. all people in the same network (local)

The simplest one: we're all in the same network and we all want to work with each other. Open some port in your firewall allowing your instance to communicate with another one.

1.2.2. all people in the same network (VPN)

Almost as simple (depending on how the VPN is setup).

1.2.3. all people in the same network (Internet)

Also fairly simple, although they're probably going to be problems due to NAT or so (let's go public v6 only?).

1.3. Timeline

2022-01-29: start of writing this down




        

emile - 1731525159.714905s - generated using vokobe "0.1.3"