smashed

"I installed version X.Y.Z and so far so good"

"I tried all available updates and it keeps crashing".

There is no transparency in the published updates. Take that firmware blob (which is probably 99% GPL licensed by the way) and shut up. That's basically what the vendors are saying.

What's ironic is that most OEM are using some sort of out of date openwrt derivatives as a base for their closed source firmwares, which are obvious GPL violations.

You don't need to read every single connection reset by peer or similar network errors..

How is windows accessing the zfs pool exactly? Afaik, there is no zfs support on windows?

Since these are backups, shouldn't they be read only? A snapshot at least would ensure easy rollback.

Also, windows defender is not the only thing that can alter your archives. Think malware and ransomware.. once again a fully read only unalterable storage should be preferable if you care about the data.

Why post this? It's a fluff piece on a supposedly bad Netflix show the author did not even bother to watch.

Or if you had enough space, still waste minutes copying the deleting the file...

Searching for such a simple thing in the control panel was infuriating to say the least. I finally found it, random clicking in every potential places and it was in the most unintuitive place you could think of.

You would expect "keyboard layout" search to bring helpful results but it does not.

If referring to the go programming language, the title should say "golang with PHP"

There is no other way to disambiguate one of the most commonly used English verb from the obscure (in relative terms) programming language.

I somehow got accustomed to the nftables rules format. It is in fact objectively much better than the iptables format in many ways. The native JSON, easy bulk submit to the kernel, built-in sets and maps (the source of the currently discussed CVE though). It really does fix a lot of what was wrong with iptables.

But iptables was probably not broken enough for most users to warrant re-learning everything.

Now, the traffic shaping tool, oof.. I still cannot grok any of it. I've been happy with the fireqos script so far to abstract everything out of the tc syntax.

If it says (nf_tables), you are using the compatibility layer from the iptables-nft package.

It works quite well. Apps like Docker that inserts rules using the legacy iptables syntax are oblivious to the fact that they are actually inserting nftables rules.

It also provides an easy migration path. Insert your old rules using your iptables script then list them in the new syntax using nft list ruleset.

The problem is that it works so well that it seems most users just stayed with the iptables syntax and did not bother migrating at all.

They convinced executives to do a pilot. It was a shit-show. Quick and dirty API endpoints running on bluemix and spewing 500 internal errors at every gust of wind. Nothing remotely intelligent.

There are numerous discussion going on the issue tracker, about adding rust chapter, targeting linux 6.1, etc.. Very cool to see github issues and pull request actively used to keep a guide up to date.

The guide will walk you through the basic of a kernel module. Exposing virtual files under /proc or /sys or messing around with system calls. It will fall short of helping you with the nitty gritty of writing an hardware driver though.

The problem with writing drivers is that you are interfacing with a real-world machine for which you will have very little information about.

Pick a device similar to the one you want to support, but that is already supported in linux. Go look at its source code. This will tell you far more about the work involved. You might realize that there is simply not enough information available to support the driver.

https://news.ycombinator.com/item?id=24760117

The libre office proponents have made numerous appeal to the Apache foundation but I don't think I've seen any statement or response? Basically they pretend it does not exist.

Apache should recognize its project is inactive and archive it, for the benefit of its users.

We've also been educated to buy and prepare our own meals from the most natural/unprocessed ingredients as possible and avoid heavily industrialized/preprocess ingredients for health reasons.

Lab grown meat is the opposite of both of that.

I am just playing Devil's advocate here. I understand the appeal and potential environmental benefits as well.

Source? Instant global communication is valuable enough by itself to attract massive investments and interest. I highly doubt technological advancements from adtech was in any way shape or form required for that.

https://hardwarerecs.stackexchange.com/questions/15086/how-d...

I know there is still much interest in deploying it for internal/employee authentication in large organizations where you control the app login and the employee hardware. Some organizations that wrongly deployed multi factor auth based on SMS have realized that was a poor choice and are looking for alternatives.

There are like 12 domains total in the list...

May be I am not understanding how it works.

This is a misleading graph. Not a single doubt about it. The fact that it is a few years behind does not change that fact. They knew what they were doing in 2019 when they published it. The science of misleading graphs has seen very little change since that "old" time.

