smashed

> Do things e.g. pfSense support that already? "Hold" an outgoing connection from the moment the SYN is observed, notify whatever client, and only allow if the user clicks?

Not that I am aware of.

This is a desktop centric workflow where the user can react live to an application that is sending traffic.

Your typical network firewall will apply a set of static rules and the decision to log/reject/drop is done ASAP. Waiting for user input is impossible.

Some systems can show logs of recent blocked traffic, and allow an admin to quickly generate an exception/allow rule for blocked traffic but that's pretty much it.

This article is a few years old but it compares both really well:

https://adamj.eu/tech/2019/04/03/django-versus-flask-with-si...

Flask works for simple projects but as your needs grow, the built-in and extensive Django ecosystem will have you covered. And as seen above, Django in its simplest form is no more complex.

Some people really don't like the Django ORM, so in this case you might avoid Django altogether. It's possible to use Django without its data layer but it's a big part of its value.

Also if you are building a pure API project, FastAPI is worth checking out for a streamlined process. Django Rest Framework works too, but is an extension.

On Gitlab.com you need to input a valid credit card once in order to validate your account, but you can still get 400 minutes on shared runners for free.

This is used to combat abuse and crypto miners, they don't actually charge the card.

You can also connect your own private runner to either the saas or self-hosted gitlab-ce for free, you just have to provide your own runner.

I understand that communities evolve, mutate and sometimes divide over time. Online communities are the same, maybe just faster and larger.

The author of the article though feels a bit odd? What exactly is the endgame here? You divided a subreddit and created a new one, that's good for you and your "disciples" I guess...? Like what the hell I've had just read...?

Some people treat http as a pure transport/network layer and the actual body as the app-level layer.

In such an approach, any http-level error would be a network, server maintenance or other unknown/fatal error type of things.

App errors are encoded in the response body in a app-defined way.

It's not a completely bogus way of handling things, as long as it is perfectly consistent throughout the project and properly documented, which is rarely the case.

Interesting. I am new to the space and have never been exposed to the main alternatives you mention in the Readme. Here's my thoughts after taking 5 minutes through the doc:

I was interested by the "data" part of the framework that is mentioned in the tagline. I saw live updates, fast sync of data with the front-end.. that all seems nice and solves a real problem..

Do you have more advanced examples on hooking up a live streaming data feed and building dashboards over that live data?

I looked through the readme and documentation and all I found was an example about incrementing a counter when you click a button.

The bird changing hue was also a bit worrisome. In a sense it's great that it refreshed fast, but then it mentions it's refreshed by a timer? We clearly see a slider widget being manipulated, that means it should be changing a value in state and the UI should refresh when that value changes.. why is the timer needed?

Yocto has made great progress into fully reproducible builds too, just fyi..

Yocto is fine and very powerful. I work with it daily, producing a "just enough os". It's amazing to produce a full OS with fully traceable sources, versions and licensing of everything, even CVE patch tracking.

If you work long enough in embedded Linux you will encounter it for sure.

I would advise against starting with yocto for a beginner. It is very complex, most tasks look more like weird magical incantations than actual code. It will discourage many, as things will feel completely incomprehensible for months.

You kind of have to know the problems it solves to appreciate it.

In another comment I pointed to OpenWRT and Raspbian. They have real world devices they target, you can git clone, build and flash real devices to get you started and see real results faster. Their build systems do not have all the complexity of layers and are easier to follow.

Since your context is embedded Linux, I would recommend following Raspbian development for general purpose SBC embedded Linux or OpenWRT for smaller, more specialized devices.

Both systems have code bases and build systems that will build root filesystem and kernels for a wide range of devices.

By following development of a device (aka target) that interests you, you will see how drivers are stabilized with various patches applied over time.

This.

In fact, most embedded Linux thingy will be running the busybox version of core utilities instead of gnu coreutils for binary size reasons.

I other words, even gnu coreutils is too big.

I know there's been a lot of gripes against git-flow but I think one of the reasons it had such an impact is that project maintainers/leaders are looking for some sort of "workflow" or process around git.

As a project grows, you want some process around how to name branches, when to use tags, how to handle merges, from which branch to base your work on, etc.

Git flow gave all the answers in an authoritative way. You could just say to junior team members/contributors that the project uses git-flow and send them the link to the doc.

I applied git-flow to my projects but simplified the process, eventually abandoning almost all its principles. It did give me a starting point to think about what we really needed, what is important and how to communicate it with a team.

One particular process I am quite fond of is to use the develop branch as a free for all integration/testing branch with automated deployment to a test (dev) environment with absolutely no guarantee of working whatsoever to any stake holder. This allows devs to demo their work, collaborate and spot conflicts early, without being slowed down by fear of breaking something or waiting for a code review.

Unlike git-flow, that develop branch is a dead end. It does not get merged to master or any other branch ever and gets force-push (reset) when things go wrong.

Feature branches eventually get proper code review, their history can be cleaned up and eventually merged (or dropped) via a proper pull request.

The solution is very easy for consumers looking for a real privacy solution:

Use a browser that is not made by an advertising company.

In other words, just drop chrome. It has never been easier to do, with Edge and Safari readily available on all major platforms and Firefox for those who prefer it, and of course the many other chromium forks that are around.

There is no reason to be dependent on chrome today. There was a few years where it was overly dominant and very hard to avoid for compatibility and performance reasons, but that is just not true today.

Personally I use Firefox on android and desktop and I don't miss chrome at all. I uninstalled (technically, disabled) it on mobile as Google widgets like to open links in it otherwise.

I have chrome on the desktop as I work in software so I need to test compatibility with it, but that's it.

