Vinnl

There is no leverage so I fail to see how this could succeed.

Isn't there upside to the US too if more Europeans visit the US?

It's not clear to me if this would allow access to all biometric data, or "just" to that of people crossing the US border?

And for the latter, what data are we talking about? If it's mostly fingerprints, don't those already get collected upon crossing the border? And can't they already be read from a passport's chip?

Mastodon.social is too big, but it is on a different scale: https://arewedecentralizedyet.online

(Though I do agree it's partially irrelevant, depending on what problem you're trying to solve.)

Doesn't Briar itself provide functionality to share the apk via Bluetooth? So you don't even need F-Droid (though it's still good to have regardless, of course).

I think something like "figuring out a way to stack the odds in your favour in a gameshow" would fit that bill, and that seems fairly innocuous to me.

Though full disclosure: I did that, so that might colour my view. https://vincenttunru.com/hacking-a-gameshow/

Sure, but I'm interested in a steelmanned explanation before judging.

It was the second reading, but was it also treated as such? (Because if so, it sounds like this would have been a rejection?) If not, what is the steelmanned reason for doing so?

I did get the first one straight away, so it's not too unclear, but it did induce a short moment of panic, which I'm not sure I'd categorise as fun :P

This is fun! Could use a short "how it works" blurb on the landing page though :)

Thanks. Do you know then why of the majority that voted against today, enough people voted in favour of the urgency procedure?

To understand whether/to what extent this is brazen, I'd be interested to learn the reasoning why urgency procedures are possible, and in particular, why the apparent majority against shouldn't have been enough, and what is needed to classify something as urgent.

I don't think it's just French. The million-billion distinction is different from English in many European languages - [1] lists basically every language other than English in the EU. And in my example, "actual" to mean "current" and "eventual" to mean "possibly" are at least also present in Dutch and sometimes used in that way in the EU.

[1] https://en.wikipedia.org/wiki/Long_and_short_scales#Current_...

Thanks! Although these, possibly with the exception of #2, sound like things that Zed handles, rather than the harness?

I was the same, but did end up switching due to features. I'm not sure I remember which sealed the deal, but I remember at least being able to remove/change the left-most button that just points to an About screen IIRC, and updating maps without going through the app store? And just the fact that improvements to Organic Maps also seem to make it to CoMaps, whereas I don't think they flow in the other direction.

No, but: https://github.com/streetcomplete/StreetComplete/issues/5421

Ah, I'd heard that latter one, but I thought that was just a mistake in the sense of "could of". TIL!

I think it's a bit quick to want that variant to be actual already, but eventual we might be able to make it work.

Not even the accents - different voices are annoying enough. When I was young I watched some cartoons in English, and hearing them in Dutch later, despite being my native language, was still uncomfortable.

Wait, "couldn't care less" is British?

I declared my blog to be `en-GB` as well, but I'm fairly sure it's neither that, nor any other pre-catalogued locale. There's just no way I'm able to know where any of the references I use came from, let alone which weird contortions I came up with by myself. There are probably a few in this short comment alone.

Ah OK, so the ACP connector ensures tool calls work with Zed, and communicates the available tools and their results to the harness, and then the harness mainly provides a system prompt and the API calls?

So if you use Claude via Copilot in Zed... You use Zed's harness, I think? What does Copilot do, at that point?

I volunteered for a project [1] with roughly this philosophy. Traditional publishing currently serves three purposes:

- Organise peer feedback - Publish the work - Recognise good work, helping with both discovery and credit

That latter part especially is what allows publishers to charge the ridiculous markup that they do.

But with "modern" technology, feedback and publishing really doesn't require all that infrastructure - email and arXiv can easily be used to self-organise that. So we built a system of recognition that does not block publication, and can be used as a layer on top of arXiv and any other venue, allowing peers to vouch ("endorse") for a work.

I had even proposed and implemented an integration for arXiv Labs that got accepted, but then never merged. I should follow up on that...

[1] https://plaudit.pub/

Awesome, thanks!

I never understood why we're OK with placing billboards, which by definition try their best to get you to look at them, next to the road, which we're supposed to look at.

Sadly that one seems to have been removed.

Your wish came true: https://news.ycombinator.com/item?id=48671717

I think you might be forgetting how much it sucked before React.

Right, but I think a typical Bluesky user never sees data from there in their feeds?

Don't get me wrong, I think it's pretty cool that you can run all these different apps and have them store their data on their own PDSes. And theoretically it's possible for everyone in my Bluesky feed to be on their own PDS and use different apps. But the question from a Mastodon point of view is: is that the case in practice, and if not, how likely is it that there will ever be a significant portion of non-Bluesky posts in an average microblog feed, on atproto?

I felt the same: when folks ask this question they might not be using the correct terminology, but what they actually want to know is how many different PDSes (that's what you mean by "atproto hostings", right?) there are in a typical feed.