this post was submitted on 17 Aug 2023
26 points (93.3% liked)

Fediverse

27828 readers
276 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
26
... (programming.dev)
submitted 1 year ago* (last edited 6 months ago) by [email protected] to c/fediverse
all 13 comments
sorted by: hot top controversial new old
[–] [email protected] 7 points 1 year ago

Lemmy

It just needs more users and it's perfect.

[–] [email protected] 7 points 1 year ago

Lemmy but with the resources to host video

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago)

A wiki with strong moderation tools, and gnupg signed/verified text built into it from the start.

An activitypub method to keep git repos in sync automatically.

A small blog type tool that's used as a replacement for facebook. It would have a hosted "gathering" component that is always online, then when you open your local app, it pulls down all your stuff.

Shared secrets like a distributed KeePass or Bitwarden.

Distributed home directory and/or development environments.

Something like the useful bits from KeyBase. I really wanted keybase to be something that could support this use case: Alice@foo gets a dev job at Bar. Her ID is added to the cool_project@bar group and automatically she has access to all the group's ~~big~~ bug tracking, file shares, wiki, git repos, group chats, etc. Her joining the group is recorded in a permanent record, which can be publicly or privately annotated by people specifically allowed by the group she joined. It'd become an automatic resume.

[–] donio 5 points 1 year ago* (last edited 1 year ago) (1 children)

I'd really like to see some client-API consolidation. A common client API that could efficiently handle both "microblog" style and threaded discussions (lemmy etc) and leave the door open for other discussion formats too. This would allow for clients/frontends to flourish even more and backends could compete on features and efficiency. The backend specific features could be expressed through an extension mechanism of the common API.

[–] [email protected] 2 points 1 year ago

I feel like something like that would need to be discussed at the standards level; a common API spec could maybe be issued as an extension of the current ActivityPub standard. Call it "CommonSocial", or something.

[–] cow 1 points 1 year ago

Peertube but not written in JavaScript

[–] [email protected] 1 points 1 year ago

It exists, it's Firefish, it has everything I need.