Parastat @parastat@octodon.social

@loweel we don't owe you anything.
Please be demanding in someone else's mention.

@tixie thank you :)
We have a great designer, that helps a lot

A small reminder that if you have question on #parastat , you can always @ this account.

The answer will likely take sometime, but usually we reply to everyone that has questions.

(note: @ our individual accounts with generic question is bad form tho)

Some taste of what is to come (this is not a mockup tho, its the real thing)

#parastat

The fediverse in 2019 https://fediverse.party/en/post/fediverse-in-2019 by people over at @feneas

@schmittlauch
OCAP is there to fix ActivityPub problems, but doesn't change AP fundamentally.

Maybe there are voices that never make it to the W3C.
Maybe design by committee is not the only way we should build the fedi.
We think that there is power in diversity.

People rolled their own protocol before, the fediverse has quite a few: Dispora, ActivityPub, OStatus, Zot, DFRN already (handy picture attached).

I'd argue Mastodon has been and is a success despite underlying protocol(s).

@schmittlauch There will be one of us at fosdem, so maybe not a rounded representation of the whole project/team.

On AP, we probably plan to do both communication on a subset of the feature. It is not written yet, so I cannot really tell you more than that.

Compromise are usually good, nothing fits every use case right.
We might just not share the same ones to the w3c working groups on social stuff.

I'm not sure where you get the idea of proprietary protocol, it wont be proprietary

Going to #Fosdem ?
Want to get some parastat sticker?

Find the Purple hoodie wearer with our logo at the front

@Brainship @dzuk I think we have better left to right support, more themes that catters for different kind of visions and have screen reader a first class citizen (not that we are expert on making interfaces for screen reader yet).

Accessibility is also in the resource needed eg. device spec required to use parastat. People on low end device should be able to use the web interface of parastat

@riking I'm not sure what to reply because conceptually we will likely not have a concept of "not authenticated".
There is also some more on top of that, but that's a full length blog post, which will be for another day unfortunately

@dzuk

@IceWolf there are a few differences in what our goals are with our own protocol vs ActivityPub.

We want the protocol to be fairly small over the wire and that means looking at every layer in SSL/TLS, HTTP, ActivityPub and see what we can do differently to be achieve a small footprint.

There are other security aspect we want to make a core part of the protocol. We will have more on what we mean by that as a long post, but that's for another day

@dzuk