This is also part of Gitea. Which makes since because Forgejo is a soft-fork of Gitea.
744 karma · joined December 9, 2020
This is also part of Gitea. Which makes since because Forgejo is a soft-fork of Gitea.
I use my GitHub account to make bug reports, small pull requests, and silly personal projects. It is not that important. I want to sacrifice security for convenience on it, and that should be my choice.
I also do not agree with the argument this secures the supply chain because:
1. It ignores supply-chain attacks from people who already have repository access.
2. Most big companies (ie. Google) are probably already using 2FA.
3. And if people are automatically pulling code from random people/groups without checking it... maybe that's what actually needs to be banned.
[0]: https://wiki.mozilla.org/Add-ons/Extension_Signing
[1]: https://developer.apple.com/documentation/safariservices/saf...
And the only way to turn that restriction off, is to either use Firefox Nightly or Firefox Developer Edition (which is a beta). If you want to use stable Firefox, because you like having a stable web browser, you just can't turn the restriction off. Period. The closest thing you can do is installing it as a "temporary extension" which uninstalls itself when the browser restarts.
It's kind of ridiculous that the default browser of most Linux distros has a Apple-esque mentality of "we get to tell you what you're allowed to install."
From the sounds of it, the only situation where this PR-mirroring works properly, is PRs without any comments, which I imagine are quite rare. But if your PR does have comments, then you not only have to sign up for Gerrit anyways, but you're also responsible for keeping the GitHub PR and Gerrit PR in sync. That sounds horrible.
I've also been on Discord since 2017, and I've done it many times. Especially on servers which put voice channels right next to text channels. And I'm not the only one either, judging by another comment[0].
[0]: https://news.ycombinator.com/item?id=36439417
> The app even prompts you if you're sure about joining under some circumstances.
The app is even worse! It brings a full-screen pop-up and if you haven't granted Discord microphone permissions, it will bug you, every, single, time.
As someone who doesn't use voice channels, I can't even count how many times I've accidentally joined them because I mis-clicked. And then I have to find the "end call" button because, of course, it's small and located away from the channel itself. It is so unbelievably annoying.
The best feature Discord added recently was the ability to hide channels, so I can finally, once and for all, forget about voice channels.
Yes, yes they could. That's not and shouldn't be Apple's problem. That's your workplace's problem to regulate how the device is used on-site, the government's problem to regulate how it can be used in public, your household's problem on how it can be used in private, etc.
The device will be inevitably jail-broken anyways, so a walled-garden isn't going to stop bad actors.
Not to mention, most of the things you mentioned can already be accomplished with less expensive and much more subtle devices, like a standard digital camera. And those device definitely don't try to prevent abuse. (Imagine if your camera refused to take a picture because it thought you didn't have permission!)
At least in this situation the archived data is public.
Android's better than iOS in that regard, but that doesn't mean it isn't still terrible. Sure, you can sideload apps, but you still can't run as root unless your device's manufacturer allows it. And sure, it might have a built-in file manager, but in newer versions of Android, you can't read/write to /sdcard/Android/data without a separate device.
And this trend is even infecting non-phone devices as well. You can't install extensions on Firefox if they haven't been signed by Mozilla. The only way to disable this restriction is to use a fork or beta version (Developer Edition or Nightly).
Yeah, that is probably the best solution. Most mobile OSes do that by default now anyways. Desktop Linux has Flatpaks and Snaps. Windows has UWP apps. And I think MacOS has its entitlements system IIRC.
If you don't absolutely trust somethibg, you shouldn't allow it to run unrestricted.
Most chat apps like Discord will automatically include an embed generated from a URL's metadata when present in a message.
It's the same code (presumably) but Chrome OS's version was compiled with metadata that said it was running on Chrome OS and Linux's version was compiled with metadata that said it was running on Linux. And that metadata is later embedded into the license request which Xfinity's servers check.
Of course, that's just my assumption from what I understand. I can't verify anything due to how obfuscated Widevine is. But due to how long-lived this problem has been, the two Widevine versions having the exact same version number (4.10.2557.0), and that everything else Widevine-wise works, I'm inclined to believe that this is intentional.
I got it to write a pro-fossil fuels essay, and it gave some pretty typical pro-fossil fuels talking points (here's some excerpts):
> In contrast, renewables are often hampered by their reliance on weather conditions, and they require complex and expensive infrastructure to be built and maintained. For example, solar panels can only generate electricity when the sun is shining, and wind turbines only produce power when the wind is blowing at the right speed.
> In contrast, fossil fuels have a much lower ongoing cost, making them a more cost-effective option in the long run. This is especially important for developing countries, which may not have the resources to invest in expensive renewable infrastructure.
> The construction of solar panels and wind turbines requires the use of materials such as concrete, steel, and copper, which are extracted through processes that generate significant greenhouse gas emissions. In contrast, fossil fuels like coal and oil are already extracted and ready to use, reducing their overall environmental impact.
We live in the 21st century and have proper APIs to detect features now, we should not be relying on parsing this user-agent string which is 90% legacy-garbage anyways.
I mean, sites blocking compatible browsers is such a common problem that not only do user-agent switcher extensions exist, they're also some of the most popular extensions out there!