Hacker Newsnew | past | comments | ask | show | jobs | submit | anonymouse008's commentslogin

“The way out of interchange”


Good use of tech. Hardest thing will be corrosion on the fabric electrodes. Muse S has much to teach if you haven't looked at them yet.


We don't use fabric electrodes, we've developed our own conductive silicone. The other thing to learn from Muse S is that mastoid (over ear) electrodes are nearly impossible. We have comb electrodes similar to dreem.

Though, I don't think corrosion is the issue with Muse S, the electrodes tear as I understand it. Either way, they are not robust enough.


Aero-engineers: why can't we make airfoil kits to make certain vehicles 'air worthy'? A 10k addon to your current sedan to make it short take off and landing sounds way more fun than anything else.

I understand that weight on ground for stability is completely different than air travel... but why not create a whole class of vehicles around this premise?

The only one I can remember is the SkyCar from Moller. He was a little ahead of the game with petrol based quad motors.


LOL> uh. yeah cars are just WAY too heavy. You'd need some very large airfoils and quite a bit of power over what you would typically use in a GA aircraft. For example, i can move a Cessna 172 around on the ground with my bare hands. Good luck doing that with a sedan.


How much should one trust RLS? Reading PostgREST, it looks like you could use a JWT parameter to enforce a policy - whether individual user or group based.

I really love the idea of RLS, but wonder at it's provable security properties.


RLS is rock solid. That's what Supabase leverages to create access policies and more. They have a very good example of how it works and how powerful it is in their docs: https://supabase.com/docs/guides/database/postgres/row-level...


Last I looked (several versions ago) RLS for `UPDATE`s was not great. Checking now... I see the same problem remains for `UPDATE`s, that you can't see old and new values for the affected row in the policy code. The workaround, when you need to see the old and new values, is to use a `TRIGGER`.


Not an expert but my impression is that RLS is not only rock solid, but extremely more testable since you can construct sql queries that test virtually any access scenario


You don't have to use RLS. You can do permissioning in VIEWs and TRIGGERs.


CPC of $2500 isn't bad for the potential upside


Even if you have good enough insulation; you still have to dissipate the Peltier plates heat… which makes little believable sense to me without a hefty heat sink


I have good relationships with seafood and food distributors though have never thought battery powered cooling packing made sense here. What exactly am I missing? Even in vaccines this is a solved problem with fewer points of failure if you just add telemetry.


> Even in vaccines this is a solved problem with fewer points of failure if you just add telemetry.

It's not a solved problem, and in fact it's a serious problem, pretty much anywhere outside the OECD.


I'm thankful.

Congress skirted their duties for 40 years. This legislative / executive codependency then created a tightly connected and interdependent governance system, outside the purview of the judicial 'checks and balances.' This is why things like warrantless mass tapping and the Patriot Act became 'good law.'

We are unwinding decades of bad governance. This is a joyous occasion, along with the ACJ decision from last session.

Before anyone says there were still checks and balances - if you feel the need to, you have no idea what Cheveron meant


> Congress skirted their duties for 40 years.

Delegation dates back to (at least) the early 1900s:

> Since 1935, the Court has not struck down a delegation to an administrative agency.15 Rather, the Court has approved, without deviation, Congress's ability to delegate power under broad standards.16 The Court has upheld, for example, delegations to administrative agencies to determine excessive profits during wartime,17 to determine unfair and inequitable distribution of voting power among securities holders,18 to fix fair and equitable commodities prices,19 to determine just and reasonable rates,20 and to regulate broadcast licensing as the public interest, convenience, or necessity require.21

* https://constitution.findlaw.com/article1/annotation03.html

And from 1825:

> It will not be contended that Congress can delegate to the Courts, or to any other tribunals, powers which are strictly and exclusively legislative. [23 U.S. 1, 43] But Congress may certainly delegate to others, powers which the legislature may rightfully exercise itself.

* https://caselaw.findlaw.com/court/us-supreme-court/23/1.html

Delegation is a key component of governance and predates the US with Ministers of the Crown, and once the the US was formed with Secretaries/Directors/etc, all of latter which are approved by the US Legislative branch through (e.g.) Senate-approved appointments.


This is not about delegation. This is about interpretation of the limits of delegated power. Under Chevron the executive agencies decided that without check. Before Chevron and after Raimondo it's the courts that decide. The 40 years of Chevron were an aberration.


> Under Chevron the executive agencies decided that without check.

That isn't even close to being the truth. Under Chevron congress was always free to pass statutes as detailed as they want to avoid the kind of ambiguities that would even apply to Chevron in the first place, and judges have always had the oversight to ensure that an agency's interpretation was a "permissible construction of the statute".

Those are two literal checks. I have no idea where you ever got the idea that executive agencies were "without check" but that is just plainly wrong.

"First, always, is the question whether Congress has directly spoken to the precise question at issue. If the intent of Congress is clear, that is the end of the matter; for the court, as well as the agency, must give effect to the unambiguously expressed intent of Congress. If, however, the court determines Congress has not directly addressed the precise question at issue, the court does not simply impose its own construction on the statute . . . Rather, if the statute is silent or ambiguous with respect to the specific issue, the question for the court is whether the agency's answer is based on a permissible construction of the statute."


