3D video calling, or our original Matrix + WebVR demo) we always get a some grumpy feedback along the lines of “why are you wasting time doing VR when Element still doesn’t have multi-account?!” or whatever your favourite pet Matrix or Element deficiency is. > Whenever we work on metaverse or VR for Matrix (e.g. Just don't get addicted to Google-provided data :)įunnily enough, they address this question on the linked website: On this specific point, you are right, and seeing such integration would be awesome. Now, I really don't want you to get the wrong idea, I love most projects at Matrix/vector, but I can't help but feeling uncomfortable when third room is talked up, while basic chat features leave a lot to be desired. And since messaging is so reliant on networking effects, I would concentrate on being able to reach the largest possible audience. I can't really direct you to spend energy on some topics vs others, but it seems to me that there are more (potential or current) Matrix users with old hardware than VR gear. Some space-based device-specific controls would be nice to have.Ī lot of the issues can be improved by the upcoming sliding sync, and I know vector.im isn't in a brilliant financial situation. I don't wish to have the same level of intrusiveness from all chats: for some, I want to see the notifications, for others I want to hear them, etc. I only recently discovered that Android could handle conversation-level notification granularity, and don't have anything similar on my other devices. I've seen multiple serious bugs that end up clearing the local DB, triggering an initial sync that lasts for more than 10 minutes. Additionally, the UI appears to be rendered at single-digit framerates. It might be a chrome bug, I'll report this. The web app fights with the browser to draw over the URL and tab bar. my SO experiences constant glitching with Element on Chrome on Macos. It now takes seconds to sync after opening instead of multiple minutes. I thought it was just the app, but it works much better on this new phone. The phone and most apps were fine, but Element was oh so sluggish compared to the others. experience was night and day when I switched from my resource-constrained Galaxy S4 with LineageOS 18.1 to a FP4. Though very nice improvements have been made lately, I can say from what I've seen and experienced that a lot of improvements can still be made: While my comment contains some criticism, I'm really excited for this new offering.Īs much as I like the third room concept (I like it, but didn't actually try it), I am wondering how much of a distraction it is for Matrix developers?Īs a datapoint, a good chunk of my social circles use Matrix, but they seem to incessantly complain about Element. If you open the inspector on any of the examples you'll see how many tile fetches it triggers per second. So the only thing to worry about is how Google showed us couple of years ago how relentless it starts to charge for a previously free service - the Google Maps Javascript API - after it sees that enough developers got technically invested into Google Maps. The Map Tiles API documentation does not contain a "Usage and Billing" section, which seems to imply that it is free to use, bound to the above mentioned limits. Rate limit is 12,000 queries per minute for the tile renderer. This is calculated as the sum of all requests for all applications using the credentials of the same project. Maximum 250,000 renderer’s tile requests per day. Maximum 300 root tileset queries per day. Maximum 6,000 queries per day, calculated as the sum of all requests for all applications using the credentials of the same project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |