![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
IIRC they demonstrated an interaction with Siri where it asks the user for consent before enriching the data through chatgpt. So yeah, that seems to mean your data is sent out (if you consent).
**beep ** bop.
IIRC they demonstrated an interaction with Siri where it asks the user for consent before enriching the data through chatgpt. So yeah, that seems to mean your data is sent out (if you consent).
SLACC doesn’t support sending stuff like DNS servers.
If you drop the projector, then airpods already do it better when paired with the watch. There’s no point in such a device at all, then.
It was my first introduction to the type-length-value concept over the network, seemed radically different from the text only IRC protocol that I knew back then. I remember how fun it was to write an elegant parser for the ICQ messaging, and how I ended up on somewhat a DOM model where I converted the on-wire format into series of nested objects. Not the most efficient idea, but it was neat.
It’s much more than just “http requests”, honestly. A Matrix server and e.g. nginx have very little in common.
That’s what their docs say:
At an absolute minimum, Dendrite will expect 1GB RAM. For a comfortable day-to-day deployment which can participate in federated rooms for a number of local users, be prepared to assign 2-4 CPU cores and 8GB RAM — more if your user count increases.
That’s not accounting for Postgres.
I got that. What I mean is that you can easily have a tiny 256mb VPS for a bunch of static websites or even some WordPress and the official matrix servers would require you to easily double or triple the bill.
I looked into matrix servers the other day for an unrelated reason and tbh the amount of resources they ask for is way more than you need for a webpage (dendrite asks for 1gb ram minimum for a number of users, and that’s without accounting for postgres)
2M per BitMagnet instance. That’s about 18Gb in postgres. Not significant, but around where you start to think about query optimization.
BitMagnet isn’t a silver bullet. Its datastore use makes it rather unreliable past about 2M torrents mark.
Honestly, it’s hardly newsworthy given how sudo was a thing in windows for quite a while now. I use it pretty often, especially sudo pwsh
for elevated shells.
However, XAMPP didn’t just die because it opened itself up to Microsoft and got extinguished
So, we went from the somewhat imaginary “google killed xmpp” to fully fictional “Microsoft killed xampp” now? it’s almost like the fedipact people literally have no clue what they are talking about.
I took a look at the current traffic and you’re absolutely correct, lemmy (as of 0.19) has a proper schema with everything covered!
But lemmy doesn’t use “plain json”, it annotates some fields with the schema, just not all of them, which makes it a mess. You either do json-ld proper, or you don’t do it at all.
no Federation with instances that use altered versions or proprietary versions of AP.
It’s especially funny given (the last time I checked) neither kbin nor lemmy actually followed the spec properly. They ignore the jsonld requirements and resort to field names, that, by the spec, should be dropped.
Edit: lemmy is actually good now!
I can easily imagine the future where “good” instances will then stop federating with the ones that don’t have threads blocked, all thanks to these lists.
isn’t threads already several times larger than the whole of the “fediverse”?
In iOS 13 or later and iPadOS 13.1 or later, devices may use an Elliptic Curve Integrated Encryption Scheme (ECIES) encryption instead of RSA encryption
(from apple docs).
If you’re curious about it all, I’d suggest studying some notes from the protocol researchers instead of taking to the pitchforks immediately. Here’s one good post on the topic.
FWIW that java app isn’t much memory hungry and it’s not cpu-intensive at all. There are no issues with running java apps at all if you spend 5 minutes figuring the basix flags on how to set the memory limits or run it in a memory-limited cgroup via some containers runtime.