home.social

#emmett — Public Fediverse posts

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

fetched live
  1. ⚠️ Emmett framework (2.5.0 – <2.8.1) suffers from a CRITICAL path traversal (CVE-2026-39847). Attackers can remotely read files outside the asset directory. Patch by upgrading to 2.8.1+. Details: radar.offseq.com/threat/cve-20 #OffSeq #Emmett #PathTraversal #CVE202639847

  2. ⚠️ Emmett framework (2.5.0 – <2.8.1) suffers from a CRITICAL path traversal (CVE-2026-39847). Attackers can remotely read files outside the asset directory. Patch by upgrading to 2.8.1+. Details: radar.offseq.com/threat/cve-20 #OffSeq #Emmett #PathTraversal #CVE202639847

  3. ⚠️ Emmett framework (2.5.0 – <2.8.1) suffers from a CRITICAL path traversal (CVE-2026-39847). Attackers can remotely read files outside the asset directory. Patch by upgrading to 2.8.1+. Details: radar.offseq.com/threat/cve-20 #OffSeq #Emmett #PathTraversal #CVE202639847

  4. ⚠️ Emmett framework (2.5.0 – <2.8.1) suffers from a CRITICAL path traversal (CVE-2026-39847). Attackers can remotely read files outside the asset directory. Patch by upgrading to 2.8.1+. Details: radar.offseq.com/threat/cve-20 #OffSeq #Emmett #PathTraversal #CVE202639847

  5. What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!

    I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.

    Read also about more surprising places besides programming languages when compiling happens, and helps your applications!

    architecture-weekly.com/p/comp

  6. What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!

    I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.

    Read also about more surprising places besides programming languages when compiling happens, and helps your applications!

    architecture-weekly.com/p/comp

  7. What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in , I changed my mind!

    I wrote today on on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.

    Read also about more surprising places besides programming languages when compiling happens, and helps your applications!

    architecture-weekly.com/p/comp

  8. What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!

    I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.

    Read also about more surprising places besides programming languages when compiling happens, and helps your applications!

    architecture-weekly.com/p/comp

  9. What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!

    I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.

    Read also about more surprising places besides programming languages when compiling happens, and helps your applications!

    architecture-weekly.com/p/comp

  10. The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.

    Then we hear:
    - Rug pull!
    - Open Source drama!
    - Yet another License change!

    And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: github.com/event-driven-io/emm.

    If you have some thoughts around it, please comment and share with me your thoughts.

    If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.

    Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂

  11. The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.

    Then we hear:
    - Rug pull!
    - Open Source drama!
    - Yet another License change!

    And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: github.com/event-driven-io/emm.

    If you have some thoughts around it, please comment and share with me your thoughts.

    If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.

    Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂

  12. The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.

    Then we hear:
    - Rug pull!
    - Open Source drama!
    - Yet another License change!

    And guess what, I'm also want to set a dual license for and . I want to do it in a transparent way and created a dedicated, public RFC for that: github.com/event-driven-io/emm.

    If you have some thoughts around it, please comment and share with me your thoughts.

    If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.

    Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂

  13. The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.

    Then we hear:
    - Rug pull!
    - Open Source drama!
    - Yet another License change!

    And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: github.com/event-driven-io/emm.

    If you have some thoughts around it, please comment and share with me your thoughts.

    If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.

    Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂

  14. The current Open Source model assumes symmetry between all users, but... When the OSI insists cloud providers deserve equal treatment to individual developers, it forces projects into defensive positions.

    Then we hear:
    - Rug pull!
    - Open Source drama!
    - Yet another License change!

    And guess what, I'm also want to set a dual license for #Pongo and #Emmett. I want to do it in a transparent way and created a dedicated, public RFC for that: github.com/event-driven-io/emm.

    If you have some thoughts around it, please comment and share with me your thoughts.

    If you don't have, then I think that this RFC is still a decent way to learn on the OSS licensing, and why you should care about it. I tried to explain them in a straightforward way, together with the background.

    Sharing is caring, so I'd appreciate resharing or tagging someone who can have experience to share 🙂

  15. If you prefer to read, that’s fine, check #Emmett getting started, I think that’s a decent read, and not a typical boring piece of docs 🙂👌

    event-driven-io.github.io/emme

  16. If you prefer to read, that’s fine, check #Emmett getting started, I think that’s a decent read, and not a typical boring piece of docs 🙂👌

    event-driven-io.github.io/emme

  17. If you prefer to read, that’s fine, check getting started, I think that’s a decent read, and not a typical boring piece of docs 🙂👌

    event-driven-io.github.io/emme

  18. If you prefer to read, that’s fine, check #Emmett getting started, I think that’s a decent read, and not a typical boring piece of docs 🙂👌

    event-driven-io.github.io/emme

  19. If you prefer to read, that’s fine, check #Emmett getting started, I think that’s a decent read, and not a typical boring piece of docs 🙂👌

    event-driven-io.github.io/emme

  20. Looking for something to watch during the weekend? What about a lighthearted intro to #EventSourcing m.youtube.com/watch?v=SDXdcymK ? 😎

    It should give you a practical start to the most important concepts and also a good chance to learn #TypeScript modelling and how #Emmett can help! 🙂

  21. Looking for something to watch during the weekend? What about a lighthearted intro to #EventSourcing m.youtube.com/watch?v=SDXdcymK ? 😎

    It should give you a practical start to the most important concepts and also a good chance to learn #TypeScript modelling and how #Emmett can help! 🙂

  22. Looking for something to watch during the weekend? What about a lighthearted intro to m.youtube.com/watch?v=SDXdcymK ? 😎

    It should give you a practical start to the most important concepts and also a good chance to learn modelling and how can help! 🙂

  23. Looking for something to watch during the weekend? What about a lighthearted intro to #EventSourcing m.youtube.com/watch?v=SDXdcymK ? 😎

    It should give you a practical start to the most important concepts and also a good chance to learn #TypeScript modelling and how #Emmett can help! 🙂

  24. Looking for something to watch during the weekend? What about a lighthearted intro to #EventSourcing m.youtube.com/watch?v=SDXdcymK ? 😎

    It should give you a practical start to the most important concepts and also a good chance to learn #TypeScript modelling and how #Emmett can help! 🙂

  25. 👋 Folks, I need your help, I’m working on the Workflow Engine for business process orchestration in #Emmett and I want to have it in the transparent, community way.

    I prepared RFC and I’m counting on your feedback and questions! github.com/event-driven-io/emm ❤️

  26. 👋 Folks, I need your help, I’m working on the Workflow Engine for business process orchestration in #Emmett and I want to have it in the transparent, community way.

    I prepared RFC and I’m counting on your feedback and questions! github.com/event-driven-io/emm ❤️

  27. 👋 Folks, I need your help, I’m working on the Workflow Engine for business process orchestration in and I want to have it in the transparent, community way.

    I prepared RFC and I’m counting on your feedback and questions! github.com/event-driven-io/emm ❤️

  28. 👋 Folks, I need your help, I’m working on the Workflow Engine for business process orchestration in #Emmett and I want to have it in the transparent, community way.

    I prepared RFC and I’m counting on your feedback and questions! github.com/event-driven-io/emm ❤️

  29. 👋 Folks, I need your help, I’m working on the Workflow Engine for business process orchestration in #Emmett and I want to have it in the transparent, community way.

    I prepared RFC and I’m counting on your feedback and questions! github.com/event-driven-io/emm ❤️

  30. Folks, the new docs section on writing read models in #Emmett just arrived! Check it till it's fresh, and tell me how you like it!

    event-driven-io.github.io/emme

    It's a first draft, more to come and needs to be documented, but baby steps 🙂

    We'll get there!

  31. Folks, the new docs section on writing read models in #Emmett just arrived! Check it till it's fresh, and tell me how you like it!

    event-driven-io.github.io/emme

    It's a first draft, more to come and needs to be documented, but baby steps 🙂

    We'll get there!

  32. Folks, the new docs section on writing read models in just arrived! Check it till it's fresh, and tell me how you like it!

    event-driven-io.github.io/emme

    It's a first draft, more to come and needs to be documented, but baby steps 🙂

    We'll get there!

  33. Folks, the new docs section on writing read models in #Emmett just arrived! Check it till it's fresh, and tell me how you like it!

    event-driven-io.github.io/emme

    It's a first draft, more to come and needs to be documented, but baby steps 🙂

    We'll get there!

  34. Folks, the new docs section on writing read models in #Emmett just arrived! Check it till it's fresh, and tell me how you like it!

    event-driven-io.github.io/emme

    It's a first draft, more to come and needs to be documented, but baby steps 🙂

    We'll get there!

  35. I just closed the 200th Pull request in #Emmett!

    Plus #Emmett just passed 300 GitHub Stars! ⭐

    Nice milestones to cherish! Maybe it ain't much but it's honest work!

  36. I just closed the 200th Pull request in #Emmett!

    Plus #Emmett just passed 300 GitHub Stars! ⭐

    Nice milestones to cherish! Maybe it ain't much but it's honest work!

  37. I just closed the 200th Pull request in !

    Plus just passed 300 GitHub Stars! ⭐

    Nice milestones to cherish! Maybe it ain't much but it's honest work!

  38. I just closed the 200th Pull request in #Emmett!

    Plus #Emmett just passed 300 GitHub Stars! ⭐

    Nice milestones to cherish! Maybe it ain't much but it's honest work!

  39. I just closed the 200th Pull request in #Emmett!

    Plus #Emmett just passed 300 GitHub Stars! ⭐

    Nice milestones to cherish! Maybe it ain't much but it's honest work!

  40. Look, on that! I just did this print screen on recent #Emmett Pull Requests. See the names of authors. It makes me proud that majority of them are not made by me.

    It's great that we've built such an engaged and quality community around #Emmett. It's a great validation of the concept around it 🙂

  41. Look, on that! I just did this print screen on recent #Emmett Pull Requests. See the names of authors. It makes me proud that majority of them are not made by me.

    It's great that we've built such an engaged and quality community around #Emmett. It's a great validation of the concept around it 🙂

  42. Look, on that! I just did this print screen on recent Pull Requests. See the names of authors. It makes me proud that majority of them are not made by me.

    It's great that we've built such an engaged and quality community around . It's a great validation of the concept around it 🙂

  43. Look, on that! I just did this print screen on recent #Emmett Pull Requests. See the names of authors. It makes me proud that majority of them are not made by me.

    It's great that we've built such an engaged and quality community around #Emmett. It's a great validation of the concept around it 🙂

  44. Look, on that! I just did this print screen on recent #Emmett Pull Requests. See the names of authors. It makes me proud that majority of them are not made by me.

    It's great that we've built such an engaged and quality community around #Emmett. It's a great validation of the concept around it 🙂

  45. 🎉 Small step, but big milestone for #Emmett, I just released the first version of async projections for #PostgreSQL!

    Check more in the release notes: github.com/event-driven-io/emm

  46. 🎉 Small step, but big milestone for #Emmett, I just released the first version of async projections for #PostgreSQL!

    Check more in the release notes: github.com/event-driven-io/emm

  47. 🎉 Small step, but big milestone for , I just released the first version of async projections for !

    Check more in the release notes: github.com/event-driven-io/emm

  48. 🎉 Small step, but big milestone for #Emmett, I just released the first version of async projections for #PostgreSQL!

    Check more in the release notes: github.com/event-driven-io/emm

  49. 🎉 Small step, but big milestone for #Emmett, I just released the first version of async projections for #PostgreSQL!

    Check more in the release notes: github.com/event-driven-io/emm

  50. So I just closed 150th PR to #Emmett. Nice milestone 🙂🎉

    Also I did 2 releases recently driven by community changes.

    Steadily, step by step bootstrapping the project with still small but vibrant community.

    Check more in: github.com/event-driven-io/emm

  51. So I just closed 150th PR to #Emmett. Nice milestone 🙂🎉

    Also I did 2 releases recently driven by community changes.

    Steadily, step by step bootstrapping the project with still small but vibrant community.

    Check more in: github.com/event-driven-io/emm

  52. So I just closed 150th PR to . Nice milestone 🙂🎉

    Also I did 2 releases recently driven by community changes.

    Steadily, step by step bootstrapping the project with still small but vibrant community.

    Check more in: github.com/event-driven-io/emm

  53. So I just closed 150th PR to #Emmett. Nice milestone 🙂🎉

    Also I did 2 releases recently driven by community changes.

    Steadily, step by step bootstrapping the project with still small but vibrant community.

    Check more in: github.com/event-driven-io/emm

  54. So I just closed 150th PR to #Emmett. Nice milestone 🙂🎉

    Also I did 2 releases recently driven by community changes.

    Steadily, step by step bootstrapping the project with still small but vibrant community.

    Check more in: github.com/event-driven-io/emm

  55. Just read such a nice e-mail on my phone! #Emmett got a first 🥉sponsor. Thank you Product Minds!

    If you want to take back your applications back to the future with the event-driven check Emmett, as you see, it’s already getting trust in organisations 🙂

    See the project: github.com/event-driven-io/emm

    If you’d like to also want to help make my work sustainable, deliver more and better,you can also become sponsor.

    By that you also get support from me on your journey. Help me, help you 🙂

    See sponsors perks: github.com/sponsors/event-driv

    Resharing and liking this post also counts as help ❤️😅