Is this project dead?

[yonas]

There hasn't been any commits in the past two years.

[vinipsmaker]

2016-07-31 2:54 GMT-03:00 Yonas Yanfa notifications@github.com:

There hasn't been any commits in the past two years.

I'm not an official member of the project, so I cannot speak for it.

However, it looks pretty dead to me. You can actually use it, but the Java
implementation is slow to open and resource-hungry and I wouldn't enjoy
keeping this application open at all.

I liked the concept and I'd love to see a reimplementation, but I'm myself
busy with Boost.Http right now, so I can't do this yet.

Vinícius dos Santos Oliveira
https://vinipsmaker.github.io/

[yonas]

Thanks @vinipsmaker! Do you know of a good alternative? A project that is being actively maintained.

[vinipsmaker]

To not introduce bias of my preferences, I'm also giving you a link to a pretty long list of projects (some similar, most different...): https://github.com/redecentralize/alternative-internet

I'd suggest you to stay away from GNU social because it's not that resistant against censorship and don't solve problems.

I guess the most popular one right now is http://twister.net.co/, but as I haven't really been following I cannot comment on that.

[KaptainKappa]

Apologies for commenting so late.

For my bachelor's final year dissertation, I have written an implementation of TRSST in C#/.NET that can generate feeds and entries that conform to the "spirit" of TRSST, in that feeds/entries cannot be tampered with by external parties without detection, asymmetric encryption is supported and account IDs correspond to Bitcoin addresses.

However, the implementation does not follow the "letter" of TRSST, in that it cannot post to the current TRSST server in the same way the Java client can. This is partly because there is no "letter" or formal specification for laying out feeds or entries defined, however I've managed to get accounts posting to the local file system and cloud storage.

In the dissertation report, I concluded that the best step forward was to write a formal specification for the structure of TRSST feeds and entries (most likely based on Atom) as well as how clients and servers shall communicate, which will allow for third parties to write client and/or server software themselves, if they so choose, in a manner similar to email clients. I'll see if I can negotiate with the university's faculty to have a PhD project including this.

At the moment, the project hasn't been marked, so I can't post the report or the code as of yet, plus I'll be the first to say that the code is currently a dog's breakfast, unfit for public eyes. Hopefully marking will be done by October, so I'll post the code/report then if there's sufficient interest.

[yonas]

@KaptainKappa Thanks! It would be great to have a link to your code when it's ready.

[vinipsmaker]

At the moment, the project hasn't been marked, so I can't post the report or the code as of yet

Looking forward to read it when you're ready to share it.
:)

[TheAndruu]

Since you brought it up... I forked this from Trsst a while ago and re-wrote much of the server portion which may make it easier to manage if anyone wants to delve into it.
https://github.com/TheAndruu/complete-trsst

The server code is cleaned up, and there's instructions in the README for running. If anyone wants to make a client to invoke the server endpoints... that should be all that's left to be done on this.

[yonas]

@TheAndruu Fantastic! That's very helpful. We should contact the owner of this project and discuss merging in your changes.

[KaptainKappa]

My dissertation project has finally been marked and can now be released to the public, as below:

Report.pdf

I think future contributors may be interested in sections 5-7 (pages 13-18) more than anything else, in which I describe the implementation of key features, critique the TRSST white paper, and propose further avenues of development for the TRSST protocol as a whole.

[yonas]

Thanks @KaptainKappa!

With the freedom of speech issues Twitter is now facing, I think finding an alternative solution has become very important.

[fiatjaf]

Hey, everybody. We have a small but growing community around a protocol and some independent clients being developed at https://github.com/fiatjaf/nostr, which I think is the best solution to censorship-resistant, scalable communication and "social networking" on the internet until now.

Nostr's idea is very similar to trsst: each person has a keypair and publishes content to multiple independent servers that are online somewhere. It doesn't matter if these servers go malicious or go offline because other servers can be used and users never lose their identities. Anyone can run one of these servers.

It's a very simple design with a ton of flexibility and also some safeguards for ensuring a malicious server can't do much damage.

Although I think the idea is quite obvious the only other project that I found on the internet that is similar to Nostr until now is trsst. Please join us! There's even a Telegram channel for these early development stages with regular voice calls.

[singlemaltz]

There was a kickstarter that raised $65K for this project but all communication from Michael Powers stopped soon after.

Hope he didn't die.

https://www.kickstarter.com/profile/1904431672