publiush

7 ms·

1.
by publiush 5y ago
This is cool! This is an extension version of the federalist [1] project I was working on earlier! This makes using federalist so much easier! Way to go! Also, this is really cool that you did this! [1] https://news.ycombinato
2.
by publiush 5y ago
I think that there is a bit of a disconnect in those that work on systemd. I agree that a revert makes sense in this case. Most people who will suffer real catastrophic breakage are also NOT usually using rolling-release or bleeding edge
3.
Pure Node.js Torrent Library and CLI(github.com)
2 points by publiush 5y ago|0 comments
4.
Windows 11 Saves Bitlocker Key in cleartext if you don't signin to MS Online(twitter.com)
1 points by publiush 5y ago|0 comments
5.
DNSCurve(en.wikipedia.org)
3 points by publiush 5y ago|0 comments
6.
by publiush 5y ago
As per the earlier drama with some of the Handshake admins and developers trying to bully developers out, I have linked up with some of the other developers who have experienced the same thing from them. We have setup a new discord server
7.
Handshake Discord Server Without Toxicity(discord.com)
1 points by publiush 5y ago|4 comments
8.
by publiush 5y ago
I actually made a system called federalist [1] that uses mutable torrents. Hope you like it! [1] https://github.com/publiusfederalist/federalist
9.
by publiush 5y ago
I e-mailed him about it days ago. By the way, are you familiar with Zooko's triangle?
10.
by publiush 5y ago
It's been an on-going conversation that's been going on a few days.
11.
by publiush 5y ago
If we're talking about the same person, he was the only one who actually encouraged what I was doing and even gave me the idea for Zooko. However, the admins on their discord, were less than encouraging. EDIT: As per the same person&#x
12.
by publiush 5y ago
I've decided to begin my own community. Those toxic admins can't control the blockchain.
13.
by publiush 5y ago
I also just pushed zooko message [1]. This allows you to encrypt and decrypt messages using only your handshake name. [1] https://github.com/publiusfederalist/zooko-msg
14.
by publiush 5y ago
This is definitely a little bit of a different medium to twitter and likely the '1 post per block' limitation is great in this case. Think before you Zooko, as it's permanent and forever.
15.
by publiush 5y ago
[Submission Statement]: Right now, there are a lot of sentiments as it relates to de-platforming on various platforms. I was able to implement a completely decentralized twitter-like microblogging system on top of a blockchain, so this inh
16.
by publiush 5y ago
Right now it's in POC form, so it's just using a simple 'zooko:' prepend to identify Zooko messages (Zookos). Since it's completely decentralized on chain, it actually doesn't need ActivityPub or XMPP for help
17.
Show HN: Like Twitter, but Immutable, Verifiable and Decentralized(github.com)
14 points by publiush 5y ago|10 comments
18.
by publiush 5y ago
Again, this is a security issue and doesn't in any way reduce the proven efficacy of cryptography. It's pedantic at best, and I am going to stop replying to your comments. Happy new year.
19.
by publiush 5y ago
I agree that the intentions were pure. That said, this isn't a product, but instead, a project with a specific goal of improving internet security by showcasing concepts to the HN community. The discussion within the thread, I think,
20.
by publiush 5y ago
> Are you implying people should feel free to create and obtain a new name on the blockchain using any random website? Also I do not see the list of popular GH names in the link you provided. The popular names are in the names folder. I
21.
by publiush 5y ago
The instructions you pasted are for claiming a name that was pre-reserved when Handshake launched [1]. This is different from creating and obtaining a new name on the blockchain. [1] https://github.com/handshake-org/hs-
22.
by publiush 5y ago
This is solved with key management and security as opposed to with the fact on whether or not the technology has merit. Now, we're really moving goalposts. ;)
23.
by publiush 5y ago
It's more of using specialized, purpose driven applications vs using a generalized swiss army knife of epic proportions. Handshake was purpose built to work with traditional DNS while ENS is something entirely different. I think that&
24.
by publiush 5y ago
This isn't a marketing message/post. This is a Hacker project to explore improved ways of doing things with the new primitives of our collective technology base. In this case, owning your own identity with a decentralized identit
25.
by publiush 5y ago
I apologize for that. There was an assumption that most people were aware of the Handshake Naming system [1]. Handshake is a naming blockchain that's recently been gaining adoption quickly (Namecheap [2]) (Opera Browser [3]). Using
26.
by publiush 5y ago
> Between "there's no guarantee that the message viewed by a user was actually written by the poster" and "You absolutely cannot fake a message being cryptographically signed without providing a broken verification fu
27.
by publiush 5y ago
> If you think about it, this is also true for web3 — true enough that it's broken. You absolutely cannot fake a message being cryptographically signed without providing a broken verification function. > We don't live in a w
28.
by publiush 5y ago
> This part can be addressed easily with avatars such as those Gravatar makes. Using a blockchain instead seems like a huge overkill, and also brings 'login' back into the equation because most websites will use something like
29.
by publiush 5y ago
I think where we're headed is a blend of Web 2 and Web 3 (Web 666). In this, Web 2 continues to live on in its current form, because it works quite well. However, there are some issues with Web 2 that Web 2 can't easily solve th
30.
by publiush 5y ago
You hit the nail pretty much on the head. While you're correct that a 4chan-like mechanism would provide a means of authentication, the hash would not be human-recognizable easily (basically, not meaningful). Using a naming block cha

More ›