mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Server stats:

2.7K
active users

#distributedpress

1 post1 participant0 posts today

100+ websites are now published on the #DWeb with @distributedpress! Congrats! 🎉

Join the endeavor towards making the Web beautiful again — open, uncensorable, and free — just like it used to be 🌻

👉 Explore the DWeb here: explore.distributed.press/
(Browse via ipfs:// or hyper:// on supported browsers)

explore.distributed.pressDistributed Press Site IndexExplore the Distributed Press ecosystem. Find sites leveraging decentralized publishing.
Replied in thread

@hrefna That's the sort of approach we're taking at #DistributedPress

If you're going to be at rue fediforum tomorrow we're planning to have a session to get more into the details :)

Right now we've split the content/publishing/serving/inbox/reading into different components that can be mixed and matched

esta semana me tocó implementar herramientas de moderación para la integración entre #DistributedPress y @sutty :D

la onda es que cuando un sitio tiene activada la opción del #fediverso en sutty, podemos seguir sus artículos desde acá y cuando respondemos, entra en una cola de moderación donde le usuarie del sitio pueden decir a nivel comentario, cuenta o instancia qué hacer.

además viene con tres listas de bloqueo reconocidas (#TheBadSpace, oliphant y gardenfence) que bloquean unas 400 instancias.

mañana me toca enviar y recibir reportes de cuentas remotas :³

One of the neat innovations of the #DistributedPress #SocialInbox is that instead of having a large central instance database everyone pulls from for their clients, each user has a personal database of just the things they got sent. From there they can pull data from people they follow and replies using the ActivityPub client-server API. This means that the data you see has a higher social context to who you interact with rather than a grab bag of whatever folks throw onto the global timeline.

Continued thread

Además de fermentar verduras, estas últimas semanas estuve trabajando en añadir soporte #ActivityPub a @sutty a través de #DistributedPress. De ahí salió un plugin de caché para httparty y un cliente #ruby API para DistributedPress. Este cliente también puede extraer y desreferenciar actividades de instancias remotas utilizando firmas HTTP (HTTP Signatures), por lo que podría funcionar también como cliente AP genérico.

Cuando un sitio web gestionado con Sutty recibe un comentario/solicitud de seguir/favorito/impulso, se agrega a una cola de moderación donde se puede decidir qué hacer.

También estamos organizando talleres con colectivxs para implementar funciones que sean útiles para todes :D

Besides fermenting vegetables, I've been working on adding #ActivityPub support to @sutty through #DistributedPress these past weeks. We ended up with a caching plugin for httparty and a #ruby API client for DistributedPress. This client can also pull and dereference activities from remote instances using HTTP signatures, so it could double as an AP client too.

So when a website managed with Sutty gets a comment/follow/like activity, you get a moderation queue where you can decide what to do with it.

We're also hosting workshops with collectives so we implement features that are useful to all :D

Continued thread

Suuuper rough sketch for anyone interested. Basically we'll have a list of accounts you follow in localStorage, then ingest their outboxes into this. Then we'll set up fully p2p identities and use the #DistributedPress #SocialInbox as another source to ingest stuff like followers only posts and replies from people you don't follow.

github.com/hyphacoop/reader.di

GitHubAdd database with indexing by RangerMauve · Pull Request #3 · hyphacoop/reader.distributed.pressBy RangerMauve

Hey fedifolks! I was hoping to get some bikeshedding feedback on a new #FEP we're working on at #DistributedPress.

tl;dr we want #ActivityPub objects to link to #P2P URLs for alternate ways to load them. Right now I'm debating between putting them in `alsoKnownAs` or into the `url` field. e.g. `"alsoKnownAs": ["ipns://staticpub.mauve.moe"]` for @mauve@staticpub.mauve.moe

I worry that field is already in use and that it could cause trouble. Would a new field name be better? Maybe `alternateURL`?

📣 Announcing DP Social Inbox!

I've had the pleasure of contributing to the development of the #DistributedPress Social Inbox with an incredibly talented team at hypha.coop @dripline.
This tool brings social interactions to static websites on the decentralized web.
hypha.coop/dripline/announcing

Hypha Worker Co-operativeAnnouncing Distributed.Press Social Inbox 1.0Our new feature brings social interactions to static websites on the decentralized web.