ricdeh

joined 2 years ago
[–] ricdeh@lemmy.world 1 points 1 week ago

wdym "killed the whole company"? Nokia was always more than just phones. They are still around and one of the largest telecom equipment manufacturers.

[–] ricdeh@lemmy.world 9 points 1 week ago (1 children)

Sorry for the downvote, but I see this take repeated here on Lemmy so often and it just makes no sense. This will not kill the FOSS app "ecosystem". Nothing whatsoever changes for FOSS ROMs like LineageOS or GrapheneOS. And as long as there are FOSS operating systems, apps will be developed for them. If anything, this could drive mainstream adoption of free/libre Android forward, re-invigorating the scene through public outcry.

And to the people who propose fully jumping ship from Android to "Linux phones" because of Google's recent changes, you would only make the app support matter worse. As someone who daily drives both a phone with LineageOS and one with postmarketOS (mainline-ish Linux), mobile app support is endlessly worse on Linux than the fallout from Google's developer registration could ever be. That is not to say that Linux phones will not eventually get to a point of reasonable maturity, but it is way too early and frankly utterly irrational to bury AOSP Android or needlessly hate on it.

[–] ricdeh@lemmy.world 4 points 2 weeks ago

I have been daily driving LineageOS since 2023 on a Samsung Galaxy S10+, and before that experimented a little with CyanogenMod. Number 1 reason is privacy and security. I don't want Google spyware or any other proprietary software on my phone (though I have to live with proprietary drivers, but at least they are abstracted away behind HAL).

[–] ricdeh@lemmy.world 52 points 2 weeks ago

"Street racers" are some of the worst people to exist. They have no empathy and regard for the lives and well-being of other people. Most of the time, their fatal accidents kill entirely unrelated people (including children!) that were just going about their business. Having "street racing" as your "hobby" is the ultimate display of unlimited egoism; you do not care at all about the actual humans you kill through your actions and the decades of connections you sever and memories you eradicate. And defending this abhorrent practice is almost as shameful as participating in it.

[–] ricdeh@lemmy.world 12 points 2 weeks ago (1 children)

Not true. The "words" with which specific species call some others has been determined and can be observed, so "we would never know" is false.

[–] ricdeh@lemmy.world 3 points 1 month ago (1 children)

Those probably are the intern's doing

[–] ricdeh@lemmy.world 25 points 1 month ago

BMW CEO can get bent

[–] ricdeh@lemmy.world 4 points 1 month ago

Whatever you choose.

[–] ricdeh@lemmy.world 15 points 2 months ago (8 children)

This is not just one of those ivory tower papers with their actual applications far away in time and eventually ending up in some obscure industrial process never heard of again in lay circles; this could have an immediate impact on the maker culture and makerspaces right now and in the near future. The preprint describes the process in a very understandable, digestible manner and provides actual implementation examples, as well as detailed recipes for all of the compounds. If you are even remotely interested in the subject matter, I'd recommend you to try it out for yourself. The "ingredients" are all easily obtainable and handleable. Yes, gallium and indium might be a bit expensive, but it is worth it imo. They literally used consumer kitchen equipment for some of the steps, to demonstrate how this is feasible for tinkerers, makerspaces and prototypes. No expensive machinery required (except for an FFF 3d-printer, of course).

[–] ricdeh@lemmy.world 17 points 2 months ago (10 children)

Oh this is wonderful! I strongly recommend reading the preprint, really enjoyable: URL

[–] ricdeh@lemmy.world 9 points 2 months ago (1 children)

How is EndeavourOS true neutral? It is arch-based and has a "pacman-based rolling release model".

[–] ricdeh@lemmy.world -4 points 2 months ago (2 children)

The trouble is that barriers to voting will always be manipulated by the people in charge to exclude specific people.

That's just a statement and not necessarily true just because you say so.

Anyway, such a test would obviously not be about Nascar or illegal immigrants, but rather the structure of the government and the content of the constitution, testing whether the testee understands their nation, its values, and the democratic principles it is founded on. I don't buy the pseudo killer argument that the test would eventually and automatically be corrupted. Keep it on the subject matter, and as long as the constitution doesn't change, the test doesn't change meaningfully. Everything outside these topics is irrelevant to the test.

 

So I understand that the subnet mask provides information about the length of the routing prefix (NID). It can be applied to a given IP address to extract the most significant bits allocated for the routing prefix and "zero out" the host identifier.

But why do we need the bitwise AND for that, specifically? I understand the idea, but would it not be easier to only parse the IP address ~~string~~ sequence of bits only for the first n bits and then disregard the remainder (the host identifier)? Because the information necessary for that is already available from the subnet mask WITHOUT the bitwise AND, e.g., with 255.255.255.0 or 1111 1111.1111 1111.1111 1111.0000 0000, you count the amount of 1s, which in this case is 24 and corresponds to that appendix in the CIDR notation. At this point, you already know that you only need to consider those first 24 bits from the IP address, making the subsequent bitwise AND redundant.

In the case of 192.168.2.150/24, for example, with subnet mask 255.255.255.0, you would get 192.168.2.0 (1100 0000.1010 1000.0000 0010.0000 0000) as the routing prefix or network identifier when represented as the first address of the network, however, the last eight bits are redundant, making the NID effectively only 192.168.2.

Now let's imagine an example where we create two subnets for the 192.168.2.0 network by taking one bit from the host identifier and appending it to the routing prefix. The corresponding subnet mask for these two subnets is 255.255.255.128, as we now have 25 bits making up the NID and 7 bits constituting the HID. So host A from subnet 192.168.2.5/25 (HID 5, final octet 0000 0101) now wants to send a request to 192.168.2.133/25 (HID 5, final octet 1000 0101). In order to identify the network to route to, the router needs the NID for the destination, and it gets that by either discarding the 7 least significant bits or by zeroing them out with a bitwise AND operation. Now, my point is, for identifying the network of which the destination host is part of (in this case, the host is B), the bitwise AND is redundant, is it not?

So why doesn't the router just store the NID with only the bits that are strictly required? Is it because the routing table entries are always of a fixed size of 32 bits for IPv4? Or is it because the bitwise AND operation is more efficiently computable?

 

"While developers start work on building Vision Pro apps, the potential for people upgrading to the iPhone 15 this year is a big reason for investor optimism."

view more: next ›