skysight-inc/HackerNews huggingface dataset:
Signal also has a long history of shitting on their competitors with extremely questionable arguments, if not quite to the same extent as Telegram. The issues at stake here are far more important. Encrypted messengers had better hang together or they will surely hang separately.
Tangent, but I've seen a U2 at the Air Force Museum in Dayton. It's amazing how small that thing is, given its capabilities.
Hey man, it is an amazing idea. I have been thinking to build something similar.

I am building reading clubs for my custom library - on top of crypto tech, and in the process, I have experimented with several book reader tech. pdf.js, muPDF and some other tools, which one did you settle on?

My lib: https://datapond.earth
There is a very nice episode of Last Week Tonight by John Oliver diving into it, accessible on YouTube[0].

[0]: https://youtu.be/Q8oCilY4szc?si=q4iv_SlqoHlXuJod
Skimming through this guide: https://dolthub.com/blog/2021-11-15-zsh-completions-with-sub... it seems to be a lot more convoluted than I thought. Really, every external CLI binary that supports completions has this autocomplete script?

I thought zsh parsed man pages to get available options/subcommands.
Presumably it would take multiple raw photos and then you’d have to do the post-processing to put them together in your editing software.
Forget RCA, we should think bigger! Putting LLMs in charge of nuclear weapons could completely eliminate the root causes of accidents worldwide!
I have no specific data, and Europe has slightly better bail rights than most of the USA, but I would think for this list of charges and his flight risk a judge would have qualms or problems denying bail.
Currently I'm working on file compression program in Rust. Nothing too fancy, it just use common algorithms (LZ77, LZ78, etc.)

The only difference here is that the program will switch on the fly between different algorithms depending on which one that can compress file smaller.

It can compress 1 GB file (enwik9) down to around 230 MB. Pretty good I guess for something that I worked in my spare time.

I'm not publishing it yet, since I'm still experimenting with it a lot.
> The main differences between Commercial Crew and previous US manned space programs are that a) two different vehicles were built, not one, and b) NASA does not own or operate the vehicles; their builders do. Everything else is the same: NASA provided specifications for what it wanted in a manned spacecraft capable of reliably carrying people to ISS, various companies bid based on the specifications—their designs varying greatly from one another—and NASA chose the winning bids.

I think there is a big difference you haven't mentioned.

With Apollo, with the Space Shuttle, with the US components of the ISS, with SLS/Orion – NASA owned the design and made the big design decisions. They hired contractors to do a lot of the grunt work of the engineering – analysing different options, fleshing out high-level designs into detailed designs, etc – but the big picture design decisions were made by NASA. (Or, in the case of SLS, dictated to NASA by Congress.)

By contrast, with Commercial Cargo/Crew and HLS, NASA is just writing the requirements spec and letting the contractors make the big design decisions. And then the contractors have to convince NASA's engineers that the design actually fulfils those requirements. But NASA isn't making decisions like "what fuel should the launch vehicle use"–so long as they can convince NASA that what they are doing meets the requirements spec, the contractor can do almost anything they like. Whereas, on earlier programs, NASA was making the final call on many of those high-level design decisions.
I'm in a similar boat but from different reason. Stared working on HomeHero (https://homehero.pro). It's mainly focused on taking care of home and it's inventory so... maybe it will be useful?
Blog post from same company in two years:

"How we switched from a custom database to Postgres".
A good series of examples is in the book "Barbarians at the Gate", chronicling the career of F Ross Johnson. His company would get acquired and then he and his folks would outmanoeuvre the acquiring company management.
I've been having a lot of fun building a digital garden for my WIP notes into my personal website: https://mxstbr.com/notes/digital-garden

My quests (goals) with this digital garden are:

1. Publish more than I did when I just had space for essays, which hopefully leads to…

2. Getting more input from people on my ideas

3. And have fun futzing with my digital garden technically