> The 40 years of Chevron were an aberration.

The Chevron ruling was codifying what was already happening for decades:

> When a challenge to an agency construction of a statutory provision, fairly conceptualized, really centers on the wisdom of the agency's policy, rather than whether it is a reasonable choice within a gap left open by Congress, the challenge must fail. In such a case, federal judges—who have no constituency—have a duty to respect legitimate policy choices made by those who do. The responsibilities for assessing the wisdom of such policy choices and resolving the struggle between competing views of the public interest are not judicial ones: "Our Constitution vests such responsibilities in the political branches."

* https://en.wikipedia.org/wiki/Chevron_U.S.A.,_Inc._v._Natura...

There is plenty of oversight in interpretation and Congress does not need to micromanage interpretation or implementation. Delegation as a principle of government pre-dates the formation of the US with Ministers of the Crown, and was continued post-formation as that's why there are Secretarys of Department X/Y/Z or Directors of Agency A/B/C.

The People (through their representative in Congress) are fine with agencies doing the interpretation. Those agencies are headed by an Executive of The People (President), and are run by administrator who are People-approved (through Congressional hearings and Senate approvals). The Legislative branch can dial up and dial down the flexibility of interpretation any time they want through Acts that change how the department/agency involved works, or through altering leadership (Secretarys, Directors) of the agencies.


Chevron codified what had been happening since the New Deal. Raimondo codifies what has been happening since Chevron! Pretty ironic. Each case was a bookend to the preceding trend.


It wasn't really "without check" though, was it? Courts could still rule that an agency exceeded its authority, it's just that Chevron meant the courts had to give deference to the agency's interpretation if Congress left the law ambiguous – and if the agency's interpretation was "reasonable."

So for example, if a law grants an agency power to regulate pollution emitted into the air, the agency already couldn't simply decide on its own that it was also able to regulate toxins dumped into rivers. But it could decide, if the law was vague on this point, whether "emitted into the air" included car exhaust vs. only stationary factories, for example.

The principle was that if Congress left a definition or meaning ambiguous in the law, it's implied that defining its precise meaning is part of the regulatory work they wanted the agency to do. Now, instead of that principle, the meaning of every ambiguity is open for litigation to select a different interpretation if the court finds it preferable to the agency's.


It pretty much was "without check" unless the action was facially against the text of the governing statute for the agency.

Your example about pollution in the air and in the water is actually close to a good one: The EPA decided recently that they had power over CO2 emissions because of some very mild toxicity, even though that's not the reason why anyone wants to control CO2 emissions. They could easily have argued in your scenario that toxin dumped in the water evaporates and ends up in the air, so it's in their purview, and it might not be wrong under Chevron.


It's more clear if you use the word vest and divest rather than delegation. Congress cannot divest its own legislative powers, nor can it vest them in another branch.


Exactly.

If Congress seeks to regulate air, water, land, and space pollution, from American companies, they should appoint industry experts who intend to leave public sector jobs for lucrative private sector jobs by going to work for the companies the laws need to regulate. It’s worked great for politicians who become lobbyists or prosecutors who go work for big law.

It’ll work great here too.


Absolutely! We should also make sure that no one in agencies is safe. It’s only the industries and courts which can do the work - only for a short while, you know, till congress gets less gridlocked.

Seeing how polarized and partisan things are, it will only be a few decades!

Plus seeing how some of the court positions have been, I can only think that lobbying is going to become a massive business ! So much growth!


regulatory capture has joined the chat


> This is why things like warrantless mass tapping and the Patriot Act became 'good law.'...Before anyone says there were still checks and balances - if you feel the need to, you have no idea what Cheveron meant

It's wild to think that either of things couldn't have been possible without Chevron. Congress would have passed anything required to allow those to become law.


What is "the ACJ decision from last session"? For that matter, what is ACJ?


ahh yes our good ole non partisan judicial system will surely save us


Yeah, I feel most invoicing forgets it can be both time and fixed cost // then also only cares about generating, rather than tracking the flow afterward.

Might be just me though?


that’s exactly what we think too! and we will support fixed and hour/qty based too!

also we will match incoming transaction for auto matching, notifications for missed payment and so on!


Wait, so you compile a swift executable that’s callable from js? How would one distribute this client side in browser?

I’m not smart enough to understand this. I love swift, vapor and node individually, I don’t get it together


Node’s a server-side thing, so I don’t think you’d distribute these in the browser.


It's a desktop thing too when working with cli tools or electron, though I've found that for electron I just end up calling other languages via IPC on stdin/out. It might not be as fast as ffi from node, but its certainly leagues easier and clearer.


Other way round.

NodeJS has had FFI for over a decade that allows you to call functions in .dylib/.a/.dll on Mac/Linux/Windows. I've used it extensively to link with libraries provided by USB device manufacturers to avoid direct USB interfacing.

See:

https://www.npmjs.com/package/ffi

This let's you call Node from inside Swift.


You wouldn't run this in the browser. On the frontend, this would be useful for Electron apps (which run an embedded Chromium for the UI and a local node server for business logic and interfacing with the operating system) on MacOS. On the backend, this might be useful if you have a node-based API and want to share some Swift code between your iOS frontend and node backend.


It might be possible to compile it to web assembly and then call it in the browser.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: