home.social

#tasky — Public Fediverse posts

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

  1. #Tasky :mastodon_mascot: くんは、ブラウザで表示中のページをシェアするとアドレスだけじゃなくてページタイトルも投稿欄にあらかじめ入れてくれて、しかもそれをキャレットの一行下記載しておいてくれるから好き :tony_smirking:

    #Mastodon #Android

  2. #Pachli っていう :android_logo: 向け :mastodon: クライアント :mastodon_mascot:

    hachyderm.io という、テック周りで結構有名な方のアカウントがある :mastodon: サーバー(自分がメインで使ってる :mastodon: Web クライアントの #PhanpySocial の公式アカウントもこのサーバーにある)を運営してる The Nivenly Foundation というところが開発してるクライアントっぽい。
    これも試してないけど、 #Tasky が好きな人なら気に入るはずだよみたいな説明がついてるからそういうシンプルめのクライアントっぽい雰囲気

    Cooperative social media
    pachli.app/

    #Android #Mastodon

  3. The next set of features I want to add to my event-engine for DLang, Eventy, are now all set out - what would have been very easy to do in C (signals etc.) is a little harder in D as such bindings do not exist - however - one can bring them in using ImportC!

    In any case, both the ideas and implementation details are now all layed out. Adding promises with await() and then() functionality. The former which will actually make finally implementing my network-scheduler #Tasky a lot easier.

    http://deavmi.assigned.network/blog/new_eventy_goals/

    #dlang #eventy #eventdriven
  4. Going to afk from my laptop this afternoon and evening, write some notes and see if I can come up with a nice way to reimplement #Tasky both protocol wise and also user-end API wise. The latter point is really what matters and is what I want to implement in a very-nice manner.
  5. One of the things I have planned is to rewrite my #Tasky network scheduler - so that will need some work first of all before any of this can start.
  6. I will be ontop of #tlang, #tasky, #crxn, #bnet and more... just this which has been taking up my time the last few months
  7. Spending this weekend on the #Tasky website!

    (Oh look at that, a screenshot with my other screen included 😆 )
  8. Just finished re-working some of #Eventy now to make it work better for #Tasky. I am glad how it turned out as my event-engine is still generalized in this fashion and to be quite honest a lot neater now too due to this update.

    I'm going to probably spend the next few days working on tidying it up, pushing a new version, integrating it with #Tasky and then pushing some of that stuff out.

    I do however think it will be a good time to start writing some documentation for the former, that'd be nice.


    A nice thing too is that the unittests passed, so I'm happy about that!
  9. Whilst I work on learning #Nelua, finishing up #tasky. I am also teaching myself some #Ada!