So far, so good!
It’s from NASA dude
I've been working on a Lisp interpreter in Zig. This my first attempt at a garbage collector.

https://wmedrano.github.io/fizz
There’s a similar build for Windows 11
my webframework: https://github.com/spirobel/mininext

(my goal with mininext is to provide index.php like productivity but with all of npm and typescript at your fingertips)

currently busy using it to build things. will document everything in detail soon.

https://x.com/spirobel/status/1827231794934247674
We have been working on AI agents for sales and marketing. Our focus is in deep customer research instead of at scale marketing or spray and pray motion of outbound emails.

Our purpose is modeled to give sales and marketing skills to non-sales people. Just like how Canva gave design powers to non-design people.

We believe everyone has to have the skill to sell and market themselves or their product. Yet the only trend that does not change is understanding your customer/prospect.

AI agents help with this.

Check us out: godmodehq.com
I'm working on updating the https://yavaca.com site including the backend written in golang. It is for users to publish out-of-office (OOO) plans so they can unplug while on vacation. Great for maintaining a healthy work-life balance. Having fun with the golang part.
How can I configure my phone to use it? I thought SMSes come straight from a carrier and there is not much you can do outside of your messenger app.
Playing with cursor, trying to get used to using it better.
This is a good point, I tried to research `SameSite=Lax` but most of the docs don't actually mention how it applies to form posts. But the actual RFC does specify that it only applies to top-level "safe" methods. So form POSTs are actually protected by default.

https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-coo...

This does actually make it pretty robust, although it does become an issue if you actually want to support cross-site form posts. But that is a pretty niche use case.

> includes the much simpler `SameSite=Lax` cookie under "Defense in Depth" later on.

The reason that I put the cookie-ignoring solution first is that it is robust and flexible. If you do want to support some cross-domain interaction with a logged in user you need something other than `SameSite=Lax`. The "ignore auth unless explicitly handled" provides a simple and effective baseline while being much more flexible. I also don't think ignoring cookies across you app is any more "mildly convoluted" that ensure that all cookies have a specific set of attributes. Both basically require a common layer to implement, but it seems more likely that someone adds a cookie somewhere without the approved helper than that they somehow accept a request that bypasses the middleware.

> `SameSite=Lax` is the default on all major browsers

It isn't. For some reason Firefox has had it prefed off since forever: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Se...

But it is well supported if you set it explicitly.

> loosening the default CORS protections ... but definitely makes your server less secure for basically no reason.

Can you elaborate? The "loosening" described is equivalent to what can be accomplished via a CORS proxy (other than possible network perspective concerns if they apply to your use case). So it isn't really loosening it. How does this make your server less secure?

This is explained here: https://kevincox.ca/2024/08/24/cors/#shouldnt-i-be-more-spec...

> One way to help fix that is by introducing PUT, PATCH, and DELETE to HTML forms—methods which don't have the same CORS exceptions

This would be nice, but it seems to mostly be a workaround, you can choose a different verb just to get CORS protection but now you can't use POST even if it is appropriate.
Why should I think that LLMs would be good at the task of analyzing a cloud incident and determining root cause?

LLMs are good at predicting the next word in written language. They are generative; they make new text given a prompt. LLMs do not have base sets of facts about how complex systems work, and do not attempt to reason over a corpus of evidence and facts. as a result, I would expect that an LLM might concoct an interesting story about why such a failure occurred, and it might even be a convincing story if it happened to weave bits of context, accurately into the storyline. It might even, purely randomly, generate a story that actually correctly diagnosed the root cause of the failure, but that would be coincidental based on the similarity of the prompt to text of similar postmortem discussions that were part of its training set.

If you had an extremely detailed postmortem document, then I would expect LLM‘s to do a very good job of summarizing such document.

But I don’t see why an LLM is an appropriate tool for analyzing failures in complex systems; just as I don’t see a hammer being a very effective tool for tightening bolts.

