home.social

#shlink — Public Fediverse posts

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

  1. 🚀 Vos URLs n’ont qu'à bien se tenir !
    Marre des liens à rallonge ? Je viens de stabiliser mon infrastructure #Shlink ! 🔗 (Regardez-moi ce tableau de bord tout propre en images 👇)

    Si mon instance moteur reste mon petit jardin secret, je vous propose d'utiliser mon interface Shlink Web pour gérer vos propres serveurs en toute simplicité. C'est cadeau, c'est libre, et c'est ici :
    👉 sh-admin.blablalinux.be

  2. 🚀 Vos URLs n’ont qu'à bien se tenir !
    Marre des liens à rallonge ? Je viens de stabiliser mon infrastructure #Shlink ! 🔗 (Regardez-moi ce tableau de bord tout propre en images 👇)

    Si mon instance moteur reste mon petit jardin secret, je vous propose d'utiliser mon interface Shlink Web pour gérer vos propres serveurs en toute simplicité. C'est cadeau, c'est libre, et c'est ici :
    👉 sh-admin.blablalinux.be

  3. 🚀 Vos URLs n’ont qu'à bien se tenir !
    Marre des liens à rallonge ? Je viens de stabiliser mon infrastructure #Shlink ! 🔗 (Regardez-moi ce tableau de bord tout propre en images 👇)

    Si mon instance moteur reste mon petit jardin secret, je vous propose d'utiliser mon interface Shlink Web pour gérer vos propres serveurs en toute simplicité. C'est cadeau, c'est libre, et c'est ici :
    👉 sh-admin.blablalinux.be

  4. 🚀 Vos URLs n’ont qu'à bien se tenir !
    Marre des liens à rallonge ? Je viens de stabiliser mon infrastructure #Shlink ! 🔗 (Regardez-moi ce tableau de bord tout propre en images 👇)

    Si mon instance moteur reste mon petit jardin secret, je vous propose d'utiliser mon interface Shlink Web pour gérer vos propres serveurs en toute simplicité. C'est cadeau, c'est libre, et c'est ici :
    👉 sh-admin.blablalinux.be

  5. Well, the one issue with #Shlink is if you don't set Docker to restart the container, you lose everything.

    I hope that's the only problem.

    I have fixed that issue, but also exported the short URLs so I can have them for later in case there is a bigger failure down the line.

  6. Well, the one issue with #Shlink is if you don't set Docker to restart the container, you lose everything.

    I hope that's the only problem.

    I have fixed that issue, but also exported the short URLs so I can have them for later in case there is a bigger failure down the line.

  7. Well, the one issue with #Shlink is if you don't set Docker to restart the container, you lose everything.

    I hope that's the only problem.

    I have fixed that issue, but also exported the short URLs so I can have them for later in case there is a bigger failure down the line.

  8. Well, the one issue with #Shlink is if you don't set Docker to restart the container, you lose everything.

    I hope that's the only problem.

    I have fixed that issue, but also exported the short URLs so I can have them for later in case there is a bigger failure down the line.

  9. Well, the one issue with #Shlink is if you don't set Docker to restart the container, you lose everything.

    I hope that's the only problem.

    I have fixed that issue, but also exported the short URLs so I can have them for later in case there is a bigger failure down the line.

  10. So, another thing pissed me off and motivated me to move.

    #Rebrandly has decided to gate my access to my own URL shortening which I was only made aware of when trying to update majors.house/ttt to techtalkthursdays.net/.

    Finally moved over to #Shlink for more #SelfHosted goodness!

  11. So, another thing pissed me off and motivated me to move.

    #Rebrandly has decided to gate my access to my own URL shortening which I was only made aware of when trying to update majors.house/ttt to techtalkthursdays.net/.

    Finally moved over to #Shlink for more #SelfHosted goodness!

  12. So, another thing pissed me off and motivated me to move.

    #Rebrandly has decided to gate my access to my own URL shortening which I was only made aware of when trying to update majors.house/ttt to techtalkthursdays.net/.

    Finally moved over to #Shlink for more #SelfHosted goodness!

  13. So, another thing pissed me off and motivated me to move.

    #Rebrandly has decided to gate my access to my own URL shortening which I was only made aware of when trying to update majors.house/ttt to techtalkthursdays.net/.

    Finally moved over to #Shlink for more #SelfHosted goodness!

  14. So, another thing pissed me off and motivated me to move.

    #Rebrandly has decided to gate my access to my own URL shortening which I was only made aware of when trying to update majors.house/ttt to techtalkthursdays.net/.

    Finally moved over to #Shlink for more #SelfHosted goodness!

  15. My unofficial internal instance of stickybean, a pastebin software, has been suspended twice in two weeks.

    The first time, the support has recovered the service pretty quickly.

    The second time, they wanted me to call the billing service. But I'm off for two weeks. I guess the service will be removed permanently because it usually happens after one week.

    I'm doing this service only in my free time. I have warned everybody that may happen. And it's happening.

    The team that should host this service has changed over the years, with external people, with high turnover. I have a replacement service in my head. I've already written tutorials so they could easily deploy it themselves. But I've done it in the past and nothing happened. Maybe I'm not a great technical leader? I don't think so. It's just not worth it.

    The best bet is to deploy myself in our own namespace and tell them to update the CNAME.

    I plan to use PrivateBin this time. Eventually with an URL shortener like Shlink. There are third party clients working with a default setup but every service is behind a proxy adding an authentication layer so I may fork or get inspired by one of the clients and add this feature.

    Sounds fun right? Yes. Now I need to find time to do it, because as always, the business value of such change is so small, the priority is low, very low. Unless developers voice up because they were using the service.

    Anyway, I'm having time off and my kids need me. Bye 🌴😎

    #privatebin #shlink #collaboration #hosting #leadership

  16. My unofficial internal instance of stickybean, a pastebin software, has been suspended twice in two weeks.

    The first time, the support has recovered the service pretty quickly.

    The second time, they wanted me to call the billing service. But I'm off for two weeks. I guess the service will be removed permanently because it usually happens after one week.

    I'm doing this service only in my free time. I have warned everybody that may happen. And it's happening.

    The team that should host this service has changed over the years, with external people, with high turnover. I have a replacement service in my head. I've already written tutorials so they could easily deploy it themselves. But I've done it in the past and nothing happened. Maybe I'm not a great technical leader? I don't think so. It's just not worth it.

    The best bet is to deploy myself in our own namespace and tell them to update the CNAME.

    I plan to use PrivateBin this time. Eventually with an URL shortener like Shlink. There are third party clients working with a default setup but every service is behind a proxy adding an authentication layer so I may fork or get inspired by one of the clients and add this feature.

    Sounds fun right? Yes. Now I need to find time to do it, because as always, the business value of such change is so small, the priority is low, very low. Unless developers voice up because they were using the service.

    Anyway, I'm having time off and my kids need me. Bye 🌴😎

    #privatebin #shlink #collaboration #hosting #leadership

  17. My unofficial internal instance of stickybean, a pastebin software, has been suspended twice in two weeks.

    The first time, the support has recovered the service pretty quickly.

    The second time, they wanted me to call the billing service. But I'm off for two weeks. I guess the service will be removed permanently because it usually happens after one week.

    I'm doing this service only in my free time. I have warned everybody that may happen. And it's happening.

    The team that should host this service has changed over the years, with external people, with high turnover. I have a replacement service in my head. I've already written tutorials so they could easily deploy it themselves. But I've done it in the past and nothing happened. Maybe I'm not a great technical leader? I don't think so. It's just not worth it.

    The best bet is to deploy myself in our own namespace and tell them to update the CNAME.

    I plan to use PrivateBin this time. Eventually with an URL shortener like Shlink. There are third party clients working with a default setup but every service is behind a proxy adding an authentication layer so I may fork or get inspired by one of the clients and add this feature.

    Sounds fun right? Yes. Now I need to find time to do it, because as always, the business value of such change is so small, the priority is low, very low. Unless developers voice up because they were using the service.

    Anyway, I'm having time off and my kids need me. Bye 🌴😎

  18. My unofficial internal instance of stickybean, a pastebin software, has been suspended twice in two weeks.

    The first time, the support has recovered the service pretty quickly.

    The second time, they wanted me to call the billing service. But I'm off for two weeks. I guess the service will be removed permanently because it usually happens after one week.

    I'm doing this service only in my free time. I have warned everybody that may happen. And it's happening.

    The team that should host this service has changed over the years, with external people, with high turnover. I have a replacement service in my head. I've already written tutorials so they could easily deploy it themselves. But I've done it in the past and nothing happened. Maybe I'm not a great technical leader? I don't think so. It's just not worth it.

    The best bet is to deploy myself in our own namespace and tell them to update the CNAME.

    I plan to use PrivateBin this time. Eventually with an URL shortener like Shlink. There are third party clients working with a default setup but every service is behind a proxy adding an authentication layer so I may fork or get inspired by one of the clients and add this feature.

    Sounds fun right? Yes. Now I need to find time to do it, because as always, the business value of such change is so small, the priority is low, very low. Unless developers voice up because they were using the service.

    Anyway, I'm having time off and my kids need me. Bye 🌴😎

    #privatebin #shlink #collaboration #hosting #leadership

  19. My unofficial internal instance of stickybean, a pastebin software, has been suspended twice in two weeks.

    The first time, the support has recovered the service pretty quickly.

    The second time, they wanted me to call the billing service. But I'm off for two weeks. I guess the service will be removed permanently because it usually happens after one week.

    I'm doing this service only in my free time. I have warned everybody that may happen. And it's happening.

    The team that should host this service has changed over the years, with external people, with high turnover. I have a replacement service in my head. I've already written tutorials so they could easily deploy it themselves. But I've done it in the past and nothing happened. Maybe I'm not a great technical leader? I don't think so. It's just not worth it.

    The best bet is to deploy myself in our own namespace and tell them to update the CNAME.

    I plan to use PrivateBin this time. Eventually with an URL shortener like Shlink. There are third party clients working with a default setup but every service is behind a proxy adding an authentication layer so I may fork or get inspired by one of the clients and add this feature.

    Sounds fun right? Yes. Now I need to find time to do it, because as always, the business value of such change is so small, the priority is low, very low. Unless developers voice up because they were using the service.

    Anyway, I'm having time off and my kids need me. Bye 🌴😎

    #privatebin #shlink #collaboration #hosting #leadership

  20. Right now, I'm using #shlink to generate a unique URL for this purpose. So I publish a #joplin note, then put that URL into shlink, and give my person the shlink url. Then I can see if they clicked it or not. In theory, Joplin allows plugins and I could automate this workflow somehow but I have no idea how Joplin plugins actually work.
  21. Right now, I'm using #shlink to generate a unique URL for this purpose. So I publish a #joplin note, then put that URL into shlink, and give my person the shlink url. Then I can see if they clicked it or not. In theory, Joplin allows plugins and I could automate this workflow somehow but I have no idea how Joplin plugins actually work.
  22. Right now, I'm using #shlink to generate a unique URL for this purpose. So I publish a #joplin note, then put that URL into shlink, and give my person the shlink url. Then I can see if they clicked it or not. In theory, Joplin allows plugins and I could automate this workflow somehow but I have no idea how Joplin plugins actually work.
  23. Right now, I'm using #shlink to generate a unique URL for this purpose. So I publish a #joplin note, then put that URL into shlink, and give my person the shlink url. Then I can see if they clicked it or not. In theory, Joplin allows plugins and I could automate this workflow somehow but I have no idea how Joplin plugins actually work.
  24. Right now, I'm using #shlink to generate a unique URL for this purpose. So I publish a #joplin note, then put that URL into shlink, and give my person the shlink url. Then I can see if they clicked it or not. In theory, Joplin allows plugins and I could automate this workflow somehow but I have no idea how Joplin plugins actually work.
  25. Uy, me hace falta un acortador de enlaces para una cosa muy puntual... ¿Para que usar uno de por ahí pudiendo autoalojarme uno propio?

    *Tres horas después de pelearme con la instalación de docker de #Shlink*

    Ah ya, por eso.

  26. Uy, me hace falta un acortador de enlaces para una cosa muy puntual... ¿Para que usar uno de por ahí pudiendo autoalojarme uno propio?

    *Tres horas después de pelearme con la instalación de docker de #Shlink*

    Ah ya, por eso.

  27. Uy, me hace falta un acortador de enlaces para una cosa muy puntual... ¿Para que usar uno de por ahí pudiendo autoalojarme uno propio?

    *Tres horas después de pelearme con la instalación de docker de #Shlink*

    Ah ya, por eso.

  28. Uy, me hace falta un acortador de enlaces para una cosa muy puntual... ¿Para que usar uno de por ahí pudiendo autoalojarme uno propio?

    *Tres horas después de pelearme con la instalación de docker de #Shlink*

    Ah ya, por eso.

  29. Uy, me hace falta un acortador de enlaces para una cosa muy puntual... ¿Para que usar uno de por ahí pudiendo autoalojarme uno propio?

    *Tres horas después de pelearme con la instalación de docker de #Shlink*

    Ah ya, por eso.

  30. A year in retrospect:

    🚀 Released new major versions for Shlink and the web client.
    🔀 Implemented a rule-based dynamic redirects system.
    📉 Started (and paused) work on Shlink Dashboard.
    📈 Resumed work on Shlink Dashboard, to release early next year.
    🎉 Added support for 8.3 and 8.4

  31. A #Shlink year in retrospect:

    🚀 Released new major versions for Shlink and the web client.
    🔀 Implemented a rule-based dynamic redirects system.
    📉 Started (and paused) work on Shlink Dashboard.
    📈 Resumed work on Shlink Dashboard, to release early next year.
    🎉 Added support for #PHP 8.3 and 8.4

  32. A #Shlink year in retrospect:

    🚀 Released new major versions for Shlink and the web client.
    🔀 Implemented a rule-based dynamic redirects system.
    📉 Started (and paused) work on Shlink Dashboard.
    📈 Resumed work on Shlink Dashboard, to release early next year.
    🎉 Added support for #PHP 8.3 and 8.4

  33. A #Shlink year in retrospect:

    🚀 Released new major versions for Shlink and the web client.
    🔀 Implemented a rule-based dynamic redirects system.
    📉 Started (and paused) work on Shlink Dashboard.
    📈 Resumed work on Shlink Dashboard, to release early next year.
    🎉 Added support for #PHP 8.3 and 8.4

  34. I have lately been checking @Matomo as an alternative to Google analytics.

    This made me think, would you find it useful to have support sending visits stats to a instance?

  35. I have lately been checking @Matomo as an alternative to Google analytics.

    This made me think, would you find it useful to have #Shlink support sending visits stats to a #matomo instance?

  36. I have lately been checking @Matomo as an alternative to Google analytics.

    This made me think, would you find it useful to have #Shlink support sending visits stats to a #matomo instance?

  37. I have lately been checking @Matomo as an alternative to Google analytics.

    This made me think, would you find it useful to have #Shlink support sending visits stats to a #matomo instance?

  38. I have lately been checking @Matomo as an alternative to Google analytics.

    This made me think, would you find it useful to have #Shlink support sending visits stats to a #matomo instance?