Live data from Hacker News

Viewing profile — rogerbraun

rogerbraun

HN member
Joined
Wed, Apr 27, 2011, 2:59 PM UTC
HN karma
692
Public activity
125 items

About rogerbraun

Marketing Engineer at Applause

Recent public activity

  1. comment
    Comment #18459721

    The install docs are on the wiki: https://git.pleroma.social/pleroma/pleroma/wikis/Installing%...

  2. comment
    Comment #17408829

    Some background information on ActivityPub in Pleroma: https://blog.soykaf.com/post/activity-pub-in-pleroma/ https://blog.soykaf.com/post/what-is-pleroma/

  3. story
  4. comment
    Comment #16225216

    no, we really don't. Not every tool needs to be equipped for private discussions. ActivityPub and OStatus are used for Twitter-style communication. Those aren't high security commu…

  5. comment
    Comment #16224889

    it's really not worth it. If people want to exchange encrypted messages, they should use a proper tool for that.

  6. comment
    Comment #16224589

    In AP, messages are signed with http signatures ( https://tools.ietf.org/html/draft-cavage-http-signatures-09 ). OStatus has a similar mechanism called salmons, which are signed XM…

  7. comment
    Comment #16224167

    there's #social on freenode, although it's not very active. You might have more luck asking your questions on #pleroma on freenode (another Ostatus/AP server) or on the mastodon di…

  8. comment
    Comment #16224098

    messages are signed using http signatures ( https://tools.ietf.org/html/draft-cavage-http-signatures-09 )

  9. comment
    Comment #16223717

    In OStatus 'salmons' are messages sent from one server to another that contain posts. They are signed, so the receiving server knows if it can trust it. If person peter@example.com…

  10. comment
    Comment #16223667

    this doesn't make much sense. The very easy way to add AP-level privacy to ostatus was to just use a different salmon endpoint for private messages. This way, messages would never …

  11. comment
  12. comment
    Comment #16223567

    Yes, and this was known to the main developer. There were easy ways to make it at least private if the other server was trusted, but they chose to not implement them.

  13. comment
    Comment #16223393

    Privacy on the level of AP would have been very easy to add, by just using a different salmon endpoint for private messages. This was discussed at length back then, but Mastodon st…

  14. comment
    Comment #15516284

    sadly, the federated timeline is close to useless. I don't understand why it isn't the public timeline that's exposed.

  15. comment
    Comment #15516145

    This is something that was always a problem on Mastodon, but you can use other fediverse servers like https://social.sakamoto.gq/main/all to look at the network, they show things p…

  16. comment
    Comment #14476107

    If you are European you're probably part of the visa waiver program anyway.

  17. comment
    Comment #12700902

    I looked into this a while ago. Here are some notes I made: - https://git.heldscal.la/roger/the_wired/wiki/OStatus - https://git.heldscal.la/roger/the_wired/wiki/Salmon Hope it hel…

  18. story
  19. story
  20. comment
    Comment #12071894

    It depends on your use case. The overhead is much smaller than you probably think and the Erlang / Elixir programming model works extremely well for some cases, networking for exam…

  21. comment
    Comment #10533451

    How do you take photos that look like the old ones? They seem to have much more interesting colors.

  22. comment
    Comment #10505190

    That's what I meant, sorry for the confusion.

  23. comment
    Comment #10500399

    Thanks for the answer, but if you don't care about this use case, then I think I'll just use a different application that does. The things I don't like about Signal / Textsecure ar…

  24. comment
    Comment #10500265

    Just use Conversations. It can now use the same protocol and is the best XMPP client there is. I'm completely baffled that the Textsecure people insist on using the gapps package, …

  25. story