![]() ![]() * Optimized fill of feed items by moving the fill of the hidden area to the first expand of the frame. * fixed strings in IdDialog (patch from Henry) * fixed pasting of rslinks with special characters with Qt5 * Used QTextBrowser to show the channel description for unsubscribed groups to avoid the horizontal growing of the channel list. This is not so easy because the current code heavily depends on signal/slot connections. Since we reached some rather stable status, we would now like to:Īpply for debian packaging (we will need some sponsoring!)Ĭleanup deep indexing (currently using xapian) so that it can be shipped in the next stable version This release would not be here without them. Improved debug output thanks to new RsDbg(), RsError() and RsWarn() macros Ĭonsistently switched licence to AGPLv3 (GUI) LGPLv3 (libretroshare) in prevision to application for Debian packaging.Īs usual, only congratulating all the testers and pull-requests providers will not make them true justice. Some systems tend to allocate too much memory on threads and RS uses lots of them Memory usage has improved, but is still not perfect. The RTT now between two friends keeps low values RTT/bandwidth management and service priorities has been improved after lots of careful tests. #RETROSHARE OVER TOR FULL#It appears that we can afford to only send the PGP fingerprint instead of the full key, without losing any security.įull certificate (old method, a.k.a. Up to v0.6.5, Retroshare used certificates containing the SSL id, the PGP public key and naming information. #RETROSHARE OVER TOR HOW TO#Use the double image below to compare both viewsīoth 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. Two different visualization modes are possible (top right blue button, left to the search field): grid or list. As you will see, it was totally worth it.Ĭhannels benefit from a new layout that is more suitable to their usage. ![]() While we decided to stop developing new features in November 2020, it took us 4 months to fix all the bugs, mostly thanks to a really good user-feedback. In the end, lots of bugs have been introduced in the process and it took some time to reach a perfectly stable product again. token system, notifications, etc), which had us re-implement some GUI parts taking the opportunity to make them more efficient or re-designed to a better layout (e.g. This is for one simple reason: we changed lots of core features of the software (e.g. This release took even more time than the previous ones. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |