uponcoffee

It's pretty easy to hardcore IPs of doh resolvers and bypass pihole completely.

It definitely lends credibility; versus the introduction from the other comment - that this is the guy that glitter bombs package thieves on youtube - which makes me take this less seriously.

You can mount partitions/drives but something like a yubikey, mic, etc you can't right now

Wsl 2 is really cool, right up until you want/need to do anything with the underlying hardware. No usb passthrough, no hardware acceleration, gpu passthrough is there but it's still early stages as performance is about half of native and vendor tooling is absent, etc

It's getting better all the time though - they tease usb passthrough might be doable as it's already supported with remote desktop

There was a story a few weeks back about Microsoft working on a new android subsystem. So truly coming full circle; android OS stability (via project treble), the vm approach instead of compatibility layer approach, and improvements to hardware sharing/passthrough to wsl 2 mean that they can finally realize what they tried to do with Projecy Astoria.

They'll need to manage their own app store as I can't imagine they'll have gapps//shims out of the box, but that works in their favor if they wanted to do another mobile play.

The termtosvg repo linked by another commentor seems to have a pausable example in their examples gallery, so it appears to be doable.

As i understood it, using raw input keeps the system awake and that may be working as intended (hence they suggest that Microsoft better document that//reflect it in powercfg /requests). The issue is that GeForce experience was requesting raw input when it wasn't necessary.

As i understand it, she was supposed to submit to google for an internal review a fews prior to externally publishing it. She simultaneously submitted and published it, and Google sought a retraction after internal review. She met that with an ultimatum with do X or I'll quit. They took that as a resignation (as Google wasn't going to do X), and accepted it.

I'm not fully informed about what she wanted, but I don't think it was particularly unreasonable, the controversy more has to do with headlines and spotlights about this person and her conduct/history in the past.

It did, but only for a small portion of applications. Others would run very poorly, if at all, depending on the degree in which the application hooked into google services//android api. The original project was more analogous to WINE for *nix systems, a compatibility layer; there where many edge cases that simply didn't work and supporting new versions of Android would require almost completely rewriting it (pre project treble).

The VM route is simply more workable and sustainable. While WINE has achieved some great success, it's still a spectrum. Some software simply doesn't work, some mostly works, some works but performance is abysmal, and some work flawlessly - depending on how deeply they integrate with windows and what APIs they utilize.

It's been a good while since I read the original story, but Wikipedia [0] has some background and should have some citations if you want to dig in further

[0] https://en.m.wikipedia.org/wiki/Windows_Subsystem_for_Linux

WSL's origins are actually as a android subsystem for when they where making a mobile play with the Windows Phone. At the time it ultimately got scraped because it was too ambitious of an undertaking, and got spun off as WSL. Now that android[0], windows OS and WSL[1] are more mature it's going full circle.

[0] maintaining an android subsystem (and various versions as distros) should be easier now for the same reason it's easier for vendors to update phones, project treble.

[1] better filesystem sharing, GPU pass through, WSL is close to natively supporting graphical applications, etc

To me, this seems more like a funnel for recruiting

Can you point me to any examples of that stereotype? Historical employment figures, long form discussions, etc? I've genuinely never heard of that one, and considering the dominant solution in this space is Postman an alternative, female gendered solution could be argued as inclusive.

Dude, dude is gendered. Female version is dudette.

I don't get the gender backlash here, personification has been a thing for a long time and there doesn't seem to be any malfeasance (intended or otherwise) here. It's not lewd, doesn't play to stereotypes, etc.

To me, a basic litmus test is whether you could easily swap the gender without reworking anything. If you can't, it's probably offensive, if you can it's practically gender neutral (naming aside). It's not a catch all, obviously, as it's no replacement for awareness of history, culture, stereotypes etc.

It's easy enough to maintain a rebranded mirror synced to upstream. Instead people seem to want to take offense just for the sake of virtue signaling.

Most projects are from yesterday though. Maintaining or porting legacy php is the reality of most projects.

Their comment was not about distribution, but on going development.

It's easy for an individual site to break youtube-dl, and it happens often. Awareness/distribution don't matter if:

