This will include features like groups joinable by link, group admins, lower latency, and more.Improving general group features and performance by adding support for tox “DHT group chats” or “new group chats” in toxcore.Making groups more usable with little things like an option to disable join/leave notifications.Possibly improved to fill in history gaps from trusted friends.Initially messages sent while you’re offline won’t be added to history. Expand our automated testing to make regressions rarer and development more efficient. Make the file transfer tab more useful by having the files link back to the part of chat where they were received for context. Add pending offline file transfers that behave like messages which can be queued to be sent once connected with a friend.Add file transfer auto-resume, to continue the transfer after it’s interrupted.Fix lots of the weird behaviour and crashes with the chat log and history search.Changes will be targeted at benefiting all users, and nothing is changing in terms of copyright or licensing. The objective is to improve qTox and tox in general. Think of this as a year-long “summer of code”, if you’re familiar with that program. Additionally, they funded the part-time creation of toxfs, and a few months of sphaerophoria’s part-time work on qTox. If you would like to do videocalls (I tested only desktop sharing), uTox 0.16.0 and newer will crash at any OS.Thanks to a generous qTox user stepping forward with funding, I’ve been able to quit my software engineering day job and commit to one year of working on qTox full time. Also note that openal doesn't currently support sndio input, so you won't be able to talk in audio calls (but you'll hear everyone because openal supports sndio output, that's weird). I hope I've helped, but still I prefer toxic and toxcore which openbsd-wip provides, it's sad that they won't get in OpenBSD ports. In src/main.c instead of "#if !defined(_OBJC_) || defined(_NetBSD_) || defined(_FreeBSD_)" write "#if !defined(_OBJC_) || defined(_OpenBSD_)" If you would like to run a stable uTox, compile uTox 0.11.1: UTox 0.15.0 and newer has experimental support for OpenBSD.Īlso to compile uTox 0.16.0 and newer, you have to install uTox's version of toxcore Īlso if a gtk filepicker doesn't work (versions older than 0.16.0), in src/xlib/gtk.c change #define LIBGTK_FILENAME "libgtk-3.so.blablabla" to #define LIBGTK_FILENAME "libgtk-3.so" may be a good site for searching for existing applications already ported to OpenBSD. If you decide not to pursue this task, you might be better served by exploring what applications already have been officially ported to OpenBSD. You might see this as a personal challenge to learning new skills. To successfully port an application to OpenBSD requires substantial knowledge, patience, & tenacity. In other threads, I see where you have stated that you do not have development experience. While I understand their statements about "increased security", I would think that an XMPP application running over IPSec links would be as secure, if not more so. It may be as complicated as months of work.įrom what I can see, Tox is a peer-to-peer messaging system - a slight variation of more familiar XMPP applications such as net/prosody (which is an interpreted Python application.). This might be as simple as an evening's work. If you want to run Tox on OpenBSD, you will need to figure out whether the source can simply be compiled through the tools provided, or whether you will have to modify the source code before compiling something which is recognizable by OpenBSD. The application I find on GitHub is C++ code which is a compiled language. In general, interpreted applications run slower than compiled applications because of the runtime overhead of real-time translation of source code. Every time the application is executed, the interpreter will translate the source into binary instructions which are immediately executed. Interpreted applications are executed directly as the application by an interpreter.The resulting binary image created by the compiler is executed directly by users as the application itself. A developer will translate source code into binary instructions through a compiler. Compiled applications consist of one or more source files which are translated into binary instructions understood by the operating system (boot-up code) & processor.In looking at the GitHub repository, it appears that this application is a C++ application primarily using Qt5 as the GUI interface.Īpplications fall into two categories - either they are compiled or interpreted. Would it work by running the Source Code?
0 Comments
Leave a Reply. |