Right now, I am concerned that the relative ease that modern frameworks provide to author LLM based applications, is leading many people to optimistically include LLM technology in attempts to solve problems that it doesn’t seem particularly well suited to solve.
You won't believe for what are responsible paper money printed by central banks.

As for those South Korea-related stories, the blame is partially on the government. For example, an operator of a website selling illegal videos got only 18 months in that country [1].

[1] https://www.chinadailyhk.com/hk/article/135865
Or use a tool that already does the rendering, with zoom and pan: https://visualdb.com
Yes. Not doing things that are hard because they’re being greedy, and don’t want to cap the amount people can be charged.

The problem is technically solvable, it’s good for customers.

All you need to do is prioritise actually doing it.

In what stupid world do we pretend this is somehow good for consumers? Racking up thousands of dollars in bills?

It’s just the status quo.

They’re not not fixing it because it’s hard; that’s just the convenient excuse; they’re not fixing it because they don’t want to.
I'm not understanding the why behind that claim
I've been working on 2 projects:

Insnare: https://www.insnare.net/

A head-hunting/recruitment application to search companies and people based on their skills and experience. Currently focused on Australian market.

It's also for people who are looking for jobs. The goal there is to help to find good companies which have high (or low) concentrations of people with certain skills/attributes.

Saasufy: https://saasufy.com/

A no-code/low-code platform for building apps without code. Insnare is built with and runs on Saasufy. This freed me up from having to write back end code for Insnare and made the front end code very small.
Cybersecurity being a sideshow to the main event is a brilliant way to frame the problem.

It also explains why companies rarely get punished by the markets for data breaches.
Last I checked, Durov had some of his biggest companies confiscated by the Russian government, and he basically fled Russia, so it's hard to believe he would be cooperating with them. (But not impossible I guess, they might have scared him into cooperating ??)

Also, doesn't the Ukrainian military also use Telegram quite a lot ? (And what about the Israelo-Japanese Viber, also very popular in Ukraine?)
I have 2 Google cardboards on my shelf.
I am working on an open book Library and a "new" D-Licence.

It is an experiment for the exploration of the free aspect of blockchain storage, where the book library is now permanently hosted on the blockchain, and it's content voted upon by its members.

The licence is based on creative commons, and enforces that the data is decentralized and doesn't need any account, or wallet, to use.

There is also the creation of a new label, the D-Safe label, for a safe experience across generations.

A fun side project - which I have been working on for several years now - rewriting it fully already 10 times - and been restructuring my mental health around it.
> If Apple hypothetically agreed to iMessage backdoors, why would you trust the Telegram app updates served up by Apple's app store?

I wouldn't. I don't trust Apple hardware or software, and I don't see why anyone who cares about these issues ever would. But fortunately Telegram runs on devices and OSes from a wide range of suppliers, many of which might be less open to the influences that apply to Apple.
It isn't.

Async is for tasks dominated by waiting, e.g. http serving, not computations. This means it's extremely rare to run into mmap blocking related issues if you don't do something strange.

Furthermore async doesn't exclude multi threading:

- having multi threaded worker threads in addition to CPU threads is pretty normal

- having multiple async threads potentially with cross core work stealing is also the nrom

I.e. if you just follow basic advice the huge majority of task interacting in any potential performance problematic way will not be run in async task even if you write an async web server.

> but you'll never fully match reality and you end up wasting resources when an executor blocks when you weren't expecting

and you wast tons of resources always even without doing something unusual with non async IO _iff_ it's about waiting dominated tasks as you have way more management overhead

furthermore in more realistic cases it's quite common that some unplanned blocking is mainly casing latency issues (which in worst case could case timeouts) but due async engines still using multi threading it not leading relevant utilization issues. That is if it's just some unplanned blocking. If you do obviously wrong things like processing large files in async tasks things can be different.

