Dr. Quinten Stokkink

Results 216 comments of Dr. Quinten Stokkink

@cranphin you could try to force kill the GUI process and leave the core running (I don't know if this actually works).

@cranphin the following *should* also work, based on: https://github.com/Tribler/tribler/blob/d5be6bab8ee456cde1c9bb3ab6056c5a1c3f7a92/run_tribler.py#L60-L63 Execute the following when launching Tribler: ```batch SETLOCAL SET CORE_PROCESS=1 SET CORE_BASE_PATH=%cd% SET CORE_API_PORT=8085 tribler.exe ``` *Disclaimer*: you may have to...

You could consider bundling your tests in a [`unittest.TestCase`](https://docs.python.org/3/library/unittest.html#unittest.TestCase) to avoid writing your own `test_` name matching. The `unittest` module has all sorts of functions available to automatically load or...

I think the road map should be: 1. Refactor existing code to use `Peer.send` (and internally update the endpoint accordingly). 2. Create a new version of `Community` logic, that allows...

After first attempt today, priority is as follows: - [ ] Don't use the IPv4 address in the DHT community.

Once we have this abstraction layer, it would probably make sense to use [Scapy](https://pypi.org/project/scapy/). [It supports many of the interfaces we would like to use](https://github.com/secdev/scapy/tree/master/scapy/layers), for example: - IPv6 -...

I have changed my mind. After failing to implement this (starting over 3 times) and talking with @egbertbouman a litle while ago, I believe I have a more natural fit...

Here is the class diagram (using `n` instead of `*`) of the current state of affairs and the newly proposed design (see [my previous post](https://github.com/Tribler/py-ipv8/issues/615#issuecomment-667653713)). ### Current ![olddesign](https://user-images.githubusercontent.com/3630389/89167415-b144ef00-d57b-11ea-8504-3f5b26b34f48.png) ### Proposed...

With #830, the first (easy) step is complete: we can now send and receive IPv6 interface packets. Remaining: - Refactor the `Peer.address` so a `Peer` can have one address per...

I believe we can maintain full backwards compatibilty by making sure all introduction requests and responses using IPv4 still use the old messages. For all other interfaces we will define...