[–] 5 points 1 year ago* (4 children)

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.

  • source
  • [–] 7 points 1 year ago (6 children)

    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.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago (2 children)

    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. 😅

  • source
  • [–] 2 points 1 year ago

    In my interpretation, the gains will be

    1. Google Store apps will have identities linked, making it harder to mass-produce and mass-publish scam apps
    2. 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
  • source
  • parent
  • context
  • [–] 4 points 1 year ago

    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?

  • source
  • view more: ‹ prev next ›