An argument against async is that depending what you use it can add complexity and that a lot of use-cases don't benefit form it's benefits enough to make it a reasonable choice. Through that is also a bit language dependent. E.g. JS is already anyway coperative in your program and using async makes things simpler here (as the alternative are callbacks). Or in pythons with GIL the perf. gain of async are much higher compared to the gains in idk. C++.
Perl, at build time, get errno numbers of the system in a similar way[0]: preprocess errno.h with `$CC -E` and recursively scan all files in # markers for macro defines.

The configure script even checks the existence of several system headers this way, so if your C compiler don't support # markers in -E output, you get missing includes everywhere.

[0] https://github.com/Perl/perl5/blob/blead/ext/Errno/Errno_pm....
It's all just speculation here. Maybe the French gov knows some stuff we don't.

I always found that guy's story of living 'in exile' from Russia a bit suspect. And now Russian government officials are calling for his release.

Need more information to make any kind of judgement. What I'm pretty sure of now is that this probably has nothing to do with encryption.
Related https://en.m.wikipedia.org/wiki/Kinetic_bombardment
> SameSite=Lax is now the default on browsers

Note on all major browsers unfortunately: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Se...

A real shame, because it would be a pretty robust solution for sites that don't require any cross-origin interactions at all. That being said it is well supported if set explicitly. So if you can ensure that all cookies that your app sets have the attribute you should be good to go.
IMO AAA gotcha mobile =/= AAA single player. I'd argue AAA gotcha service probably harder to produce but easier to finance due to profitability. Wukong signally there's potential market to justify PRC studios / investors spending 40-50M on big single player productions. I don't think subsequent efforts are going to bring in nearly as much due to Wukong being first/novelty, but it's progress towards establishing market other than live service. Of course knowing PRC media scape, we're just going to get increasingly large budget wuxia rehashes.
https://guestcast.xyz

A way to follow creators and not specific podcasts
I wonder if this is related to Russia having access to telegram
Sorry, you are completely correct. I'll update the article.
wow this is super cool stuff. I see the similarities between currencies and trading cards.

seems like you guys also have grading services
> Replace Boeing with Facebook/Google, and it still sounds strange to feel bad for the workers at those companies when the executives make bad decisions like chasing profits over all. I mean, why?

Because there are people working at Boeing, people like you or me, who poured their heart into the project and the institution sapped their energy away and made their efforts ultimately worse than futile.

There was someone working at Boeing who spent years of their life qualifying those thrusters. They tried their very best. Perhaps they even batted for more testing. Or more analysis. Or perhaps they didn't because they didn't know better, but they still spent their best effort to do a good job.

And when they heard that the engines are acting up they probably felt like a trap door has opened under them. They felt that sinking feeling in the pit of their stomach. Either angry that they haven't caught this in testing, or angry that they haven't approved their request to test more.

Years and years ago they proudly told their mom/girlfriend/drinking buddies that they are working on a beautiful spaceship. And they were very proud of the project. And now all those people have heard that their spaceship is a liability. All that good feeling turned ash in their mouth.

There are people at Boeing who worked very very hard the last few weeks (months?) trying to uncover what is wrong with those thrusters. There are others who spent endless hours in meetings with NASA discussing risks and explaining tests and arguing persuasively that the space ship is fine enough to ride. And it is not really their individual fault that the spaceship is not fine.

And even worse, there are people who spent years of their life designing and building flawless systems. And they did a great job and built their subsystem really really well. Well made, high quality products. Yet nobody will think of their stuff positively because some other subsystem failed.

