home.social

#tuskphp — Public Fediverse posts

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

fetched live
  1. Taking a break from the fishing game I was building while taking a break from #TuskPHP to see if I can build a tiny #MastodonBot in #Rust.

    It is a bot which flips a coin.

    I'm calling it #CoinFlipBot.

    So far I can get a random coin flip result, and set a GET request. This might take a while.

    github.com/AndrewFeeney/coinfl

  2. Taking a break from the fishing game I was building while taking a break from #TuskPHP to see if I can build a tiny #MastodonBot in #Rust.

    It is a bot which flips a coin.

    I'm calling it #CoinFlipBot.

    So far I can get a random coin flip result, and set a GET request. This might take a while.

    github.com/AndrewFeeney/coinfl

  3. @beausimensen @Njames @ramsey @jaytaph @coulb I always try to mark my work on Tusk (working title only, will probably rename if I spend much more time on it) with the #TuskPHP hashtag, and the more general #ActivityPubDev hashtag.

  4. @beausimensen @Njames @ramsey @jaytaph @coulb I always try to mark my work on Tusk (working title only, will probably rename if I spend much more time on it) with the #TuskPHP hashtag, and the more general #ActivityPubDev hashtag.

  5. Current status: Temporarily distracted from my #TuskPHP tinkering, making an arcade style fishing game for my daughter for the holidays.

    That's right, fishing. I thought it was pretty obvious from the screenshot. Can't you see the fishing line and the fish?

  6. Current status: Temporarily distracted from my #TuskPHP tinkering, making an arcade style fishing game for my daughter for the holidays.

    That's right, fishing. I thought it was pretty obvious from the screenshot. Can't you see the fishing line and the fish?

  7. @[email protected] @[email protected] I've watched this talk twice and I'd like to spend some time working with this approach to see how it feels.

    I'm going to try to incorporate this kind of approach in my #TuskPHP project and see how it goes.

  8. @[email protected] @[email protected] I've watched this talk twice and I'd like to spend some time working with this approach to see how it feels.

    I'm going to try to incorporate this kind of approach in my #TuskPHP project and see how it goes.

  9. #TuskPHP update:

    Success! I was able to post a reply to an existing toot on a Mastodon instance.

    #php #laravel #activitypub #activitypubdev

  10. #TuskPHP update:

    Success! I was able to post a reply to an existing toot on a Mastodon instance.

    #php #laravel #activitypub #activitypubdev

  11. Today's increment for #TuskPHP:

    Finished a method to generate the signing string. Next will be to implement adding the signature header to the request.

    Been a bit distracted this week with family life, and ChatGPT.

    Crawling along, but getting there.

    github.com/AndrewFeeney/tusk/c

    #php #laravel #activitypub #activitypubdev

  12. Today's increment for #TuskPHP:

    Finished a method to generate the signing string. Next will be to implement adding the signature header to the request.

    Been a bit distracted this week with family life, and ChatGPT.

    Crawling along, but getting there.

    github.com/AndrewFeeney/tusk/c

    #php #laravel #activitypub #activitypubdev

  13. Another #TuskPHP thought. I'm thinking I'll try to build it without the assumption of a SQL database. It seems to me one of the scaling issues that the #mastodonadmin community is having is around the fact that the database has to be a single node, and can only be scaled vertically, which works fine but has limits and becomes expensive.

    I'm thinking I would like to design it with compatibility with a database option that's designed to run as a cluster to allow for easier horizontal scaling.

  14. Another #TuskPHP thought. I'm thinking I'll try to build it without the assumption of a SQL database. It seems to me one of the scaling issues that the #mastodonadmin community is having is around the fact that the database has to be a single node, and can only be scaled vertically, which works fine but has limits and becomes expensive.

    I'm thinking I would like to design it with compatibility with a database option that's designed to run as a cluster to allow for easier horizontal scaling.

  15. Tonight's #TuskPHP increment:

    Among other things, inroads into logic for determining the appropriate signing string for the request. This may be the origin of my problem with getting mastodon to verify the signature of my request when #federating.

    github.com/AndrewFeeney/tusk/c

    #php #laravel #activitypub #activitypubdev

  16. Tonight's #TuskPHP increment:

    Among other things, inroads into logic for determining the appropriate signing string for the request. This may be the origin of my problem with getting mastodon to verify the signature of my request when #federating.

    github.com/AndrewFeeney/tusk/c

    #php #laravel #activitypub #activitypubdev

  17. I’m thinking through directions for #TuskPHP in terms what makes sense for me to spend my spare time on.

    As tempting as it feels to jump into front end stuff and start building my own Twitter clone, I feel like I need to avoid that urge. I know I *could* do that and it would be fun for a while, but in the end it’s a recipe for an abandoned project.

    My opinions on a microblogging front end won’t please anyone but me, and I can’t build something as slick as what people are used to in spare time.

  18. I’m thinking through directions for #TuskPHP in terms what makes sense for me to spend my spare time on.

    As tempting as it feels to jump into front end stuff and start building my own Twitter clone, I feel like I need to avoid that urge. I know I *could* do that and it would be fun for a while, but in the end it’s a recipe for an abandoned project.

    My opinions on a microblogging front end won’t please anyone but me, and I can’t build something as slick as what people are used to in spare time.

  19. Tonight's #TuskPHP increment.

    After much gnashing of teeth and some lessons on RSA padding schemes over the last few days, I get a simple test up and running for a basic signature service. I haven't actually swapped out the existing signature implementation yet but I'm hoping this will solve my signature woes.

    I took my example values from this document datatracker.ietf.org/doc/html/ which was cited in the landrok/activitypub package codebase.

    #php #ActivityPub #activitypubdev #laravel

  20. Tonight's #TuskPHP increment.

    After much gnashing of teeth and some lessons on RSA padding schemes over the last few days, I get a simple test up and running for a basic signature service. I haven't actually swapped out the existing signature implementation yet but I'm hoping this will solve my signature woes.

    I took my example values from this document datatracker.ietf.org/doc/html/ which was cited in the landrok/activitypub package codebase.

    #php #ActivityPub #activitypubdev #laravel

  21. #TuskPHP update.

    I've been spinning my wheels for a couple of days trying to post a reply to a toot on mastodon. I've ended up just getting 500 errors back from mastodon and I'm out of ideas of how to debug that without deploying my own instance. I've tried fiddling around with a local dev instance but it complains about self signed SSL.

    Instead I'm going to take a step back and see what other parts of #ActivityPub I can implement in my experimental project.

    #php #laravel #activitypubdev

  22. #TuskPHP update.

    I've been spinning my wheels for a couple of days trying to post a reply to a toot on mastodon. I've ended up just getting 500 errors back from mastodon and I'm out of ideas of how to debug that without deploying my own instance. I've tried fiddling around with a local dev instance but it complains about self signed SSL.

    Instead I'm going to take a step back and see what other parts of #ActivityPub I can implement in my experimental project.

    #php #laravel #activitypubdev

  23. Tonight's #TuskPHP contribution:

    I think I've sorted the digest header issues, and I'm now getting 500 errors from Mastadon. I can see some errors in my logic, and resulting JSON so I've got some leads to follow, but once again it's time to get some sleep.

    Slowly getting closer ...

    #php #laravel #activitypub #activitypubdev

  24. Tonight's #TuskPHP contribution:

    I think I've sorted the digest header issues, and I'm now getting 500 errors from Mastadon. I can see some errors in my logic, and resulting JSON so I've got some leads to follow, but once again it's time to get some sleep.

    Slowly getting closer ...

    #php #laravel #activitypub #activitypubdev

  25. Tonight's #TuskPHP contribution.

    After deploying my work so far to a public server I found that I was missing the "Digest" header. Turns out that this is a requirement which has been added to Mastodon's ActivityPub implementation since the article I was reading had been written.

    Some googling lead me to a few online discussions, and finally to this example from the #Drupal community: git.drupalcode.org/project/act which was helpful.

    #php #laravel #activitypub

  26. Tonight's #TuskPHP contribution.

    After deploying my work so far to a public server I found that I was missing the "Digest" header. Turns out that this is a requirement which has been added to Mastodon's ActivityPub implementation since the article I was reading had been written.

    Some googling lead me to a few online discussions, and finally to this example from the #Drupal community: git.drupalcode.org/project/act which was helpful.

    #php #laravel #activitypub

  27. Tonights #TuskPHP contribution:

    Implementing a show post endpoint, some refactoring, and finally the command to send a reply to a post:

    github.com/AndrewFeeney/tusk/c

    _In theory_ if this was deployed to a domain secured with TLS it would be possible to reply to posts with this command.

    I haven't tested it though because it's late and I've run out of time to deploy it somewhere. Maybe tomorrow ...

    #php #laravel #activitypub

  28. Tonights #TuskPHP contribution:

    Implementing a show post endpoint, some refactoring, and finally the command to send a reply to a post:

    github.com/AndrewFeeney/tusk/c

    _In theory_ if this was deployed to a domain secured with TLS it would be possible to reply to posts with this command.

    I haven't tested it though because it's late and I've run out of time to deploy it somewhere. Maybe tomorrow ...

    #php #laravel #activitypub

  29. Latest #TuskPHP contribution.

    A little more refactoring, cleaning up some domain language confusion between usernames and handles.

    github.com/AndrewFeeney/tusk/c

    I'm really skirting around the edges of actual "try sending a post" thing ... maybe tomorrow.

    #php #laravel #activitypub

  30. Latest #TuskPHP contribution.

    A little more refactoring, cleaning up some domain language confusion between usernames and handles.

    github.com/AndrewFeeney/tusk/c

    I'm really skirting around the edges of actual "try sending a post" thing ... maybe tomorrow.

    #php #laravel #activitypub

  31. In the #fediverse, does the term #handle refer to the fully qualified username and dome, e.g. [email protected]? Is the leading '@' considered part of the 'handle'?

    #TuskPHP #ActionPub

  32. In the #fediverse, does the term #handle refer to the fully qualified username and dome, e.g. [email protected]? Is the leading '@' considered part of the 'handle'?

    #TuskPHP #ActionPub

  33. My latest #TuskPHP contribution:

    I allowed myself the luxury of some refactoring. As often happens when I do that I think I might have taken things a bit far, and neglected to honour my previously stated intentions of not worrying about architecture yet.

    I've decoupled things from the database a bit and refactoring the existing logic into domain objects. Not sure if the new namespace structure will stick.

    github.com/AndrewFeeney/tusk/c

    Next step, back to that command.

    #php #laravel #activitypub

  34. My latest #TuskPHP contribution:

    I allowed myself the luxury of some refactoring. As often happens when I do that I think I might have taken things a bit far, and neglected to honour my previously stated intentions of not worrying about architecture yet.

    I've decoupled things from the database a bit and refactoring the existing logic into domain objects. Not sure if the new namespace structure will stick.

    github.com/AndrewFeeney/tusk/c

    Next step, back to that command.

    #php #laravel #activitypub

  35. Latest #TuskPHP increment:

    I signed the request to send a reply to a Mastodon post and verified the signature in the test.

    github.com/AndrewFeeney/tusk/c

    Next step will be to add a command to manually trigger a command, and then deploy it to a domain secured with TLS, and see if it actually works.

    #php #laravel #activitypub

  36. Tonight's #TuskPHP mini contribution:

    A first pass at creating a reply in PHP based in this tutorial for Ruby: blog.joinmastodon.org/2018/06/

    Ran out of time to sign the request and verify the signature in the test; a job for the next contribution.

    Once again, I'm trying to think as little as possible about architecture, performance, abstraction, etc. Just focusing on having a test, making it green, moving on. Not even really refactoring yet (still learning Activity Pub)

    #laravel #php #activitypub

  37. Tonight's #TuskPHP mini contribution.

    A rough and ready webfinger endpoint:

    github.com/AndrewFeeney/tusk/c

    In the interests of moving forward despite really not having time for this project I'm trying really hard to write stupid code that makes the test green and does literally nothing else. Not worrying about writing good code or fast code, and not worrying about handling edge cases that the tests don't ask me to worry about.

    #php #laravel #activitypub

  38. Tonight's #TuskPHP mini contribution.

    A rough and ready webfinger endpoint:

    github.com/AndrewFeeney/tusk/c

    In the interests of moving forward despite really not having time for this project I'm trying really hard to write stupid code that makes the test green and does literally nothing else. Not worrying about writing good code or fast code, and not worrying about handling edge cases that the tests don't ask me to worry about.

    #php #laravel #activitypub

  39. #TuskPHP update.

    Okay, here's a little foot in the door. I drove out a quick and nasty endpoint for the actor JSON-LD endpoint.

    Here's the test:

  40. #TuskPHP update.

    Okay, here's a little foot in the door. I drove out a quick and nasty endpoint for the actor JSON-LD endpoint.

    Here's the test:

  41. I started tinkering last night, just looking for a crack in the door to get my foot in. I need a working title to hashtag these posts with. I'm thinking #TuskPHP for now.