A) there is no central repository for updating the project//distributing updates B) threat of legal action deters maintainers from the project

You don't have to have it exposed to the internet. Without an active connection, clients cant make new passwords/sync, but you can access previously saved passwords that are already synced.

It also doesn't have to be exposed to the internet. You can have it accessible behind wireguard for instance.

I have it, a DNS server, cloud storage, etc on my home lan, and use wireguard to access it on the go.

Not free as in beer, but free as in freely auditable/accessible. Trusting your life to a black box controlled by other people is a lot to ask.

What's the issue though? Their bio seems fine, they're experienced//well known, the signal protocol is open-source with no issues thus far as I'm aware...

I asked this the other day on a similar comment, and the best they could do is critique Moxie for having a savior complex

The linked repo. I mostly agree with you that most of this should be in containers; I should have been more clear to what part of your comment I was addressing.

In regards to docker worldview, this project currently doesn't follow best practices.

And while I agree mostly with this statement:

> Surely all the complexity should be inside the container

The caveat being that complexity should be split up into separate concerns. Otherwise there's little difference between the host and container aside from an extra layer of abstraction.

For example, this repo should probably be split into several containers: cert management should probably be its own container, which a shared volume for certs); php should be rolled into its own container, and php files should reside there; logging shouldn't be handled at the container level; firewall concerns (namely fail2ban) probably should be handled at by the host, or in a container with appropriate permissions; etc

It violates a lot of principles of using containers. There's no separation of concerns here, builds aren't reproducible, it hijacks logging for its own setup, appears to allow RCE of php files on another host in the event it is compromised (does it make sense to store/bundle php files in this container if it's not meant to handle php?)... Etc

Could you elaborate on what's wronf with signal

There are many different ways that ruling could go, some of which could decide the google vs oracle by itself while not universally ruling on wether APIs can be copyrighted.

To add to some good answers...

Succinctly, it's easier and cheaper to port games wholesale than it is to: build out yet another platform for developers to target, on board them, and on board consumers to this new console.

What steam has that consoles don't, are is massive preexisting library. The problem is it mainly targets windows. Their options for bringing this to the console market are either pay for windows licenses (which on top of hardware, would make them more expensive than the alternatives), or port in wholesale. Most console games get a pc (windows) port eventually.

So if they can get proton to a mature point, they'll be the defacto winner of the console wars.

There's plenty of people that simply won't know ownership has changed because they just consume the published extension. They're clearly maintaining two sets of code, one for github and one for publishing extensions; nefarious is a strong word, it is at least suspect.

As far as an NDA goes, that's signaling to the current open-source maintainer that something nefarious is afoot. How would an NDA work? The maintainer hands other their GH account for the new party to commit under? The extension suddenly goes closed source? The maintainer doesn't acknowledge the community at all and rubber stamps anything the new party wants to commit the repository?

It'd be far easier to publicly take over maintaince, do good for a month or so, then silently publish the malware. That was probably the best route here; the maintainer was going to donate most of the monry they received back to the Turkish developers if they did a good job) and they'd have passed the transitory wave of scrutiny from seasoned devs like gorhill.

Gateway is significantly more than a dns provider. It's more like a configurable intercepting proxy where dns is a small facet. The beauty of this is that it's like magic, it just works. No distribution of self-signed certs to all devices necessary because cloudflare already handles tls termination.

Tailscale is ergonomic tunnel management//authentication. Which in itself is a great product, but it's not nearly as granular. Being able to restrict access based on identity provider, individual, etc is a must for a corporate solution.

One of Tailscale's selling points is the data isn't routed through their servers, just between peers. That's the opposite of Cloudflare; their value proposition is centralized granular control, no plumbing, just plug'n play.

Asana is project management, kanban on steroids.

Appears so, I wasn't aware of air table until reading the other comments. Pretty much seals the grave on this one. Low effort clone from a company notorious for no customer support and killing services vs the original that specializes in this... easy choice

The otherside of that coin is feature creep. Docs/sheets so their job fine, so aside from minor updates//fixes they don't need to substantially change; given their user based substantial redesigns should be their own product and if they prove to be substantially better then they can migrate away from the old docs/sheets