Our data includes anonymized API calls to traditional search indexes like Google, Yandex, Mojeek and Brave, specialized search engines like Marginalia, and sources of vertical information like Wolfram Alpha, Apple, Wikipedia, Open Meteo, Yelp, TripAdvisor and other APIs
I don’t want to be that guy, but technically they said they are using traditional indexes like Google, not that they are in fact using Google. But I guess that is splitting hairs.
Also, maybe they just dropped Google from their indexes? And what’s more: Why does it matter if they are using Google at all, when the results are satisfying?
Knowing which indexes they are using exactly would be nice to know, though.
I don’t see how this is relevant to this at all.
Why the limitation?
Consider this the exception to the rule. There’s no reason we should assume this timeline is the norm.
$5/mo
Hell no
Punkt
Never heard of it
I came from rif is fun and so I’m using Jerboa now. I don’t need a fancy UI, I need minimalism.
Probably, but I’m already heavily invested mentally into the Ubuntu/Debian ecosystem, .deb packages and PPAs and know how to navigate launchpad, etc. I’m not really looking for something new, just something that doesn’t force snaps down my throat.
What are you talking about? Install the app, enter your server address and log in.
Which of the default settings don’t work for you for this to be terrifying?
Never heard of it before. Thanks for mentioning it.
https://github.com/jellyfin/jellyfin-android
Not so hard to find, is it?
I’m using MJ PDF. [Play Store] | [GitLab]
The time when they essentially went closed source to implement MobileCoin in kind of a covert operation really didn’t do them any favors, though.
GNOME itself might work, but the GNOME suite of software can not compete with the one from KDE. After suffering for months I switched from Ubuntu to Kubuntu and never looked back. (I’m consindering a switch to KDE on Debian due to Canonicals shenanigans though.)
There are audio clients for Jellyfin, so you can absolutely host your music library with it. Personally I don’t have any experience with that, so I won’t be making recommendations.
Simply because I haven’t seen it mentioned yet: 7-zip
But realistically VLC and Firefox
AFAICT they’re both multi-protocol (or even protocol-agnostic) onion routers. Tor on the other hand can only transport TCP.
And while Lokinet has a stronger focus on exit nodes, I doubt there’s no way to host exit nodes on Veilid either.
So from what I can tell they look to be very very similiar. Maybe they differentiate on which cryptographic primitives they use, but otherwise the same concept (except for the node hosting incentive approach).
Maybe I’m entirely mistaken though. It’s hard to find technical data about Veilid.
Edit: From their pre-release docs: https://gitlab.com/veilid/veilid/-/blob/main/docs/guide/guide.md?ref_type=heads#user-privacy
User Privacy
In order to ensure that users can participate in Veilid with some amount of privacy, we need to address the fact that being connected to Veilid entails communicating with other peers, and therefore sharing IP addresses. A user’s peer will therefore be frequently issuing RPCs in a way that directly associates the user’s identifying information with their peer’s ID. Veilid provides privacy by allowing the use of an RPC forwarding mechanism that uses cryptography to similar to onion routing in order to hide the path that a message takes between its actual originating peer and its actual destination peer, by hopping between additional intermediate peers.
The specific approach that Veilid takes to privacy is two sided: privacy of the sender of a message, and privacy of the receiver of a message. Either or both sides can want privacy or opt out of privacy. To achieve sender privacy, Veilid use something called a Safety Route: a sequence of any number of peers, chosen by the sender, who will forward messages. The sequence of addresses is put into a nesting doll of encryption, so that each hop can see the previous and next hops, while no hop can see the whole route. This is similar to a Tor route, except only the addresses are encrypted for each hop. The route can be chosen at random for each message being sent.
Receiver privacy is similar, in that we have a nesting doll of encrypted peer addresses, except because it’s for incoming messages, the various addresses have to be shared ahead of time. We call such things Private Routes, and they are published to the key-value store as part of a user’s public data. For full privacy on both ends, a Private Route will be used as the final destination of a Safety Route, and the total route is the composition of the two, so that neither the sender nor receiver knows the IP address of the other.
Oh wow, from the sounds of it they basically made Lokinet and the Session messenger running on it obsolete.
Thoughts?
First time I’m hearing about this. Why would they drop the licensing fee?