1,695 karma · joined November 5, 2021
That makes it sound like national parks were invented in the USA and there are no national parks in Europe ... So when a new store opens outside of the US it's called European Wallmart?
Why don't you normalize latin alphabets filenames for indexing even further -- allow searching for "Führer" with queries like "Fuehrer" and "Fuhrer"?
http://www.pisrs.si/Pis.web/pregledPredpisa?id=ZAKO8611 -- 225. člen (piškotki)
LUKS2 does not care about the size of the disk. If it's JSON header is present, it will by default treat the entire underlying block device as the LUKS encrypted volume/partition (sans the header), unless specified otherwise on the commandline.
Another FOSS web tool is Nightscout -- it generates reports and live graphs from data gathered from your CGM via for example Juggluco. My instance is at http://sladkor.4a.si. My sensor expired, so there's no more live data.
glucometerutils is an interesting repo for downloading stored data from hardware readers etc. Abott encrypted the Libre 2 USB communication to force users to use their proprietary software, but hackers managed to extract keys.
http://juggluco.nl http://nightscout.github.io https://github.com/glucometers-tech/glucometerutils http://ni.4a.si./anonymous/freestyle-keys/tree/freestyle_key...
I'd rather download the models from 3rd party unofficial sources/torrents, since that'd be legal where I live for personal research usage. Does someone know of some server that hosts the Code Llama model weights or some torrent? I have downloaded the torrent with Llama weights, but I'd rather use the Code variant, if possible.
This usually does not help in case of DNS. Let's say a resolver queries a root that does not reply. The resolver will time out after n seconds and then try another root server, but will not send any replies to the querying client. Therefore, the querying client has no way to know if it's the resolver that is broken or the upstream authoritative server and the querying client itself will timeout after m seconds and switch to another resolver, ignoring any possible later response from the first initialized query.
If m is larger or equal to n, the problem is aparent -- client will never know if the root is broken or the resolver, usually treating the resolver as such.
But doing that would mean to either trust the current resolver you are using, which is unacceptable, as it's sometimes cloudflare or google, or running your own resolver on every device -- which also does not work. It is absolutely crucial for the DNS system we have today that there's a small number of resolvers that have large caches, otherwise root servers would blow up. Unless we massively start implementing some novel RFCs.
It's level of centralisation is comparable to that of email (and email is very well federated in my opinion).
MUCs like the XEP you mentioned are handled by a different XEP.
Camera and microphone are not a mandatory feature of Matrix either (;
I like that Matrix puts an emphasis on message history, but on XMPP that seems like an afterthought. For example on XMPP multi user chats, messages history retention relies on the server that hosts the chatroom and this is sometimes very limited, sometimes even disabled. And if that's the case, you only get messages when you have a _client_ online, as your server won't store messages when you don't have a client connected. Or something like that.
And AFAIK, multiple clients with a MUC room opened will appear as multiple users sometimes. I'm not sure how it all works really, so take my words with a grain of salt.
XMPP seems more like a pubsub system for system messages, like MQTT (:
I trust my homeserver, since I host it myself. I do not need end to end encryption. I understand this is an issue of the client, not the protocol. But there aren't many clients. Prebuilt element for android from fDroid will connect to matrix.org, vector.im and other network hosts and I don't want that at all, although this tracking can't easily be disabled. It feels very centralised.
I run my own homeserver and want to chat with my friend that runs his own server. It is unacceptable to me that clients connect to anything other than those two homeservers (apart from CRL and OCSP, which should also be disabled by default, as I consider those protocols great spyware). Not to mention the fact that homeserver software itself is known to make connections to the servers of the developers by default, without ever talking to someone on matrix.org. This is also unacceptable. My homeserver should only connect to other homeservers.
3PID is a failed attempt, as it centralises identities and works by utilising a single point that gathers a lot of personat information at one place. I don't want it.
XMPP does not have those issues. Set up prosody and use dino or Conversations and they won't make any connections to non-essential servers. Furthermore, the end to end encryption is way easier to use in XMPP (OMEMO), and it's easy to turn it off if you don't need it.
You specify what you're interested in and then the parser calls your callback whenever it reads the part of a large JSON stream that has your key.
https://libwebsockets.org/lws-api-doc-main/html/md_READMEs_R...