Google are obeying the letter of the law, while openly violating its spirit. Perhaps it'll be possible to attack them in court, but it will take years, and by that time they'll have found another trick.
213 karma · joined May 23, 2020
Google are obeying the letter of the law, while openly violating its spirit. Perhaps it'll be possible to attack them in court, but it will take years, and by that time they'll have found another trick.
Extremely common at major universities and research centres. CTSS, ITS, TENEX, Multics, Unix and even VM/370 were all alternate operating at some point.
> Other than OS2, alternate OSs for other systems were rather rare,
You weren't there, were you? A lot of people replaced MS-DOS with DR-DOS before Microsoft deliberately broke it with Windows. A little later, a number of people were running Unix System V on their PCs, to the extent that there was a regular column about Unix in Byte.
100BASE-TX uses just two pairs (lanes), one for sending and one for receiving. 1000BASE-T uses all four pairs, for both sending and receiving. Therefore, a 100BASE-TX interface that's only receiving needs to power up one pair. A 1000BASE-T interface needs to power all four pairs all the time.
I recall reading about some extensions that allow switching off some of the pairs some of the time ("Green Ethernet"), but I think that they require support on both sides of the link, and I'm not sure if they are widely deployed.
> This is a mailing list.
The way I understand it, the layering is different. In X.400, multicasting was a feature of the protocol. An SMTP mailing list, on the other hand, is an endpoint that terminates a protocol transaction, and then initiates one transaction for each final recipient.
I guess it boils down to where it is preferable to have the extra complexity: the ITU-T protocols invariably prefer to put it inside the network, while the Internet protocols prefer to put it at the endpoints. The SMTP protocol is simple, and therefore the mailing list software needs to be complex.
I don't think that's IETF policy. Individual IETF working groups decide whether to request publication of an RFC, and the availability of open source implementations is a strong argument in favour of publication, but not a hard requirement.
If the IETF standards are sometimes useful, it's more a matter of culture than of policy.
If you read French:
* https://www.plus.transformation.gouv.fr/experiences/4531155_...
* https://linuxfr.org/users/jch-2/journaux/l-identite-numeriqu...
There's also the support for concurrency and parallelism, which has started to improve recently, but is still years behind what is available in Go (but still better in my opinion than what is available in Rust).
The grammar is changing in many ways (for example, the inanimate masculine is being replaced with the animated, kroić kotleta), but this was about honorifics.
> I'm interested in learning more about this!
It's very simple, actually.
For strangers, you use the third person and the title « Pan » or « Pani » (Sir or Lady). You avoid pronouns, « The Lady has forgotten the Lady's purse on the table ».
For friends, you use the t-form ("ty", thou), and use a diminutive rather than the full name. « Johny, you've forgotten your bag on the table ».
For work colleagues, you traditionally use « Pan » or « Pani » with the full form of the first name. « Mister John, the mister's bag is on the table ». This is perceived as old-fashioned, and is increasingly being replaced by the t-form.
The v-form has fallen into disuse, as it was promoted by the Communist regime.
(The old-fashioned honorifics still exist, but they are only used in administrative correspondence: the only time when you're "the respectable gentleman" is when you need to pay taxes.)
I know. I always feel utterly embarrassed when Russian-speaking friends write down a movie title for me, and I have to ask them to rewrite it in block capitals.
https://upload.wikimedia.org/wikipedia/commons/3/34/%D0%9B%D...
Understandable.
I don't think gjs is a webview. It uses JavaScript, granted, but binds to a native toolkit, not to DOM and CSS.
Latency is better, since Galene uses an unordered buffer instead of a jitter buffer. Lipsynch should also be slightly better, as Galene carefully computes audio/video offsets and forwards the result to the receiver so it can compensate.
Audio and video quality, on the other hand, should be roughly the same, unless Jitsi is doing something wrong.
Not quite. Using UPnP, any host on your internal network can open a port for any other host. You may be thinking of NAT-PMP.
Additionally, by default UPnP mappings don't expire (unlike NAT-PMP mappings), so if a host crashes with an open port and your ESP32 inherits its IPv4 address, it will be exposed to the Internet.
Your ISP has paid 40€ for your IPv4 address. That's a cost they're most probably passing on to you.
> Every host routable from anywhere on the Internet? No thanks.
Every time you start a videoconference, there is a couple of seconds' pause while the peers perform NAT traversal.
What would be more useful, however, would be the ability to selectively block network connections: for example, to allow the public transportation app to access its API endpoint, but not the advertising and tracking endpoints. I don't think LineageOS allows that, and I don't know if Graphene does.
But it's not very useful in practice: if an application doesn't need networking for its core functionality, then there usually is an open-source equivalent that does not use the network in the first place. The few applications that lack a good open-source equivalent (public transportation, proprietary messaging protocols, banking) don't do anything useful without network access.
The videos contain at least one mistake that indicates that they were written by a native speaker of Russian (the use of the word prawilny, which is a Russian word (правильный) and doesn't exist in Polish).
It's circumstantial evidence, granted, but enough to point at a Russian origin, at least in the absence of further information.
One of the videos uses the non-existent word prawilny, which is Russian (правильный). The Polish equivalent would be prawidłowy or właściwy.
Are you sure that his carrier allows activating an eSIM while roaming? Mine definitely doesn't, which means that if I break my phone while abroad, I lose access to online banking.
struct foo {
...
atomic_int v;
...
};
struct foo x;
memset(&x, 0, sizeof(x));Reported by Patrick Breyer, <https://www.patrick-breyer.de/en/citizen-protest-halts-chat-...>
However, most other EU programmes do allow and even claim to encourage free software companies to apply.
They make decent home servers, unless you need fast storage.
They have different priorities, granted.
> They greatly reduce the privacy and security of the Android Open Source Project
That's going to depend on your threat model. Many people don't feel that having an unlocked bootloader is a significant threat.
> GrapheneOS is a non-Google Linux distribution. [...] If you have an issue with using lots Google code [...]
https://x.com/GrapheneOS/status/1964561043906048183
Even you seem to agree that we're relying too much on Google's goodwill.