smashed

Of course. A captive portal can also be more sneaky and mangle the packets to redirect them to their own DNS service, since it's not encrypted.

But that's the beauty of iodine. It will still work because if the captive portal's name servers actually fully resolve requests, it will contact your upstream iodine controlled name servers and forward the response as-is, because that's just how DNS works.

Of course it's also fairly easy to detect/block since your DNS usage will be completely abnormal.

You're not really answering why they are important?

Is it because .deb packages will install inside dist-packages and when you run pip install as root without a virtual env, it installs inside site-packages?

I don't really see how this helps though? Sure you won't get paths to clash between the two but you still have duplicate packages which is probably not what you want..

As I understand it, as a library author you either do absolutely nothing and your library will be marked as requiring GIL by default. Nothing to do, you keep on working with that good old GIL and nothing changes.

Or you make the extra effort of being thread safe and you can declare your library as not requiring the GIL.

Now if a user script mixes your GIL free lib with an older lib that has not been updated, well, too bad for them. Even with your hard work, the code will still operate like before, everything gets the GIL treatment.

Normal python devs will need to track down which pesky dependency of their script is causing the GIL slowdown. Kinda sucks but at least nothing breaks.

It's a sensitive, opt-in, and safe way forward. Hard to argue against it, really..

You're saying the cheesecake factory makes everything except the actual cheese cakes?

This is just a normal udp broadcast packet sent to FF:FF:FF:FF:FF:FF / 255.255.255.255. You do not need raw sockets to receive it.

There is an ISC dhcp article here with more info on why they need it: https://kb.isc.org/docs/aa-00379

But I just thought about it some more.. In a normal unix socket, you don't set the destination mac address when sending a packet. You just set the destination IP address and the kernel figures out the destination MAC address using a static, cached or dynamic ARP lookup.

But since the dhcp client has not been assigned the IP yet, ARP would fail.

The DHCP server would need to set a static ARP entry before sending the response, and hope the kernel properly fills the destination MAC. This causes more problems..

Its much easier and reliable to just craft the exact headers required as-per the RFC, especially in a cross-platform piece of software like the ISC dhcp server.

Iptables (aka linux's netfilter) processes DHCP packets like any other packets.

The ISC DHCP server though listens for raw packets and thus completely by-pass the netfilter rules.

This is similar to how you can use wireshark to see raw packets received on the physical port, before any filtering.

Any Linux process running with CAP_NET_RAW can by-pass the firewall in such a way, this includes your typical DHCP server running as root.

The question then should be why is ISC DHCP server using raw sockets? That is probably because DHCP sits in-between OSI layers, it bridges the gap between the mac address world and IP address world.

I'm not sure of the exact technical reason though. The linked SO answers talk about some case where NAT rules could be altering packets, not sure how common NAT+DHCP is used...

In the case of a DHCP client, you do need raw sockets because the Linux IP layer will not let a normal socket send packets with a NULL IP source address.

Can't speak for him but from looking at his work, I think he also likes minimalism and human scale software (if that's a thing).

Of course it's probably not the license he'd prefer but you can still appreciate something for what it is despite the license.

Thanks for your work as a mod.

While I understand it's a lot of work, and some (most?) might be posting low quality answers, my main problem with stack overflow has been exactly that over time, the top answer becomes stale.

The question is still relevant, but the best practice or library, platform whatever changed... That is a problem the stack overflow model has a hard time adapting too.. and it just gets worst over time..

> or if Twitter will still exist for another 10 or 20 years

Years? You are being generous here. I would rephrase that to 10 to 20 months at the rate he's destroying everything.

Yes, and the problem is that people and organizations have grown very accustomed and appreciate all these band aids.

It's very flawed, but the flaws are very well understood and people actually seem to like operating all these workarounds.

Not saying that's good, just what I'm seeing in the field.

I think I was not clear enough.

First there is a floor price on milk. Milk cannot legally be sold below that floor price to consumers.

Farmers are prohibited from selling fresh milk direct to consumers. It's illegal. Period. They can't gift it either. It has to go to a transformer to be mixed with, homogenized and pasteurized.

Dairies and cheese makers, with the proper license, buy fresh milk in bulk to be transformed.

Since yogurt, or cheese, is not milk, there is no floor price. Somehow this often cause the transformed product to cost less than the raw ingredients (milk) that goes into it if you were to purchase that milk as a consumer.

And of course, you can only buy pasteurized, homogenized milk, which is an entire other problems.

This is the case in Quebec, Canada. Other provinces have different but similar laws. The dairy industry is the only one that is protected in such a way, hence why OP commented how crazy the industry is here, as nothing else work that way.

I can relate, fellow Canadian too..

Even making your own yogurt is not cost efficient. It is literally cheaper to buy yogurt than the standard ordinary milk and sour it yourself. Cheese is even worse.

All the weird regulations, price control, quota, duties and import restrictions seem to ultimately benefit mostly the very large industrial transformers, leaving actual farmers with scraps and consumers with ballooning costs.

Very neat indeed.

It says on the about page that it starts a container on demand and gives you the output.

You can see in the output that systemd detects it is running under podman.

No idea what kind of container as a service they are using, and how they secure/lock it down. Systemd is a pretty powerful system, you can make it execute pretty much anything...

Imho, in the context of a GUI library, native would mean it has the native look and feel of the platform and the performance.

