I used to work on the Opera browser. I quit when it got sold to China. Also wanted to do that, since most people as well as main Oslo HQ was fired from Poland a year earlier.
Opera was very much a not-dubious company. But that is what it has turned in to.
--
I use Firefox as my main work-browser, and have for a long time, and the last few years I've used Vivaldi as my main personal browser.
I find it easier to just have separate browsers rather than do anything more advanced for context. :)
What Ansible resources do you use for Nomad, Consul and Vault though? I've found a few but they all seem to lag behind release. Noone is up to date at Nomad 1.0.3. Would be nice with some half-way standard way of setting it up, like k8s has quite a few projects that do.
Why? That is the thing that excites me the most. Though it isn't thightly locked with the whole STX-side of things which isn't as interesting to me.
Only needing some "dumb" storage media to store your application data and "cloud" files unlocks suddenly a user-centric way for everyone to store data. It also unlocks real competition on the infrastructure layer.
You don't make your own generator and make your own power, -- you don't buy power from say Dell because it needs "Dell electricity". Data should be like this too, ability to be owned and controlled purely by the user (as in you have solar panels + battery) or what most people would do: delegate the work to a power provider.
Ofc not real competition in the "power provider" case since there's physical stuff happening, but for data storage (and batch/"offline" computation and event/webhook handling) a user will be able to set up their own raspberry pi or just use say Amazon to store the encrypted data. :)
I find it fits 100% in to the world I'd want to live in. ^_^
We have used a lot of time making it work on Safari. And we continue to use quite substantial resources on it. Their webrtc implementation is quite new, and not as stable as Chrome and Firefox. And with new code comes new bugs.
There is currently a bug with audio, where it'll crash in Safari, -- and we have had some issues reconnects that was more our fault (though Firefox and Chrome is much more forgiving). We have a workaround for the first, and will be doing a fix for the second once we're reasonably sure it won't regress other browsers.
Is it any of those issues you talk about? Or is it something else? (I'm not personally familiar with the Safari issues, btw, since I'm a Linux user, but I keep an eye on Firefox and Chromium-based browsers)
A Whereby-developer here. It's awesome you recommend us. <3 But we'll also kill your CPU ^_^
You can turn on "mobile mode" in advanced device settings, and it should be a bit better. But we're a bit limited in how CPU-friendly we really can be, living in the browser. Not that we can't improve, there's certainly extra tricks we could try - but not easily without also lowering fps and resolution.
I don't think "low resource use" is a big selling-argument for our product. Video can be quite heavy.
Actually, if you are using 4+ rooms, we will in many cases be better than some other webrtc services because we for these bigger rooms use a server in the middle to distribute all the streams. That will result in lower resource use. You only encode and send once, and it is distributed by the server. But if other webrtc kills CPU on 4 or less, we probably won't be much better.
This "more than 4 room" is not p2p and end-to-end encrypted, since the server (SFU) needs to read and change some headers. So it is a tradeoff. There's now "insertable streams" which allow you to do encryption on the media client side, but it's a test for now: https://webrtchacks.com/true-end-to-end-encryption-with-webr...
Hey! I've been using Whereby at work for a while and it's great.
However, I should mention that it's not possible to join calls through the mobile app (as far as I can tell), and the web app on mobile wouldn't capture my Bluetooth headset's audio properly somehow.
Again, thanks for the great work. Just thought I'd let you know :)
Thanks! It is very valuable with feedback like this, even if in this case we're painfully aware of it. :)
I was working on fixing up that when COVID-19 hit. Now we're trying to stamp out more obscure audio+video bugs (like bluetooth, which can be unreliable). We're in process of hiring a few more people so we can hopefully put someone on caring more for the non-logged in mobile app experience.
You do get a join button once you've logged in. But I must confess it is not a good experience by default. It used to be on the top of the priority list, but then scaling and any video/audio issues jumped to the top.
Hi, one Whereby-developer here. I use Vivaldi and Firefox on Linux mostly. So you could rather say we over-test Chromium-based browsers on Linux. Also test in "real" Chrome and open up Opera now and then, and Brave quite infrequently.
But the API we get from the browser is basically just `navigator.mediaDevices.getDisplayMedia()`, so what we do to screenshare is actually not much code at all. If we do something bad for Vivaldi/Brave though, we'll be quick to fix it, but this is likely their bugs, not ours :) Vivaldi screensharing on Linux broke half a year or so ago, but we're in the same town and know them, so they quickly fixed whatever bug it must have been after we pinged them.
But the most likely thing here is just that they might not have updated to newest Chromium with all these fixes. Or maybe not done the necessary platform-integrations or UI for it. Having worked on Opera previously I know anything involving chrome (UI) will often take a lot longer to do because you actually have to write a lot of custom code for it (in contrast to pure web-platform features and improvements, which basically will be free).
Blockstack 'Gaia' is a bit like that. But more focused on the actual storage services like Google Drive / S3 / Dropbox. Mentioned in the whitepaper: https://blockstack.org/papers
Blockstack can use IPFS for storage. If you create "mycoolapp.app" (or "myname.id" to use a namespace that currently exists), you can store application code or even data in IPFS (using the http-gateway just like you did now).
Blockstack provides naming, identity and security (you know what public key is connected to "myname.id").
Opera was very much a not-dubious company. But that is what it has turned in to.
-- I use Firefox as my main work-browser, and have for a long time, and the last few years I've used Vivaldi as my main personal browser.
I find it easier to just have separate browsers rather than do anything more advanced for context. :)