According to that I'm not covered because I tried to print more than that percentage of the book to PDF (and was presented with the kind of unusable garbage output shown in my post).
Thanks a lot for the feedback, and sorry about the issues. Would you please report them on the Jami bug trackers per https://docs.jami.net/user/bug-report-guide.html if not already? This would help the team keep track, look further into them, and hopefully fix them.
This isn’t really a helpful response. It’s the project owner’s responsibility to maintain the project, not their users.
While it’s certainly nice if the user does this and removes burden from you, it’s a better practice (and engenders more good will from your users) to just ingest this into the bug tracker on the user’s behalf (and dedupe as needed / do a search and give them the link to existing bugs if it describes their issue).
Yes, the creators should be testing their app. But making bug reports is also a fundamental useful thing. Should I not report bugs in mac os or chrome or python3 because the project owner should have figured it out? No.
He's saying, and I agree, that a casual first time user making a low friction complaint somewhere like here should simply be digested immediately by a team member and ammended onto a perviously created bug in their system. Or a new bug should be created by a team member.
I do this at my job all the time because our Jira setup is fucking balls and I have all kinds of greesemonkey to make it usable and quick for me. Any casual user is going to bounce the fuck off our jira setup. Secondly I know if there is already a bug in our system covering this issue or not, less time for my team to do de-duping etc.
Yup. About the only two complaints that might reasonably warrant asking the user to create a ticket themselves is the NAT one and the CPU spike doing nothing. For both of those though, rather than having the user create a bug report just to go back and forth over it asynchronously over months until the end user gets discouraged and drops it, a better situation works be diagnostic tools that could monitor and collect data that the devs could then analyze, ideally baked into the code where you just click a button to submit feedback and your code can code to open a bug report or just ingest metrics or something.
Thanks for trying/using Jami! And sorry to hear about the previous issues. If you do encounter them again, please do file a bug report so the team could investigate and hopefully fix them:
If you register a username for your Jami account, your JamiID will be that username, otherwise it will just be the account's infohash (public key fingerprint). A Jami username is a mapping between a unique human-friendly name and an account infohash.
> Is this JamiID that I created forever mine?
With the default Jami name server, https://ns.jami.net, username registrations are permanent, and cannot be changed or deleted. Also, if you delete or lose your account without having backed it up earlier, you will lose that username and it cannot be recovered. This is one of the reasons why it's really important to back up your account.
> If my friends create their JamiID, will the search just list them?
Yes, you can search others by their JamiID, whether it's their username or the longer account infohash.
> Do I need to import any JamiID's? How does discovery work for these JamiID's?
You would search for their JamiID and add them as contacts, similarly to how you would with other messaging applications. When you search a username, Jami will query the name server to get the account infohash and send a contact request. For example, with the default name server, to look up 'bandali' Jami would make a request to https://ns.jami.net/name/bandali to get the associated account infohash.
You can read more about this on the Jami user FAQ and the 'name server protocol' section of the developer manual:
Jami has "Swarm" conversations, which are git-backed behind the scenes, and can be synchronized across multiple devices and/or participants seamlessly. Actually, thanks to the way Jami uses git, a subset of participants in a group conversation could enter a local network and continue chatting amongst themselves, and once they connect with the rest of the participants again their histories will automatically be synchronized and merged.
To add a new device, from account settings select 'Link another device'. This will create an encrypted archive of your account details and temporarily (for 10 minutes) put it on the OpenDHT network, and give you a PIN which you would use on your new device to have Jami retrieve and import your account. You could also do this manually and without going through OpenDHT, by having Jami create a local backup of your account on your current device, and then transfer the backup archive onto your new device yourself, and import it into Jami. After adding the new device, your Swarm conversations and their histories will begin synchronizing shortly.
This. Jami is truly distributed, and there's no need to set up and manage any server(s) in the sense that one would do for Jitsi, Matrix, BigBlueButton, etc.
Also, thanks to Jami's distributed nature, it can also function in local networks without internet connectivity:
Yes, Jami calls are p2p whenever possible, and TURN is used when not (e.g. due to overly restrictive firewalls).
Yes, Jami supports conferencing. One can add additional participants to a 1-on-1 call on the fly, effectively making it a conference. Alternatively, one can enable rendezvous mode from account settings, in which case incoming calls to that account will be added to a conference (similar to a Jisti room).
Amazing. Are there any optimizations for video conferencing in case one participant doesn't have upload bandwidth to stream his video to 10 different IP addresses at once?
I was fidgeting with the tought of something like a overlay multicast network on top of unicast IP, since RFC 1770 was deprecated/never implemented.
Right. In Jami by default only the host of a conference/rendezvous-point will stream to/from all peers and mix their streams, and other peers normally only stream to/from the conference host. Also Jami can automatically adjust the call's bitrate on the fly depending on the link quality:
The moderator and local mute/unmute are separate. If you mute yourself locally, no one else can unmute you. Similarly, if a moderator mutes you, you locally unmuting yourself wouldn't override that either.
Yes, I'm an associate member [0] of the Free Software Foundation (FSF) [1], which besides supporting the GNU project in various ways, runs many Free Software-related campaigns [2] and supports a variety of other Free Software projects.
> You must not have viewed or printed, in total, more than five percent (5%) of the e-book.
-- from <https://global.oup.com/academic/help/ebooks/?cc=ca&lang=en&#...>
According to that I'm not covered because I tried to print more than that percentage of the book to PDF (and was presented with the kind of unusable garbage output shown in my post).