Reddit retroshare5/7/2023 ![]() ![]() A new cache for metadata allows a much faster loading of forums/channels/boards.Some backstage improvements are also worth mentioning: In particular its html and JS files do not need anymore to be installed on the client where the WebUI runs. The webinterface is now entirely supplied by Retroshare. Option ‘-W’ asks retroshare_service to set a new password for the webinterface. Another limitation is currently that retroshare_service does not use the automatic Tor configuration code (which depends on Qt) and setting up a headless Tor node requires some manual tweaking in order to (1) configure Tor system-wide to start a hidden service, then (2) create a Tor node with the Qt UI, choosing the manual Tor configuration option and setting the correct ports according to what was supplied to Tor. While ‘-U’ would normally be followed by the node ID you want to start, using ‘list’ instead will show up the list of available nodes and ask for the profile password before starting it. retroshare_service/src/retroshare-service -U list -W Setting up a retroshare server with retroshare_service+WebUI therefore needs to copy the full ~/.retroshare/ data directory prior to launching retroshare service: >. While retroshare_service can be used to create new nodes, the web UI doesn’t currently offer to do it. See, and add “rs_webui” in the compilation flags. It is rather cheap and can be ran on Android phones as well as screenless servers.Ĭompilation simply requires the appropriate flags: > qmake CONFIG="rs_jsonapi"Īn example of application to this interface is the new WebUI developed during Google Summer of Code 2019. The former headless retroshare server has been replaced by a new executable named retroshare-service, to which one talks using the retroshare built-in JSON API. ![]() 10 – End of retroshare-nogui (don’t panic!) Note the use of postToObject (here again!) which allows the event to be handled in the GUI thread, since rsEvent will likely call the lambda that is registered as event handler from a different thread (here, the file transfer loop). Here’s why (“ ids(, mEventHandlerId, RsEventType::FILE_TRANSFER ) It appears that we can afford to only send the PGP fingerprint instead of the full key, without losing any security. Up to v0.6.5, Retroshare used certificates containing the SSL id, the PGP public key and naming information. Both in channels or boards, the new visualization system is now based on an abstract item model (instead of manually inserted items as it was in v0.6.5) making it much faster to load and offering a lot more possibilities for how to display the information. ![]()
0 Comments
Leave a Reply. |