janinge
However, previously you got an exemption on the 7 day TTL on Web Storage, by being installed as a PWA. This must have been too generous. I guess they figured that if you combine lack of stable local storage, with no support for the Background Synchronization API, nobody should be able to implement anything of value on top of these APIs.
And just in case this isn't enough, let's just hide the install option even deeper than before. On iOS the path is now something along the lines of
1. Tap site's domain name 2. Meatballs menu 3. Share 4. More (Meatballs again) 5. Scroll until you find "Add to Home Screen" 6. Leave "Open as Web App" switched on 7. Add (upper right corner)
There is no obvious install prompt, and no clear browser level affordance. Nothing in the flow even tells you if PWA functionality is supported by the website. You might end up with just a weird shortcut that opens a URL full screen.
If you'r in the Apple ecosystem and are using AirPlay with your smart speaker(s), it's however possible to also play synchronized audio across to your own DIY speaker setup, using another open source project.
https://github.com/mikebrady/shairport-sync
Or you could of course choose to only use your old dumb speakers with this, and they will pop up as easily selectable sound output devices on all Apple devices connected to your network.
Or combine it (and librespot[2], owntone[3]...) with Snapcast to create a virtual speaker for your whole house that shows up everywhere.
Jitsi Videobridge does this by receiving simulcast streams from each participant. This server individually picks out streams and qualities that will fit in each recipient's downstream pipe based on measured bandwidth and configured priorities (e.g. you could choose to give more bandwidth to those who are actively speaking, or shut down all but the last N speakers video streams).
Yes, the available network bandwith on a Jitsi Videobridge could be a bottleneck. Each meeting need to fit on a single bridge instance. However, using common servers connected at 1 Gbps or 10 Gbps, it shouldn't be any problem to have meetings with substantially more than 2-4 people. Say a HD stream from most webcameras outputs 3 Mbps at full blast, with 50% overhead due to the simulcasting. That's over 2000 participants on a single server connected at 10 Gbps, all receiving all video streams in full quality.
For meetings with 2 participants the streams run peer to peer, so here you get the best possible latency and quality.
We've set up Jitsi on a VPS instance at a nearby provider, and have not seen any problems with meetings of 10-15 people. Stability and performance also outperforms all the other solutions I've tried. There's currently a bug in Firefox's simulcast implementation, so if you have any participant using this browser, this feature gets disabled for everyone. Even with this issue, I haven't noticed anything but excellent performance with this few number of participants.
The following article might also be interesting.
And are there any property of MTProto that makes it infeasible to replace AES IGE in a later revision of the protocol?
Most pages shouldn't need a refresh when you go back after a few seconds or minutes. What annoys me are websites that set stupid expiry times or Cache-Control values.
"Mastering engineer Bob Ludwig created ultra-loud master of Led Zeppelin II, but his version was pulled when it skipped on a record player owned by Atlantic boss Ahmet Ertegün’s daughter"
Smartphones mostly use wireless networks and cell towers to determine their approximate location, which can be easily spoofed, except for the current active cell (which could be miles away). If devices had to acquire GPS fix every time they reconnected to a network, batteries would drain much faster. And satellite navigation doesn't work properly indoors. Civilian GPS can also be spoofed.
Manufacturers would probably prioritize usability over rectifying such a "problem" which never had bothered anyone before, except maybe if there was PR involved. I think there's still no way to list all configured wireless networks on iOS devices? Fixing this would probably improve privacy more (if people cared) than this randomized MAC feature.
Current i.MX 6 silicon aren't able squeeze out more than 470 Mbps from their Ethernet MAC.
http://cache.freescale.com/files/32bit/doc/errata/IMX6DQCE.p...
ERR004512
Google Drive could maybe be useful if there existed some working FUSE implementation that would fit on cheap single board computers like the BeagleBoards and Raspberry Pi.
One of my servers were once used in a amplification attack (DNSSEC...) for a few days before I noticed. I guess Hetzner didn't detect this because just the uplink got saturated. Had to manually request a null route so I could SSH to another IP alias on the box. I wouldn't mind if they automatically did this for me since the offending IP would be unavailable either way. At least they don't charge you for DDoS traffic, like my current European budget provider does.
If you move to something like Cloudflare, make sure to at least firewall off everything but their IP addresses. Otherwise it will be trivial for the attacker to connect to all the port 80's in the IP allocation to the provider they know you were using, and compare the responses to what they get from Cloudflare, to obtain your service's origin.
YouTube often fails to load videos here, and I have to switch between bandwidth settings (up/down, doesn't matter) to get things going.