This usually means the app is written in exactly the same language/framework/libraries as the built-in, pre-installed core apps.

Nowadays, users don't seem to care all that much though, and will tolerate a lot of crap and bloated apps, as long as it gets the job done.

What exactly is "native" about this?

I remember there was PHP bindings for GTK [0], which at least looked sort of native on Linux.

This could be cool if you can ship a large PHP backend codebase, allowing a web app to become an offline desktop app. You'd probably have to bundle a MySQL instance many cases though :)

0: https://en.m.wikipedia.org/wiki/PHP-GTK

Or what millions of windows developers already know and love: visual basic.

I hope Microsoft comes up with something like it, so we are not forced to learn java in order to add scripts to html pages.

You might be interested in iodine.

https://github.com/yarrick/iodine

And people could not resist the urge to add styling and heterogeneous layouts all over. Weird typography, layouts, alignments and extra padding here and there.

A secret reason why I like to push markdown workflows is that you can't deviate from the site's overall look and feel. Focus on your content, hit publish and it will look good. Even if we change the site's look down the road, the content is still going to be fine.

Tor exit nodes are also frequently blocked or severely scrutinized... I'm surprised it worked..

Maybe since it was official government affairs, any US ip address had to be let through no matter what.

> The brewery "may have been built in this place specifically to supply the royal rituals that were taking place inside the funeral facilities of the kings of Egypt"

Or may be people were just thirsty and the beverage was both nutritious and safe to drink? Why would everything in ancient times be about rituals?

Yup, and in the embedded world, they are used to achieve encryption of the OS firmware, thus preventing reverse engineering of the device, protecting IP and securing devices through obscurity.

I'm thinking of enterprise grade networking hardware for example. Their main OS ROM is encrypted and they will refuse to decrypt if the boot process is altered.

There are no real secrets or user data being protected by the encryption. Heck, actual passwords and user configurations can be stored in clear.

Hmm, from the link you provided, it was a website named freechuckcloseart.com that would autogenerate artwork in the style of chuck close.

I'm not a lawyer but I'm pretty sure this was a trade mark issue. He just had to avoid marketing his product using someone else's name.

What exactly are you saying here?

Keycloak is not open source enough?

It's fine to talk about alternative solutions but you could at least compare and contrast the solutions together and provide some insight into why you are plugging another product...

Lots of comments about how hard of a market it is to get going. Of course it is but just wanted to point out it is possible. Here in Quebec there is "du proprio" [1] which is pretty successful and are getting significant market share. Anyone I know looking to buy is looking at both MLS and duproprio listings.

But I can tell it must be a very tough business. For one they have run continuous TV ads for years. The ads are targeting sellers only almost, and the main message is to save on realtor fees. So I'd suspect it's the listings that are the challenge, in a seller's market, the buyers will come.

Their offers/pricing for sellers is very thorough. Yard signs of course, but also pro photographers sessions, 3d virtual visit thingy (check it out its neat), full legal services to complete the transaction... Their online listings and overall experience is much better than MLS/Realtor websites.

In the end the platform was bought by PurpleBrick which is a slightly different business model I believe, and PurpleBrick was bought by a large credit union that might simply advertise mortgages? They never attempted to expand much outside of the quebec market afaik, but the platform looks like it's here to stay and going strong here.

[1] https://duproprio.com/en/

This exact scam was also performed in developed countries.

The money (cash only for.. reasons..) was collected by a "friend" who would happen to be just right there in the neighborhood.

Very often a car broke down and being stranded far away, no way to pay repairs, credit cards declined for "reasons"..

We called it the "grandmother scam". It does not work with mothers because they tend to recognize their son/daughter voice, even over "bad" connection. But grandma's, aunts and more distant relatives would fall for it.

Unfortunately, if you willingly give cash money to a stranger knocking on your door, there is very little protection/recourse..

You are a few years behind the merger and acquisition market conditions.

The ballast point buy out by constellation brands was probably very much the peak of the craze around craft breweries.

Ballast point was very savy in increasing their unit sales numbers. That 12$ a 6 pack in the California market was unheard of at the time and made sales projections go off the charts.

Of course it was bullshit and unsustainable but their investors took it line and sinker..

The sheer amount of competition with thousands of breweries all over, to me means its a good local business (lifestyle in hn lingo), and a very tough regional business it you want to grow.

Could be something like "2d barcode" that got shortened to "2d code" cause there was not really any bars.

> last time I dealt with Drupal (back in 5 and 6 days), it would actively complain if it could write to its own directory,

That's great, but if you remember drupalgeddon, the attack vector (sql injection) used the url routing system, which very conveniently would map a path to any php function + arguments. Ugh.

SQL Insert a call to php's eval + the code of your choice as the args and voila, SQL injection becomes rce instantly.

I can understand a CMS having read write access to the database, the main benefit is to update the content of course. But mapping paths to executable code, straight into the database is a highly dubious choice.

Many home routers/wifi access point/mesh wifi systems are qualcomm/atheros based.

These system are almost always built on the official SDK provided by Qualcomm, known as QSDK.

QSDK is a fork of an old OpenWRT version (chaos calmer, 2018). Unlike the open source version, it includes proprietary drivers and many changes. Openwrt devs refer to it as a "frankenfirmware".

I don't but I'd like to know.

I was under the impression that it was mostly GPU vram based but once the model is loaded, it could produce output quickly? I'm probably over-simplifying things...