rasengan

45 ms·

541.
.UK registry team tries to go commercial causing an overhaul in management(theregister.com)
2 points by rasengan 6y ago|0 comments
542.
by rasengan 6y ago
I think the attraction is simply the portability and battery life tablets provide. You can also use Shells [1] and simply run those desktop OS on your tablet. I think this is the sweet spot that lets you truly go all tablet. [1] https:&#x2
543.
Running an Always-On Desktop with Shells(distrowatch.com)
3 points by rasengan 6y ago|0 comments
544.
by rasengan 6y ago
ASCII art is what it was called. Edit: As aptly mentioned ANSI art is the right word. This was the colorful BBS days as opposed to FXP courier days they were covering.
545.
by rasengan 6y ago
This is what they do in the Republic of Korea.
546.
by rasengan 6y ago
Dear Roy, It is unfortunate you are dealing with this. I am so sorry and hope for the best. The Handshake founders had an airdrop pre allocated for you in the Handshake Blockchain [1] so there is about $64,000.00 in there that you can claim
547.
by rasengan 6y ago
You could also recycle your old laptop by running a cloud OS app like Shells [1]. You just need an old laptop that can run a modern browser. [1] https://shells.com
548.
Everything you need to know about DaaS(techradar.com)
1 points by rasengan 6y ago|0 comments
549.
by rasengan 6y ago
Moral: If anything can be used against you, the adversary who will use it against you can get it and use it against you.
550.
Secured by DANE. Zero ICANN DNS. Zero Certificate Authority(twitter.com)
2 points by rasengan 6y ago|0 comments
551.
by rasengan 6y ago
Shells.com cloud computer on an iPad Pro.
552.
by rasengan 6y ago
This highlights one reason why you would want to have your own TLD on Handshake [1] instead of a leased subdomain. This way you aren’t subject to the uptime of another. [1] https://handshake.org
553.
by rasengan 6y ago
If you use the Firefox and Chrome extension [1] you do not need to trust that the encryption code is broken. [1] https://private.sh/extension.html
554.
by rasengan 6y ago
That's a good suggestion. Thank you!
555.
by rasengan 6y ago
Yes. A comparison would be single-key versus multi-key authentication.
556.
by rasengan 6y ago
It's not a trustless solution, but one that requires multiple parties to collude to break trust as opposed to in most search engines cases, just one. In other words, if "Search Engine Company" wants to deanonymize and link yo
557.
by rasengan 6y ago
That's true. This is the same as Tor in the sense that if multiple parties collude, you can be de-anonymized.
558.
by rasengan 6y ago
End to end encrypted means this here: [Client] ---> [Private.sh] ---> [Gigablast] In the above diagram, [Private.sh] cannot see the search query. Thus, it's end to end encrypted. Private.sh is the "signal server" in t
559.
by rasengan 6y ago
In this case, the only way to be sure of this is to use the private.sh extension[1] which has the public key hardcoded in and is being served by google and mozilla. [1] https://private.sh/extension.html
560.
by rasengan 6y ago
Our solution here is our extensions [1][2] which are hosted and served by google and mozilla (third parties). [1] https://chrome.google.com/webstore/detail/privatesh-private-... [2] https://addons.mozil
561.
by rasengan 6y ago
This is absolutely end to end encrypted. A proxy can only strip the IP. The NaCl client side encryption deployed on private.sh is what makes this end to end. The client encrypts the search query with the public key of gigablast. The prox
562.
by rasengan 6y ago
DDG is a great search engine. I trust they do not log and maintain privacy. One entity needs to be trusted. That being said, with the private.sh offering, it requires two entities to collude to identify users. Thus, it does provide more g
563.
by rasengan 6y ago
Great question. If you review the javascript, NaCl is used to encrypted the search query before giving it to private.sh. Thus, private.sh is unable to decrypt your search. The search provider uses NaCl to decrypt the search query and then
564.
by rasengan 6y ago
> Then again, it can't be worse than the status quo, so still good that you're working on this one way or another! Thank you. To clarify, private.sh != search provider (gigablast). Thus, it would take collusion between both t
565.
by rasengan 6y ago
You can use the private.sh extension [1][2] to ensure that private.sh isn't doing anything fishy. The public key of Gigablast is hardcoded in and the assets are served by a third party. [1] https://chrome.google.com/we
566.
by rasengan 6y ago
The search (where decryption takes place) is controlled by GigaBlast.com.
567.
by rasengan 6y ago
The javascript source should show you that it's being encrypted -- and the proxy is under our control, the search engine is not.
568.
by rasengan 6y ago
You may be on to something here. In the past, most search engines started from DMOZ (now defunct) which was a simple, curated, directory.
569.
by rasengan 6y ago
You're absolutely right. This is a much better explanation, and we'll improve our language with this advice in mind. Thank you so much for your help and input!
570.
by rasengan 6y ago
It's an initiative by Imperial Family Companies [1] which uses GigaBlast as the provider. [1] https://imperialfamily.com/

More ›