GithubHelp home page GithubHelp logo

catalyst's Introduction

catalyst

(wip) flexible social blogging/news platform for encouraging intercommunity communication among local communities.

building

build webserver: cargo build --release build wasm blob: cargo run --bin xtask

running

cargo run --release --bin catalyst

This will run a webserver on 0.0.0.0:8080 (or localhost:8080).

Roadmap

In intended order of implementation:

  • Make and reference immutable posts with sanitized html
  • Support browsers that don't have setHTML support (?)
  • Special posts that allow linking and post management/"deletion"
  • Optionally sign posts and maintain an identity
  • Document API endpoints and expected3
  • Support multiple identities
  • Author profile pages
  • Sync posts between nodes via webrtc
  • Per user and per instance permissioning
  • Use webrtc for user-facing chat+video too
  • Harden privacy and security guarantees
  • Document trust model clearly
  • Private/encrypted/group-private posts & messages
  • Basic image+video transcoding, hosting
  • Identity/fact attestation and local user beliefs.
  • Claim+verify same-person-ness (for multidevice support)

In no particular order:

  • Better optimize DB queries for memory use
  • some system to create and execute db migrations
  • User friendly post editing (automate creating a new post linked to an outdated post)
  • WYSIWYG editor mode and tools
  • First class listings/classifieds post types to let folks do commercial stuff easily
  • Enable isters to use their preferred payment backends safely
  • Special post types for IOUs and other public commitments
  • Give users access to directly modify local recommendation engine
  • Search / Topics
  • Notifications of some kind (not push), read notifications tracking

catalyst's People

Contributors

jam10o-new avatar twistedporkchop avatar

Stargazers

 avatar Nora avatar

Forkers

twistedporkchop

catalyst's Issues

[feats] features for biasing post retrieval

Default get_posts endpoint currently returns one post per author - this currently puts signalling messages (which we intend to hide) at the same level as other posts, which can lead to sparse first loading pages (as most posts would be hidden) - we should change the default get_posts to another method that is not one-post-per-author, or at least allow hidden posts not to count towards max_posts

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.