HN user

bb010g

167 karma

I do stuff.

[ my public key: https://keybase.io/bb010g; my proof: https://keybase.io/bb010g/sigs/WbxfbZ5JVkmh_mzOB7KYQL9sRZZiwcNzQSJUnFxC98g ]

Posts4
Comments86
View on HN
Lobsters 3 years ago

When the Lobsters algorithm said his account was too new to post a link, I thought I was vouching for and reviewing his project link by posting it myself.

I'm pretty sure this would be considered a normal vouching & introduction of a member to the site, if those members did not then repeatedly follow up your introduction with repeated self-promotion (including bonus violation of the spirit of the unseen domain policy). As someone inviting others to Lobsters, you were trusted with a small duty to introduce them to the site properly. For most of those you invited, you were both the person initially posting the invitee's relevant unseen domain and the inviter for that invitee. It's respectful there to warn new users of site policy that you don't expect them to know.

When I invited a friend to Lobsters a few months ago so they could post their cool new project there, I made sure to educate them about the self-promotion policy so that both they could continue to use the site and so that I didn't become a problem for the site.

Lobsters 3 years ago

As a Lobsters user, I think you could have avoided those spam flags with a less click-baity title and opening line of the body. “MIT CSG Memo 137 was the first CS publication to use the term "object-oriented"” would have been a better title, since you posted after the result was discovered.

Also, Hillel Wayne already politely explained this to you! https://lobste.rs/s/ebztmj/now_we_know_which_cs_publication_...

`Apache-2.0` allows Element the same power right now. No organization is maintaining meaningful community forks of Synapse and/or Dendrite with their own proprietary modifications on top. Element hasn't used their power to take the vast majority of their modifications private so far.

If Element decides to go proprietary, which they could already decide to do, then the community is now left to fork an `AGPL-3.0` project instead of an `Apache-2.0` project. Oh no, we'll be protected from this happening again in the future, wailing and gnashing of teeth.

Blink 1.0 3 years ago

It's an unprivileged VM, so unless you're the type to do binary analysis before running things this is just as safe as any other binary.

What are your thoughts on KERI? Some of Phillip's slide decks are weird to go through, but I really like its security & usability goals (key rotation needs to be realistic!) and the fact that it's going through the IETF RFC process. (Also, it avoids cryptocurrency-related blockchain baggage. It's disappointing how much blockchains have infested decentralized identity efforts.)

<https://github.com/WebOfTrust/keri>

Blocking Kiwifarms 4 years ago

I see that policy works extremely well in cases like <https://twitter.com/keffals/status/1566153033586810885>. As long as you give all the information necessary for someone interested to interact in a harmful way, it's fine, but you have to frame it in a way that doesn't suggest harassment. Just speculate about all the locations they could possibly be having lunch, and trust that nobody will harass them.

Does the OpenID Connect work also include IndieAuth work? It seems like a natural fit for Matrix, given the shared focus on decentralization.