Funny to see the site itself sitting at the 3rd position right now and the AI summarizing its own page. It seems to be using content that is not shown on the page though, maybe an og:description meta tag. Otherwise it would be spiraling in an infinite loop of summarizing itself.

Small comment: the "dehyped" title does not seem very useful. For most articles it is almost the same as the original title, just rephrased. It should summarize the conclusion or whatever the meat of the article actually is. Repeating the same thing or similar is just a waste of time and space.

Also it seems broken on the site itself, but that could be the AI getting confused on what the actual page title should be. It picked the top story as the dehyped title, which I guess is understandable but when generating a title for a news feed, it's wrong.

If I remember correctly, the main argument against web sql was that it really was just SQLite disguised as a web standard. I.e. there was a single implementation which defined the spec: SQLite. Every browser implementation relied on it.

In retrospect, with the chrome monoculture we have today, this seems like a silly argument but at the time it was a legitimate concern.

He's saying the tech stack changes over time and gets updated. Probably going from on-prem to cloud with some saas sprinkled in, as many other industry. What does not change as rapidly is the strict regulations and particular needs of the healthcare domain.

I like the fact you qualified ingress as "reasonably" painless.

Frankly it is not painless at all. Ingress is complicated and there is a ton of way to configure it, with all the forced tie in with the cloud provider's offering, be it l3 or l4 load balancing, various proxy services, etc.

It's not easy at all either on docker-compose. You have to roll your own proxy container and take care of TLS termination, cert renewals, manage specific headers and config, etc.

I am not sure what exactly I want to add to the conversation, only that either way, it's not "easy". I'd be glad to be proven wrong if you have a specific solution that makes ingress really painless.

Heroku had their share of problems recently no? It seems mismanaged and on the way down, sadly..?

And you say Heroku, "etc", but the thing is that there is very little heroku-like alternative. What "etc" is there really?

The real alternative is a Linux VM with docker-compose.

Once you outgrow that, managed kubernetes is the logical next step, even for a small team.

I was at a pub recently where they had a full kitchen but no waiters. You had to line up around the bar, catch the attention of one of the super busy barmen, yell your food and drink order, pay up, then they prep your drink and give you a buzzer that will eventually tell you to go grab your food yourself at the kitchen window.

They had the guts of slapping a mandatory service tip on the bill and the machine asked for an extra tip. I was wondering what service I was actually paying for...

At this point of mal-service, I'd take an automated machine.. could not be worse really.

Or yes, avoid the experience altogether.

Please correct me if I'm wrong but XWayland is about bringing an X11 app to show up its output under a Wayland desktop.

I.e., an app that has not been updated yet to work with Wayland.

You can get an entire wayland desktop to display on an X11 backend. This was used in development when there were no display drivers compatible with Wayland but you still wanted to work on app compatibility, etc.. The flow will look like App => Wayland => X11.

Not sure how practical it is for your use case.

Not to be rude, but you let your passport in a laptop bag with an actual laptop inside in plain sight in a mall parking lot because it would be just a couple minutes?

You're not at fault here, the thieves are, of course. Stealing sucks, and they probably did not care about your passport at all, but still...

I've done the same in the past, leaving my passport and stuff in the car in places I thought were safe. I got lucky so far, but I'll try to remember I was just lucky and be more careful in the future. Thanks for sharing.

That is a bit harsh..

Nouveau will bring up you're Linux desktop just fine and connect all your monitors.

It will run OpenGL apps and light games.

Last time I checked it could not boost the clock and push most chips to high performance mode.

This is mostly 100% Nvidia's fault of not opening up the specs.

Otherwise what nouveau has been able to reverse engineer is just amazing.

The nouveau driver is so much less painful to use, it just works completely seamlessly. If you don't need the extra performance, it is not worth the trouble to install the Nvidia blob.

You are trolling.

JNLP still sends shivers down my back.

It is still in use to this day. Hugh.. It sucked when it was new and still does just as bad.

I agree. I've seen Python being taught in Physics and hard science university cursus as an introduction to programming 15+ years ago.

How many cruise autonomous vehicles are operating in SF versus Waymo's?

It seems that Cruise is involved in incidents every week while waymo is doing mostly fine?

Although the news coverage often lump them both into the same group, reporting that Yet another incident involving autonomous vehicles today...

Just wondering if maybe Waymo's tech is better or if they are just running at a much smaller scale.

I was in SF recently and saw both brands on the streets in equal numbers (once each).

The graph in the article does not even cover a full month.

There is a downward swing but that could be a normal change in any given month?

A 6 month to a full year graph would show a better trend..?

"Scientifique" is a french noun for scientist and is pronounced just like you would pronounce scientific.

Could be an easy mistake to make.

> both electron shells. also come with their sandbox already.

Not sure about the 2 specific apps posted, but web applications packaged as electron apps often do so in order to easily escape the normal browser sandbox without having to prompt for permissions? Or even call into native code which would be impossible from a web app.

I would not think that because an app is electron based, it is sandboxed from your system.

Ideally if you can run the same app under your normal web browser, you'd be fine. I see many people install the Slack app for example, but the web version works just as well within the full browser sandbox.

What does the sentence you quoted even mean? This reads like a rough first draft that needs to be clarified. I don't get it at all.

Nothing wrong with applying tried and tested UI elements, that's how the majority of GUI software is built.

Coming up with a long winded article about how you invented a new way of managing your downloads and how great you are for coming up with this new way of doing things when you actually mostly copied your main competitor's UI is disengenious.

And the dataclass serves as documentation for the available attributes and type safety..

It's really the way to go, takes a minute or two to define and saves so much headaches in the long run.