It is kind of like you are working on a beautiful great pyramid. (FYI pyramids were not built by slaves.) And you work hard, and quarry stone all day, and shape it, and push it and pull it and you really really do your best job. You are really a champ. And you should deserve to celebrate in the sun with your team mates the beautiful pyramid. But unfortunately you are not one of the lucky ones working on Khufu's pyramid, you are on the team which works the second pyramid built for Sneferu. And something is wrong with the plans. Or the foundations, or the site selection. Or the rocks are not strong enough. Nobody really knows but even though you are doing a great job individually the damn thing is collapsing in front of your eyes. And it will be known forever as the "bent pyramid". And it sucks. And you feel bad. And that is sad and we should feel bad for those people.
An app for easing house management - HomeHero (https://HomeHero.pro). Primarily inventory oriented towards easier finds, location hierarchy and related tasks.
Currently only web, android and Linux as there's been little interest from Apple and Windows side
It seems like they all have DIFFERENT autocomplete scripts, some of which subshell out to the tool being completed to generate further completions.
> Because the small details actually matter in the experience.

Since when has a large company actually cared about those details?

The last time Microsoft cared was the late 00s. By 2010, Microsoft's UI decisions were squarely in the "doesn't make any sense" camp. Today, they've almost finished removing the last of those sensible late-90s UI decisions (which were, I will note, thoroughly researched), in favour of… vibes? A/B testing? I'm not really sure.

The last time Google cared was around the same time: late 00s, early 2010s. Then they killed Google Specialized Search, flattened their logo, flattened Android 5's UI (the beginning of the end for non-power-users being able to find their way around), and proceeded to flatten everything in sight. Skeuomorphism is a dirty word.

I've seen the same trends from Twitter, Facebook… actually, every big tech property except facebook.com, which has somehow managed to keep its 00s-chic multiple-window interface and colour scheme. If not for the News Feed, it might actually be one of the more usable social media sites!
Have you tried https://www.dreamlist.com
mad people don't need reasons to be mad; but rather excuses. If not flat earthism then something else like aliens or smth.
> CouchDB / PocketDB aren’t really up to date anymore.

Source? I’ve been using CouchDB as my game world DB for years, works fine for me?
How do they get it across the well-guarded border by the way?
Agreed, so far, SpaceX seems to be fine with building more Dragons, I had been assuming they were just refitting the 3 they built initially for the free-flying missions, but turns out they have 5 in service at the moment. Boeing seems to have decided to stop at 2 Starliners, and of course too early to say about fleet size for Dreamchaser.
How’s this different from explainshell?
https://bauble.studio/ is a lisp-based procedural 3D art playground that I hacked together a while ago. It's fun to play with, but it's a very limiting tool: you can do a lot to compose signed distance functions, but there's no way to control the rendering or do anything "custom" that the tool doesn't explicitly allow.

So lately I've been working on a "v2" that exposes a full superset of GLSL, so you can write arbitrary shaders -- even foregoing SDFs altogether -- in a high-level lisp language. The core "default" raymarcher is still there, but you can choose to ignore it and implement, say, volumetric rendering, while still using the provided SDF combinators if you want.

The new implementation is much more general and flexible, and it now supports things like 2D extrusions, mesh export for 3D printing, user-defined procedural noise functions... anything you can do in Shadertoy, you can now do in Bauble. One upcoming feature that I'm very excited about is custom uniforms and embedding in other webpages -- so you can write a blog post with interactive 3D visualizations, for example.

(Also as a fun coincidence: my first cast bronze Bauble arrived today! https://x.com/ianthehenry/status/1827461714524434883)
> This is a toy project, not intended for production use.

Well, darn.
There is a large spectrum between total anarchy and totalitarian regime, so in the same way there is a spectrum in free speech.
I use it all the time, every day. Better than "Sheets".

what do you find unusable about it or what do you think is better?
torrentfreak.com is legendary
Yeah, I had a section on this but decided to cut it because I felt the other protections mostly obsoleted the need to talk about this.

> pretty much everything requires a non-simple request in order to invoke an action

Except for POST request such as in forms. They may be a little out of fashion with JS-based frontends and JSON APIs but I would consider it a pretty gaping hole. If the list could be reduced to just HEAD and GET requests I would consider it a pretty complete protection. But POST seems like too big of a hole. (Although if you can block all requests that are POST with a "simple" Content-Type then you unlock a pretty robust protection.)