home.social

#microdon — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #microdon, aggregated by home.social.

fetched live
  1. I started working on the #Microdon Fediverse back-end again because (in part) I wanted to work on the #ProToGo Fediverse front-end again.

    Microdon is a light-weight single-user Fediverse back0end.

    ProToGo is a career oriented Fediverse front-end.

    #Microdon #ProToGo

  2. I started working on the #Microdon Fediverse back-end again because (in part) I wanted to work on the #ProToGo Fediverse front-end again.

    Microdon is a light-weight single-user Fediverse back0end.

    ProToGo is a career oriented Fediverse front-end.

    #Microdon #ProToGo

  3. RE: mastodon.social/@reiver/112921

    2/

    I want this (back-end Fediverse servers and front-end Fediverse clients as separate projects) for myself, too.

    To try to make development for myself easier.

    One of the Fediverse servers of this type that I have been working on is Microdon:

    codeberg.org/reiver/microdon

    It is meant for a light-weight single-user use-case.

    ...

    I have found myself working on it (Microdon) again recently.

    ...

    ("Microdon" is the name of several fish if you are curious about the name.)

    #FediDev #Microdon

  4. RE: mastodon.social/@reiver/112921

    2/

    I want this (back-end Fediverse servers and front-end Fediverse clients as separate projects) for myself, too.

    To try to make development for myself easier.

    One of the Fediverse servers of this type that I have been working on is Microdon:

    codeberg.org/reiver/microdon

    It is meant for a light-weight single-user use-case.

    ...

    I have found myself working on it (Microdon) again recently.

    ...

    ("Microdon" is the name of several fish if you are curious about the name.)

    #FediDev #Microdon

  5. RE: mastodon.social/@reiver/112921

    1/

    The Fediverse would be better off if if back-end servers and front-end clients were separate projects.

    I have been arguing that for a while.
    (I know I am not the only one.)

    With respect to Fediverse server, there are different types you might want, depending on your needs. And, it would be nice if you could pick and choose (separate from your choice of front-end).

    For example, is it single-user or mutli-user? Should it be light-weight, or deal with high-scale? Etc?

    #FediDev #Microdon

  6. RE: mastodon.social/@reiver/112921

    1/

    The Fediverse would be better off if if back-end servers and front-end clients were separate projects.

    I have been arguing that for a while.
    (I know I am not the only one.)

    With respect to Fediverse server, there are different types you might want, depending on your needs. And, it would be nice if you could pick and choose (separate from your choice of front-end).

    For example, is it single-user or mutli-user? Should it be light-weight, or deal with high-scale? Etc?

    #FediDev #Microdon

  7. CW: microdon

    Added basic nodeinfo support to microdon.

    It uses its own stlyle of path for each nodeinfo file. But also supports Akkoma, Firefish, Pixelfed, and Mastodon style paths, too.

    #microdon #nodeinfo

  8. CW: microdon

    Added basic nodeinfo support to microdon.

    It uses its own stlyle of path for each nodeinfo file. But also supports Akkoma, Firefish, Pixelfed, and Mastodon style paths, too.

    #microdon #nodeinfo