dathinab

66 ms·

871.
by dathinab 2y ago
> To our modern sensibilities, this is a wildly invasive policy. is it? not really cutting the "value" of money in half always had been a important emergency tool countries had and sometimes used and "moving" half of
872.
by dathinab 2y ago
number of active registered users you have a login with bluesky, you register with a email thats more or less what matters here at the moment
873.
by dathinab 2y ago
> 1. It puts Bluesky on notice that they need to watch their numbers can't be as they haven't reached out to Bluesky, can't put someone on notice without communicating with them this articles seems to be based on newpapers
874.
by dathinab 2y ago
> Sounds like they aren't but the EU wants to be on their back anyway. > The regulator hasn’t reached out to Bluesky directly, yet, The Financial Times writes. I think no on is on anyones back, they just follow standard procedure
875.
by dathinab 2y ago
fun fact there is a semi standard encoding called wtf-8 which is utf-8 extended in a way so that it can represent non well formed utf-16 (bad surrogate code points) it's used in situations like when a utf-8 based system has to interact
876.
by dathinab 2y ago
> No fixes for this issue in 2 years [..] I'm not sure how framework is supposed to fix a SSD firmware issue if the vendor doesn't fix that. Also out of interest which SSD was it?
877.
by dathinab 2y ago
11gen (i.e. first generation) Framework did had that issues, but that was mostly a issue of the 11gen Intel CPU being used. It's not really much of an issue anymore with newer CPUs. Through you won't beat M2+ Macs when it comes to
878.
by dathinab 2y ago
> docked operation (TB4 dock) maybe Linux but could also be specific to the Dock, many docks are not tested against standards but just Windows and/or Macs and sometimes just one of them, too. > I have a long history with ThinkPad
879.
by dathinab 2y ago
I'm happy with it (13" specific feedback, latest AMD gen, but I had the 11th gen Intel before). But if I can recommend it is a bit of a mostly yes but not soley yes thing. Some of the good parts: - can be repaired (I have a tenden
880.
by dathinab 2y ago
> zero evidence you mean except the original poster often implying exactly that in their articles or the personal experience of the commenter that nearly always whenever they ran into borrow checker problems it was due to exactly that re
881.
by dathinab 2y ago
I habe been writing rust at work since 2016 or so and I can't say that the virtue checker ever had been much of a problem. Like it's not that it never caused issues but most times fixing them also produces much better code. In my
882.
by dathinab 2y ago
> Meta cuts the price of its ad-free plan by 40 percent in a bid to sate EU regulators (the second article bundled with the first article, at least for me) I'm sooooo feed up with platforms and news sites/papers knowingly stark
883.
by dathinab 2y ago
yes that is the point you can rely on implicit drop to always make sure you never forget to unlock (as long as you don't leak the guard which is hard to do but possible) but you can also explicitly drop it to have full control over whe
884.
by dathinab 2y ago
no not at all If you port C code to rust and now need much more locks in Rust it's nearly always an indicator for either your C code not having been correct (e.g. accessing resources behind a lock without acquiring it) and/or you
885.
by dathinab 2y ago
> This is not true in C, where you can reference the shared memory after the lock is released. technically yes but practically this is nearly always programmer bug to bypass a lock
886.
by dathinab 2y ago
I haven't been supper up to date with changes to rust-lang recently (I had seen that they are stabilizing if_let_rescope but didn't look into what it is, to much to do at work). Through making if-let less syntax sugar for changing
887.
by dathinab 2y ago
To elaborate a bit more this is a consequence of a overlapping of two design decisions: 1) temporaries being added "alongside" the item they appear in. This makes a tone of thing much much simpler, but comes back to bites us here.
888.
by dathinab 2y ago
and nothing prevents you from explicitly dropping lock guards in rust either actually it's a common pattern in complicated multi threaded code or similar to require that
889.
by dathinab 2y ago
maybe but that is unrelated to the distilled problem shown in the blog and RWLocks are not the only way this can bite you but it's also behavior for rust match-like statements in general so nothing new nor specific to if let
890.
by dathinab 2y ago
The issue here isn't new features at all. `if let` is more or less syntax sugar for `match`. And match behaves like that, too and has been in rust since 1.0. That match did behaves like that is due to some old, you could say legacy, re
891.
by dathinab 2y ago
How common is it to use MTLS in the user-to-service use case (e.g. browsers with mTLS configured)? I mean for (potentially external) service-to-service authentication it's way easier then for user(browser,app)-to-service.
892.
by dathinab 2y ago
> We had this. It worked well, in my opinion at least, and the number of complaints and straight up threats because kids would learn things "they shouldn't be" was just… insanely frustrating. are you US based? so of the No
893.
by dathinab 2y ago
2.1 is mainly updating 2.0 with various later RFCs and usage recommendations, many of them are not drafts. And some document used e.g. https://datatracker.ietf.org/doc/html/draft-ietf-oauth-secur... are technicall
894.
by dathinab 2y ago
Preferable the intersection of OIDC, OAuth 2.1 and Best Current Practices. As in use OAuth2.1 recommendations including OAuth Best Current Practices to structure you clients inside of the OIDC framework which mostly will "just work&quo
895.
by dathinab 2y ago
> Also there must be at least someone very knowledgable of Keycloak to give guidance to the rest of the team this is why I said large team, you need people with knowledge, but on small teams you likely can neither hire them (if the team
896.
by dathinab 2y ago
it's about the issues I mentioned in the other response, not about them using rust in some science project it's quite easy to accidentally commit trade mark infringement if there is a restrictive policy about it and you "just
897.
by dathinab 2y ago
> This is a trademark policy exactly but if you distribute something containing a trademark and the trade mark policies don't allow distribution it is pretty much automatically a gray area of trade mark infringement i.e. you do a cl
898.
by dathinab 2y ago
Also interesting is that OAuth2 is a bit too flexible in how you can put things together and OIDC provides a lot of good practice about that how. So even systems where OIDC compliance is a non goal often are partially OIDC compliant, I mean
899.
by dathinab 2y ago
There are plans to add namespaces AFIK, they are just quite early stage. Through for a long time (part of rust developers) haven't been very happy with the idea. a stuff like `abcde/bar` vs. `abcbe/bar` are a total pain. But
900.
by dathinab 2y ago
> The way I read it the intent is to ensure there is one sanctioned version of Rus basically that Through it's very annoying that it needs refinement _again_ and _again_ every f* time they update the trademark policy. Like why - is

More ›