Yes they improved, but pointing out this chart is of public interest and interesting.

They are related in some way, since a connection is tied to a user, you will need to open a connection for every active user.

That means solutions like pgbouncer that pools connections might not work as well than your typical app where most connections are interchangeable.

I came to that realization when I needed to delete a file and the function call to use was named `unlink`.

> You might ask why the Messenger API expects a JSON string inside a JSON string inside a JSON string inside an HTML form. You would have a very good question.

Probably multiple layers of tooling and encapsulation to get to the real backend, or just unpaid tech debt.

Also, first the author discovers a GraphQL endpoint. I thought great, just introspect the schema instead of blindly poking around!

But no, the GraphQL API seems to only be used to transfer project LightSpeed payloads which are server generated JS snippets meant to be blindly executed to update the UI. Rough.. I know GraphQL originates at Facebook but I don't think that was the intended usage...

Also, the author's python script seems to be opening a new session on every invocation. This might have triggered the account suspension, since login endpoints are certainly amongst the most heavily monitored for suspicious behavior.

The minute windows update would automatically load the Nvidia driver in the background, the screen would go fully black with no going around.

Searching online, the combination was unsupported by Nvidia and there was nothing you could do.

Linux with nouveau worked flawlessly. No kernel parameter, just boot using a live usb and everything works.

Yes, sometimes you can hit a weird hardware issue and need to revert a firmware blob or add a kernel parameter to disable something. These are rare occurrences, not the norm.

Every platform has its quirks. It's just not true that windows or macos is perfect, you are simply used to all the weird quirks.

You can switch to raw socket and do the TCP syn/ack dance on your own but this is mostly done for network testing/pen testing, as there are more overhead involved, not less.

This is mostly because the OS actually controls the send/receive buffers used by the actual network drivers. The userland program just takes care of filling these buffers and the kernel and drivers take care of emptying them (i.e. sending). TCP flow control is handled by the kernel, freeing the app to focus on its data. This abstraction actually works quite well.

There are frameworks for userland network stacks, when you're working in high performance networking and need to avoid any overhead the kernel could introduce. The drawback is you need to implement the entire stack, including the low level driver, otherwise it would be slower than what you can already do with classic sockets.

Http/1 Keep-Alive was one the earliest protocol performance improvement. It meant the TCP connection could be reused for the next resource, avoiding the overhead if closing and reopening a new connection for every request to the same server.

You can see http/2 multiplexing as a natural evolution to the keep alive. Instead of doing every request sequentially, just send everything you need at once and let the server figure out in which order to process everything.

Concurrent TCP connections do have an impact on all stateful firewalls in your path, stateful load balancers and of course the server itself. A client that opens dozens of simultaneous TCP to request all the resources on a page all at once would be frowned upon, and quickly hit rate-limits and anti-abuse protections. You can call it ossification of protocols but that is the situation even google could not workaround when specifying http/2 and then quic.

Hostapd which manages the encryption of wifi access point in pretty much all wireless aps already supports it. You can supply a list of mac address to psk or obtain the psk from radius server. The mac address is provided as the username, all your need to do is return a different psk depending on the mac address. I have POC code lying around I should probably publish somewhere.

Like pointed in sibling comments, it is pretty trivial to clone a mac address so if you were to dump a "unique" psk, all you need is the mac address that goes with it.

What it does gain you though and that is a big plus in some situations, is the ability to revoke a single psk without having to reconfigure all your client devices. That is very useful.

The onboarding is a little bit wacky though. You need an easy way to get the client mac address, generate a unique psk for it, save that in your config, then attempt connection....

One way I would like to explore is have a "next available psk" easily available, for example in an app available to the network administrator. When hostapd asks for the psk associated with unknown/never seen before mac, return that default PSK and save it as associated with that mac on succesful connection, then regenerate a new default PSK for the next device.

This way, an admin can share the password or onboard new devices easily. You don't need to know the mac address of the client in advance.

If you need to revoke access for a device, just revoke the psk that was associated with it.

How exactly is your mobile device going to ACK those received packets? The mobile device needs to transmit as loudly as the AP for its ack to be received.

Boosting the transmit power higher than your receiving device can transmit leads to very bad wifi links, where the mobile device is receiving a good signal but it's own messages are not received back.