Typo on “Free, Open Source Software does not a social movement make.” Presumably “does not make a”?
uuh, I see Zed's been available for Windows for a month now. That has always been a blocker for me. I'll definitely try it out.
Yes, forks remain as they are. Yes, the fork network has a shared data repository on GitHub.
Consequently, rewritten history will break history compatibility, possibly requiring manual fixups on forks or work based on it.
I can't currently use VS Code with extensions to check, but you should be able to uninstall or disable Copilot and MCP. When I search for MCP in the settings, I see several settings, some of which can restrict MCP use/start.
Alternatively, maybe you want to try a VSCode fork, like Codium (dunno if they only drop telemetry or some of the Copilot stuff as well now), or an alternative similar IDE, like Geany.
Looks like it's just random commenters taking random guesses because those have happened before.
What is a “repository reset”? One commenter writes:
There was a temporary similar “outage” back in July with rewritten history, apparently something inappropriate was recorded in the repo history they wanted cleaned out. The repo came back after that. I have no idea if this is the same thing, or if they just got tired of maintaining it.
Seems strange to me. You can prep locally and then force-push. I don't see why rewriting history would require taking the repository down.
"Vibe" coders produce code though, right? This is about analysis and issue reports. They didn't produce code.
In what way did they “gamify” their unit tests? You mean through presentation of test state/successes?
I always read the weekly post title and am tempted to write and comment. I've written an entire post before. But then I notice it's in c/cybersecurity - which my work is not in specifically. 😅
Now if only I had the motivation and commitment to create something similar!
In my interpretation, the gains will be
- Google Store apps will have identities linked, making it harder to mass-produce and mass-publish scam apps
- Enabling app installs outside of the Google store will have an additional barrier to combat scammers interactive pressure, maybe a cooldown of 24 hours or something like that
So they're addressing students and private hobbyists, but not open source and hobbyists willing to publish.
Sounds like it will be a kind of sideloading onto your own devices.
that allows experienced users to accept the risks of installing software that isn't verified
So for F-Droid, a vetting and curating publisher, users will have to go through this expert process. The announcement that activation under pressure will be prevented makes me thing of a time cooldown, like activate now, and it becomes active by tomorrow, 24 hours later.
Scamming is a real problem, and to a degree, it may end up being a good thing. As long as Google does not take this opportunity to push hidden agenda of increasing accessibility and choice, to seize more control not for security but as market and platform strategy.
F-Droid says they don't want to impersonate other projects in order to be able to publish their projects, arguably decreasing security, which is a valid concern. As long as there's a setting to allow this kind of sideloading and the use of F-Droid like before, I guess it is what it is, and may be acceptable.
If only they had started from where they are now. It's plainly obvious there's these kinds of users and use-cases. Did they really need "the community feedback" to learn about everything outside of their primary "linear" users?
-3
How Copilot Studio uses .NET and WebAssembly for performance and innovation - .NET Blog
(devblogs.microsoft.com)
view more: next ›
Great writeup, good argumentation, and excellent sourcing, linking to external resources