Groxx

Absolutely, the ones that are clearly trying more than make up for the rest imo, and some are stunning. There are a lot of them. And many of the rest are just having a bad brain day and need help rubber-ducking to see the thing right in front of them - we've all been there, many times.

One of my favorites is spending nearly 10 minutes trying to get someone to read a single word on their screen correctly, in a dialog box that was blocking them, containing fewer than 10 words, so I could find the cause of their problem. After nearly 30 minutes to figure out that they had a popup blocking them, and not "the computer doesn't work".

What eventually worked was getting them to spell it to me backwards. That strategy has worked out quite well in other cases too - I suspect because it avoids some of people's built-in autocorrect and dyslexia (autoincorrect).

(I honestly mostly enjoy tech support, and I've done it for many years, sometimes professionally. But some people do seem like lost causes, and are not just having a bad day)

Even easier: click the download link on the website. https://sqlite.org/download.html

You can add CVE info later in a git note, if you want something git-managed to point to it. Might take some habit-tweaking to include notes in log output though, to see them later.

Flawed root detection issues are kinda common to see when running Graphene, tbh I suspect this is just an accident - it very much is not the first time, nor the first for PayPal.

This is my setup as well, though with JIT enabled (which is the default). Crashing at launch on:

    version 10.10.0

    com.paypal.android.p2pmobile
    versionCode 1160090162

Seems pretty likely a flawed root detection being rolled out (given the stack trace), my phone is not rooted.

Honestly there's a decent chance they don't even know, in most cases, because corporate environments generally try hard to have as few as possible hardware/software setups to maintain. And they're unlikely to proactively test on Graphene unless it's closely related to what they do (and it definitely is not for most apps).

Mistakes happen and ya can't fix what you don't know about. Always report issues.

Also strongly consider just using the website.

An accurate description, I think. Plus they have trouble leading from one paragraph into the next, or maintaining any kind of coherent direction further.

In summary, I think it's an expensive time to buy computer hardware, and I might recommend holding off on any purchases.

I watched that video not too long ago, very much enjoyed it. +1 to the recommendation!

Well... yeah? That's describing the event horizon. It's a term roughly as widely used as "singularity".

Talking about the inside of a black hole is indeed rather pop-misunderstood though, yes. But it's not like physicists are especially confident about the details either. Theoretical astrophysics changes a lot as time goes on and our instruments improve, and it's a rather hard field to do experiments on to get better data quicker.

It kinda started turning as people realized that a huge amount of the biggest people pushing tech are rabidly anti-human, incredibly racist and usually spouting nazi quotes every chance they get, and are out to exploit as many people as possible just because they can.

The negativity is rather well-earned at this point. I do still enjoy tech, but the ecosystem is no longer as infused (by ratio) with nerds doing cool things.

Generally the correct default, I think. And sometimes the correct non-option too.

I personally prefer to have them in many social media things (it's a hint for "this is popular enough that they won't even notice my contribution" vs "likely ~nobody else has seen this, maybe I should spread it"), and I think I manage to avoid the addictive parts pretty well... but it does still affect behavior (e.g. above, do I boost it or no?) and sometimes that's a net negative for the ecosystem.

(unintended but fittingly: ^ above is just barely under their 500 char limit. though this addition is not. I generally don't like small char limits, but to each their own)

Oooh, now I see the extractor-view setting in the UI. Yeah, that's essentially perfect \o/

Thank you again!

I assume it content-extracts that on upload? I'd really like to move storage into hister too, if possible. That way you could also switch from an extracted view to a "full" view in the UI. Though I assume that'd be fairly simple to build later.

Overall I really like what I'm seeing, it ticks a lot of important boxes for me and it's pleasantly straightforward. Hopefully I'll find time to contribute!

>Hister builds a personal search index from pages you visit, bookmarks, browser history, local files, and crawled websites.

Immediately interested and will check it out, thank you! I've wanted a "search stuff you've seen online" tool for a long time, but everything seems to be research-oriented or "archive but don't search" or some weird combination that means it's nigh useless to me. I've got decades of bookmarks and archives and I've kinda been stuck grepping them at best (it's rare but I do sometimes want a page I saw once three years ago and I love having that option), while hoping someone would build something better.

One question if ya don't mind, while I explore: any chance of singlefile support? Content-extraction is useful in lots of situations (e.g. wallabag) and it's a great default, but sometimes it fails and sometimes you really do want the page, relatively close to how it actually was. Singlefile does that much better than most, and it does so well enough (and manually-handle-able enough if needed) that I don't feel any desire to switch to WARCs or similar.

Though specifically I'm probably looking for something like "content-extract everything" + "key combo to save singlefile version too" + "upload singlefile archives to backfill / recover". Like 99% of the time content extraction is preferred, and I'm glad to see it... it's just not always enough, and having to go elsewhere for exceptions breaks a lot of the utility.

Anthropic's Generated Income

Yeah, cross language is generally considered "a protocol", and exists only to cross process boundaries. That's definitely useful! It's even a mostly reasonable one (though with a few weird decisions either due to blindly copying Prometheus' flaws or due to... idk avoiding copying Prometheus on principle? Very strange sometimes, but livable). We needed a grand unification here, even if mediocre, and the time was right.

Trying to make all the supported languages feel similar (beyond sharing concepts which almost directly match the protocol) is foolish in the extreme, and it's why it's such a monstrosity. And worse, they seem to treat that as more important than the bottom-most clients that speak the protocol, so you might be waiting years for any support for a third of the system!

Yeah, they spent a ton of effort trying to cram automatic-config-and-library-discovery-like features everywhere when they would've been MUCH better served by requiring explicit dependency injection... and then just adding DI wrappers externally. That's what contrib is for.

As it stands, due to the tower of abstractions that could've just been "init with an implementation of this interface", you need to learn several pieces and how they work together (hint: convoluted and horrifically inefficiently) to modify any piece, and inevitably you learn that to get what you want, you need to swap out a major portion of it... but doing that while maintaining the auto-registry nonsense is a gigantic effort. If it's even possible.

It is the new poster-child for "design by committee". It's horrific. Unfortunately it's also usually the best option in large setups. I greatly approve of the high level goal, but omfg

Which is why you don't install them widely enough to enable broad surveillance, yes. Temporary additions to problem-areas can be fine though. Scale is part of the "should this be allowed" equation, we allow extremely intrusive things when they're tightly scoped (and court approved).

Roughly none of these fall under normal security researcher behaviors.

Have them take pictures of every car, now you've got half of what flock offers.

It's the widespread remote camera installs that are the main problem there. If they kept data locally and had to be collected by hand, it might be fine - that's difficult enough to grow to monitor everyone all the time. Aside from using film though, I'm not sure how that would be achieved.

(To be clear, I really do think we should be prosecuting speeding (and tailgating) MUCH more than we do. Far more death and damage occurs from it than we should allow. But ubiquitous networked cameras are not the way we should do that.)

Yeah - this is the important part. With a truly benevolent government I think this may in fact be the best option...

But not only do you have to trust the government now (and you likely should not), you also need to trust the government far into the future (which you absolutely cannot do) because the tools will still exist.

Don't accept tools that are also strong weapons for oppression.

It's especially hard when multiple subjects try to do it, because it can add enormous amounts of home-time expectations. And many families can't dedicate that much time.

I do like it though, and I like that college generally leaned that way more (and was better balanced, as it had substantially less time in classrooms, so you could study during the day).

Is there anything on how a multi-node cluster works (I'm kinda assuming there's something since it makes "single" mentions a few times)? Application-level sharding is always an option (and multiple things I've worked on have used it to great effect), but anything automatic seems likely gnarly and fun to learn about, if it recovers some of the naive perf loss of "just hold the lock while doing rpc to other nodes".

Doesn't really cover the types used in the beta APIs. Nor would I expect it to though.

Is there a more technical explanation post somewhere? I'm definitely curious how it works, and I like the core idea quite a bit - I'm fairly convinced that WASM uses like this are going to grow immensely, and "it's just a global mutex/single thread" reduces complexity so much that it's always interesting to see where it's possible to use.

The latency+throughout brings many questions though, like "are you holding responding to writes and any reads that occur after until changes are written to disk" and "if so I kinda assume that change log is constantly streamed to disk with a moving high water mark for responses". I can generally see how that'd hit such benchmarks, especially with non-dirty reads being near instant, but details are always interesting.

Broadly enjoyed my read, though I do have a nitpick here:

>The absence of side effects or stalls cannot be enforced by the type system ...

Side effects is probably correct, but stalls would imply wasm code that calls out to a long-time blocking function - that's generally quite easy to type-system-ify, and wasm stuff often does so with promise-like constructs. So there would be a need for spacetimedb-side markers for "this func might do HTTP", but that kind of marker for WASM-contact-able code is very much a normal expectation.

If they don't have that kind of marker, and do allow blocking calls in their beta API, then yeah - huge problem with that kind of internal structure (shared global lock), completely agreed.

Github runs CI per PR push (obviously), and per main-branch commit (click on commit history in any project with CI, see a build result check mark on each one - that's true if you push a dozen commits too (I've done that)), in nearly all setups I've seen. I'm not sure how much of that is required vs default though.

With enough effort, you can rather obviously run CI per PR commit (it's a programmable system), but I've never seen aUI-integrated way to track the results, aside from browsing custom job names, which is very far from what I'd call "integrated" when compared to PR-level build markers. Similarly, I'm not aware of (but would not be surprised by) any way to disable per-main-branch commit builds, aside from initial pushes.

But I haven't poked around deeply in the settings, and business-account settings are rather different anyway so those might be wildly different / more flexible / more obtuse in exciting ways. Github is a very large and complicated product at this point, darn near anything could exist if you dive through enough UI layers or use old URLs to find soft-deprecated features.

Also, honestly, 100 commits = 1 transaction? That's far more of an over-simplification than anything I've said. It's a massive product with thousands of engineers, there's no chance at all it's just one database.

Probably? If you do 100 pushes instead, there is roughly zero additional data. At best you'd be comparing cache costs, which probably are lper for one large push, but there's a ton of calculation and CI that runs per commit regardless of other data being cached.

Wow, yeah - years later and I still get nothing in Firefox, and support is quite spotty in general (and clearly still buggy): https://caniuse.com/?search=datalist

Hard pass, that's essentially unusable.

Less "internal prompt" and more "they are trained to summarize after a </think> token"