Syncthing supports transferring data via untrusted relays (used when two nodes cannot communicate directly) and also supports storing data encrypted on untrusted nodes (those nodes cannot decrypt the data)
The quota includes not just the git repo, but also other services that gitlab offers. In particular the container and package registries are easy to setup in a way that accumulates a lot of data (e.g. by building and tagging a docker image in every commit and not cleaning up old images).
In most cases this will be a misconfiguration and all the quota enforcement is doing is to force people to configure their projects a bit more considerate.
As far as I know, the quota itself isn't new, it just wasn't enforced in the past.
GitHub limits the package registry to 500M for free accounts, so 5G doesn't seem so bad. Git repos themselves usually don't take up that much space; all my 135 projects on GitHub are ~250M combined (quick count, could be off a bit, but roughly on that order). Even larger repos at $dayjob with daily commits typically take up a few hundred M at the most.
Basically you need to either be in the top 0.1% of highly active accounts or do something specific that requires a lot of disk space, but for most people 5G doesn't seem so unreasonable.
That other movie is Threads (1984), the scene you describe is in the trailer and the full movie is available at archive.org (https://archive.org/details/threads_202007)
23 euro cents * 1000 is 230 Euros, not 23. But that is still a factor of 1000 lower then the prices mentioned in https://www.nrel.gov/docs/fy19osti/73222.pdf and other web publications. Are you sure about those numbers and what kind of storage do they refer to?
The Solar Zenith Angle is the most important. This is what changes from winter to summer and morning to night.
Vitamin D production is only made on the UVB range that is highest at midday. Both UVA and UVB causes erythema. Counterintuitively to common sense, it is better to sun bath midday than early in the morning.
If you sunbath at 8 you might need twice as many time to produce the same amount of vitamin D and you be exposed to much more UVA, thus more like to get burn.
Right now, the second example is an actual example of this
===
I know that having to go through multiple troubleshooting steps and not having any of them work can be a real pain, especially when you have more important things to be doing.” Lastly, let them know that you have been looking into the issue and that you think it should be resolved: “That being said, I think we might have gotten to the bottom of this."
===
They forgot to remove the instruction text before replying, I guess this is the modern equivalent of the forgotten Post It note in the bedbug letter.
Are you worried about (cargo-)theft? The way I imagine it:
- (assumption) it takes less criminal energy to steal something when no human observer is around
- lonely road in the middle of nowhere
- well known driving behaviour means it is easy to stop (overtake, then slow down to a halt?)
- enable mobile phone jammer (optional)
- take cargo
Not sure how we're thinking about this now internally. If there was such a technologically adept actor targeting us I'd be more worried personally about safety than the cargo itself.
Wouldn't that work pretty well with a human driver? I don't think most truck drivers are going to risk their life for their cargo. If you block a truck in with a couple cars and block them from calling 911, they'll just try to protect themselves and maybe try to film you if they're brave.
Some things might be easier for the thief, but others I imagine harder.
Multiple on-board backup locations of numerous video sensors means unless the entire vehicle is torched (and even then), some evidence of the people who carried out the theft will probably survive.
When talking about autonomous platforms, a jammer might no longer be sufficient. If communication is lost, how hard is it to launch a drone (or multiple) whose job it is to keep visual contact with the vehicle while increasing distance, and relay the feed up when communication is re-established (how large an area does a jammer affect?).
There are ways to mitigate these defenses/logging (reduce all unique visuals, stop vehicle in tunnel), but also ways to minimize those mitigations.
I'm not sure it's any easier than when a human is present to defend the goods.
I feel like the risk of this is lower than that of rail car theft (find a place where the train slows down, hop on it, steal stuff, leave before it gets to a depot. Or alternatively disconnect the last car and take everything).
Starsky CEO here: Currently, cargo theft is less of an issue than F&F would have you believe, and unfortunately seems more driver related than land piracy.
It certainly is something that I think of, but safety engineering requires simpler processes (because simpler means less things need to go right, which is good when things are breaking). I'd rather pay more for cargo insurance than have more complicated logic that causes more accidents with people.
Easy answer- self destructing cargo. Epoxy Glue tubes which can be exploded on capture inside the container. Goods become unusable, robbery unsubstainable.
Right, IIUC, the stated goal is to reach some standardization (https://www.w3.org/WoT/) for IoT communication. Which, in my opinion would be great for users if it panned out. It is not an ideal situation that people that prefer to control their IoT devices themselves need to rely on a myriad of integration plugins for hass. But I'm not hopeful that this will gain the required industry traction
How is Mozilla gathering personal data from people using WebThings? When I tried WebThings Gateway a few months back, it did not seem to collect/send personal data off site. It allows you to create a public endpoint as a subdomain of mozilla-iot.org for easy off site access (https://github.com/mozilla-iot/wiki/wiki/Gateway-Remote-Acce...) which would allow some tracking I assume, but in general I have noticed no hidden data collection as your comment implies.
>It allows you to create a public endpoint as a subdomain of mozilla-iot.org for easy off site access (https://github.com/mozilla-iot/wiki/wiki/Gateway-Remote-Acce...) which would allow some tracking I assume, but in general I have noticed no hidden data collection as your comment implies.
This is exactly what I'm talking about. It's not about keylogging your passwords or getting into your bank accounts. It's about the subtle metadata they'll be able to skim to start fingerprinting you for advertising profiles, and integrating into learning models. It just disgusts me that this has become the defacto behavior for every tech company now rather than "we want nothing to do with any of your analytics". Data is the new oil times 10, and this is Mozilla doing some exploration.
> for easy off site access
Exactly. The WebThings Gateway on an RPi is behind a firewall. How to access it? Mozilla makes it easy for users to securely access their gateway when remote, by setting up a tunneling service for the .mozilla-iot.org subdomains that users configure during the setup process. Mozilla has to pay* for running the https tunneling services that allow this security. Mozilla wants to protect your security; they do not want your data. The subdomain enables Mozilla's setup process to download and install the cert for the subdomain you create (from LetsEncrypt) onto the gateway, so you don't have to figure it out on your own. If you have your own registered domain name and know how to install its cert and then expose and port forward 443 from your router to the WebThings gateway, Mozilla would be happy because that reduces their tunneling expense. The goal was to make it easy for users to run a secure gateway by default. But with an OpenWrt router approach, appropriate firewall rules and dynamic dns can help reduce the need for the tunneling service, yet keep things secure. Maybe eventually ordering your own complete domain could be part of the setup process, but you'd be paying some 3rd party to make that happen, whereas the subdomain approach keeps it free.
