FreeAssembly

108 readers

11 users here now

this is FreeAssembly, a non-toxic design, programming, and art collective. post your share-alike (CC SA, GPL, BSD, or similar) projects here! collaboration is welcome, and mutual education is too.

in brief, this community is the awful.systems answer to Hacker News. read this article for a solid summary of why having a less toxic collaborative community is important from a technical standpoint in addition to a social one.

some posting guidelines apply in addition to the typical awful.systems stuff:

all types of passion projects and contributions are welcome, including and especially those that aren't programming or engineering in nature
this is an explicitly noncommercial, share-alike space
don't force yourself to do work you don't enjoy, or demand it of others

(logo credit, with modifications by @dgerard@awful.systems)

founded 1 year ago

MODERATORS

self@awful.systems

a blind man stumbles into the activitypub (awful.systems)

submitted 11 months ago by froztbyte@awful.systems to c/freeasm@awful.systems

6 comments fedilink hide all child comments

since I haven't touched AP before (and figure other possible contributors may not have either), going to use this post as wayfarer bathroom graffiti

feel free to contribute your own learning and investigation as well

you are viewing a single comment's thread
view the rest of the comments

[–] dgerard@awful.systems 5 points 11 months ago* (last edited 11 months ago)

probably the first thing to learn is:

activitypub is underspecified and the implementations are idiosyncratic.

this means that you can only get interoperability that works by trying pairs of software against each other and seeing what works. following the spec is only the first step.