home.social

#how-to — Public Fediverse posts

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

fetched live
  1. 💁🏻‍♀️ NEW: 🎨🪵 French artist Paul Gauguin experimented with unconventional #woodblock and monotype printmaking techniques, scratching fine lines and layering #colors to create intricate visual effects. These demonstrations from The #Art Institute of #Chicago show how he carved, inked, and printed these unique works.

    👉 Learn more: seethis.tv/post/gauguins-proce

    #1880s #1890s #19thcentury #activities #arthistory #carving #diy #engraving #frenchpolynesia #history #howto #ink #island #paint #paper #printing #tahiti #tools #wood #tksst #video

  2. 💁🏻‍♀️ NEW: 🎨🪵 French artist Paul Gauguin experimented with unconventional #woodblock and monotype printmaking techniques, scratching fine lines and layering #colors to create intricate visual effects. These demonstrations from The #Art Institute of #Chicago show how he carved, inked, and printed these unique works.

    👉 Learn more: seethis.tv/post/gauguins-proce

    #1880s #1890s #19thcentury #activities #arthistory #carving #diy #engraving #frenchpolynesia #history #howto #ink #island #paint #paper #printing #tahiti #tools #wood #tksst #video

  3. 💁🏻‍♀️ NEW: 🎨🪵 French artist Paul Gauguin experimented with unconventional #woodblock and monotype printmaking techniques, scratching fine lines and layering #colors to create intricate visual effects. These demonstrations from The #Art Institute of #Chicago show how he carved, inked, and printed these unique works.

    👉 Learn more: seethis.tv/post/gauguins-proce

    #1880s #1890s #19thcentury #activities #arthistory #carving #diy #engraving #frenchpolynesia #history #howto #ink #island #paint #paper #printing #tahiti #tools #wood #tksst #video

  4. 💁🏻‍♀️ NEW: 🎨🪵 French artist Paul Gauguin experimented with unconventional #woodblock and monotype printmaking techniques, scratching fine lines and layering #colors to create intricate visual effects. These demonstrations from The #Art Institute of #Chicago show how he carved, inked, and printed these unique works.

    👉 Learn more: seethis.tv/post/gauguins-proce

    #1880s #1890s #19thcentury #activities #arthistory #carving #diy #engraving #frenchpolynesia #history #howto #ink #island #paint #paper #printing #tahiti #tools #wood #tksst #video

  5. 💁🏻‍♀️ NEW: 🎨🪵 French artist Paul Gauguin experimented with unconventional #woodblock and monotype printmaking techniques, scratching fine lines and layering #colors to create intricate visual effects. These demonstrations from The #Art Institute of #Chicago show how he carved, inked, and printed these unique works.

    👉 Learn more: seethis.tv/post/gauguins-proce

    #1880s #1890s #19thcentury #activities #arthistory #carving #diy #engraving #frenchpolynesia #history #howto #ink #island #paint #paper #printing #tahiti #tools #wood #tksst #video

  6. Let’s Draw ZUCCHINI! 🌱 (The Zucchini Way)

    WORK IN PROGRESS = Part of a top-secret NH history project...

    marekbennett.com/2026/07/27/le

  7. Let’s Draw ZUCCHINI! 🌱 (The Zucchini Way)

    WORK IN PROGRESS = Part of a top-secret NH history project...

    marekbennett.com/2026/07/27/le

  8. Let’s Draw ZUCCHINI! 🌱 (The Zucchini Way)

    WORK IN PROGRESS = Part of a top-secret NH history project...

    marekbennett.com/2026/07/27/le

  9. Let’s Draw ZUCCHINI! 🌱 (The Zucchini Way)

    WORK IN PROGRESS = Part of a top-secret NH history project...

    marekbennett.com/2026/07/27/le

  10. Let’s Draw ZUCCHINI! 🌱 (The Zucchini Way)

    WORK IN PROGRESS = Part of a top-secret NH history project...

    marekbennett.com/2026/07/27/le

  11. @dillo

    Apologies! No sooner had I published, I realized that #Dillo, which was actually on the list, wasn't included in my tut.... Grrrrr!

    So, this particular article wasn't published with the intention of being as ephemeral as a regular, standard #FediPost, but rather, as a cookbook style #HowTo to update occasionally and keeping it rather current.

    I'm also considering expanding it with sections for other #Unices & Distros, with each one of the #browsers included again, but in the section for the particular #OS - whether it be #OpenBSD, #Slackware, Etc., and I've been doing a little work on that already.

    Anyway, it's almost inconceivable that I published w/o Dillo. I was very tired when I did, and I recall thinking about Dillo when I writing up #Lagrange, since I've always believed that it's a sin to remove such tiny amounts of code to accommodate (Yes I'm talking to you Mozilla!) Gopher:// ftp://, Etc.; and for the more forward thinking folks, extending similar support for gemini:// and arguably others spawned from it that I didn't personally work with since the very beginning like I did with #Gemini, back at #SDF).

    But I digress, and I'll get to the point.

    Here is the update of my Linux Browser HowTo, Which includes dillo*. It was much too long to include by just appending to the original article by about 5000 characters,lolz, so I took the easy way out - I quote-posted it, lolz

    That also implies that I'll have to swap hats a couple of times because some forums forced me to completely rewrite it to support #BBCode, and although the original looks nice in HIVE and on Dev, the Markdown is completely obliterated on Nostr (no graceful degradation there folks) - which I left as is because I think people need to see what not supporting Markdown looks like. I think it looks like shit on masto too, but masto isn't the #Fediverse, and it looks great on most other Fediverse platforms :)

    I was getting tired again, but rushing to publish, so I know I misspelled various incarnations of privilege at least 3 different ways, and no, I'm not going to clean that up :p What I think I'm going to have to do though, Is publish the next volume on a proper website with some ActivityPub powered capabilities like WordPress, or Ghost, or WriteFreely / write.as, where I don't have to worry about the length of the article and I can continue to break it into pieces or chapters, etc., as it grows. There's other OSes and Linux distros I'd like to cover, but as you can see at the end, Slackware is going to be rather boring, considering how simple it is to install everything under the sun from source - and that is indeed a beautiful thing.

    I hope what I've done today facilitates more people having access to dillo, since it's a good product, but seemingly out of reach for many n00bs, when it really doesn't need to be. Sure, setting up a Debian style repo with keys, etc., at Dillo-Browser.org would be ideal, but this is, after all, FOSS, and you've done so much already, maybe I can lend a hand at that at some point in the future, but....

    Truth be told, there really isn't anything much simpler than doing a git clone to perform the initial installation, and simply performing a git pull, followed by the same build sequence later to affect any updates.

    You have a wonderful day, and I hope I've helped bring some awareness and hopefully adoption by others of dillo, it really is deserving of that, much moreso than Microsoft Edge, which I also included in my HowTo (but mostly as a disparaging joke).

    Kindest regards,

    Bradley

    #tallship #tut #HowTo #Browser_HowTo #dillo #FOSS

  12. @dillo

    Apologies! No sooner had I published, I realized that #Dillo, which was actually on the list, wasn't included in my tut.... Grrrrr!

    So, this particular article wasn't published with the intention of being as ephemeral as a regular, standard #FediPost, but rather, as a cookbook style #HowTo to update occasionally and keeping it rather current.

    I'm also considering expanding it with sections for other #Unices & Distros, with each one of the #browsers included again, but in the section for the particular #OS - whether it be #OpenBSD, #Slackware, Etc., and I've been doing a little work on that already.

    Anyway, it's almost inconceivable that I published w/o Dillo. I was very tired when I did, and I recall thinking about Dillo when I writing up #Lagrange, since I've always believed that it's a sin to remove such tiny amounts of code to accommodate (Yes I'm talking to you Mozilla!) Gopher:// ftp://, Etc.; and for the more forward thinking folks, extending similar support for gemini:// and arguably others spawned from it that I didn't personally work with since the very beginning like I did with #Gemini, back at #SDF).

    But I digress, and I'll get to the point.

    Here is the update of my Linux Browser HowTo, Which includes dillo*. It was much too long to include by just appending to the original article by about 5000 characters,lolz, so I took the easy way out - I quote-posted it, lolz

    That also implies that I'll have to swap hats a couple of times because some forums forced me to completely rewrite it to support #BBCode, and although the original looks nice in HIVE and on Dev, the Markdown is completely obliterated on Nostr (no graceful degradation there folks) - which I left as is because I think people need to see what not supporting Markdown looks like. I think it looks like shit on masto too, but masto isn't the #Fediverse, and it looks great on most other Fediverse platforms :)

    I was getting tired again, but rushing to publish, so I know I misspelled various incarnations of privilege at least 3 different ways, and no, I'm not going to clean that up :p What I think I'm going to have to do though, Is publish the next volume on a proper website with some ActivityPub powered capabilities like WordPress, or Ghost, or WriteFreely / write.as, where I don't have to worry about the length of the article and I can continue to break it into pieces or chapters, etc., as it grows. There's other OSes and Linux distros I'd like to cover, but as you can see at the end, Slackware is going to be rather boring, considering how simple it is to install everything under the sun from source - and that is indeed a beautiful thing.

    I hope what I've done today facilitates more people having access to dillo, since it's a good product, but seemingly out of reach for many n00bs, when it really doesn't need to be. Sure, setting up a Debian style repo with keys, etc., at Dillo-Browser.org would be ideal, but this is, after all, FOSS, and you've done so much already, maybe I can lend a hand at that at some point in the future, but....

    Truth be told, there really isn't anything much simpler than doing a git clone to perform the initial installation, and simply performing a git pull, followed by the same build sequence later to affect any updates.

    You have a wonderful day, and I hope I've helped bring some awareness and hopefully adoption by others of dillo, it really is deserving of that, much moreso than Microsoft Edge, which I also included in my HowTo (but mostly as a disparaging joke).

    Kindest regards,

    Bradley

    #tallship #tut #HowTo #Browser_HowTo #dillo #FOSS

  13. @dillo

    Apologies! No sooner had I published, I realized that #Dillo, which was actually on the list, wasn't included in my tut.... Grrrrr!

    So, this particular article wasn't published with the intention of being as ephemeral as a regular, standard #FediPost, but rather, as a cookbook style #HowTo to update occasionally and keeping it rather current.

    I'm also considering expanding it with sections for other #Unices & Distros, with each one of the #browsers included again, but in the section for the particular #OS - whether it be #OpenBSD, #Slackware, Etc., and I've been doing a little work on that already.

    Anyway, it's almost inconceivable that I published w/o Dillo. I was very tired when I did, and I recall thinking about Dillo when I writing up #Lagrange, since I've always believed that it's a sin to remove such tiny amounts of code to accommodate (Yes I'm talking to you Mozilla!) Gopher:// ftp://, Etc.; and for the more forward thinking folks, extending similar support for gemini:// and arguably others spawned from it that I didn't personally work with since the very beginning like I did with #Gemini, back at #SDF).

    But I digress, and I'll get to the point.

    Here is the update of my Linux Browser HowTo, Which includes dillo*. It was much too long to include by just appending to the original article by about 5000 characters,lolz, so I took the easy way out - I quote-posted it, lolz

    That also implies that I'll have to swap hats a couple of times because some forums forced me to completely rewrite it to support #BBCode, and although the original looks nice in HIVE and on Dev, the Markdown is completely obliterated on Nostr (no graceful degradation there folks) - which I left as is because I think people need to see what not supporting Markdown looks like. I think it looks like shit on masto too, but masto isn't the #Fediverse, and it looks great on most other Fediverse platforms :)

    I was getting tired again, but rushing to publish, so I know I misspelled various incarnations of privilege at least 3 different ways, and no, I'm not going to clean that up :p What I think I'm going to have to do though, Is publish the next volume on a proper website with some ActivityPub powered capabilities like WordPress, or Ghost, or WriteFreely / write.as, where I don't have to worry about the length of the article and I can continue to break it into pieces or chapters, etc., as it grows. There's other OSes and Linux distros I'd like to cover, but as you can see at the end, Slackware is going to be rather boring, considering how simple it is to install everything under the sun from source - and that is indeed a beautiful thing.

    I hope what I've done today facilitates more people having access to dillo, since it's a good product, but seemingly out of reach for many n00bs, when it really doesn't need to be. Sure, setting up a Debian style repo with keys, etc., at Dillo-Browser.org would be ideal, but this is, after all, FOSS, and you've done so much already, maybe I can lend a hand at that at some point in the future, but....

    Truth be told, there really isn't anything much simpler than doing a git clone to perform the initial installation, and simply performing a git pull, followed by the same build sequence later to affect any updates.

    You have a wonderful day, and I hope I've helped bring some awareness and hopefully adoption by others of dillo, it really is deserving of that, much moreso than Microsoft Edge, which I also included in my HowTo (but mostly as a disparaging joke).

    Kindest regards,

    Bradley

    #tallship #tut #HowTo #Browser_HowTo #dillo #FOSS

  14. Learn #howto replace nonfree #BIOS / #UEFI demo & training with the #Zerocat #Chipflasher

    Dim. 2 aout '26 13h-19h
    #April, 44-46 rue de l'Ouest

    The event will be held in English, but people who speak both English and French and are knowledgeable of the topics will be there for explanations about the Chipflasher from Zerocat as its designer will be there.

    Please take a look at the program :
    agendadulibre.org/events/35521

    #gnuboot #asus #kgped16 #thinkpad #t400 #x230 #freesoftware #gnulinux #guix

  15. Learn #howto replace nonfree #BIOS / #UEFI demo & training with the #Zerocat #Chipflasher

    Dim. 2 aout '26 13h-19h
    #April, 44-46 rue de l'Ouest

    The event will be held in English, but people who speak both English and French and are knowledgeable of the topics will be there for explanations about the Chipflasher from Zerocat as its designer will be there.

    Please take a look at the program :
    agendadulibre.org/events/35521

    #gnuboot #asus #kgped16 #thinkpad #t400 #x230 #freesoftware #gnulinux #guix

  16. Learn #howto replace nonfree #BIOS / #UEFI demo & training with the #Zerocat #Chipflasher

    Dim. 2 aout '26 13h-19h
    #April, 44-46 rue de l'Ouest

    The event will be held in English, but people who speak both English and French and are knowledgeable of the topics will be there for explanations about the Chipflasher from Zerocat as its designer will be there.

    Please take a look at the program :
    agendadulibre.org/events/35521

    #gnuboot #asus #kgped16 #thinkpad #t400 #x230 #freesoftware #gnulinux #guix

  17. Learn #howto replace nonfree #BIOS / #UEFI demo & training with the #Zerocat #Chipflasher

    Dim. 2 aout '26 13h-19h
    #April, 44-46 rue de l'Ouest

    The event will be held in English, but people who speak both English and French and are knowledgeable of the topics will be there for explanations about the Chipflasher from Zerocat as its designer will be there.

    Please take a look at the program :
    agendadulibre.org/events/35521

    #gnuboot #asus #kgped16 #thinkpad #t400 #x230 #freesoftware #gnulinux #guix

  18. Learn #howto replace nonfree #BIOS / #UEFI demo & training with the #Zerocat #Chipflasher

    Dim. 2 aout '26 13h-19h
    #April, 44-46 rue de l'Ouest

    The event will be held in English, but people who speak both English and French and are knowledgeable of the topics will be there for explanations about the Chipflasher from Zerocat as its designer will be there.

    Please take a look at the program :
    agendadulibre.org/events/35521

    #gnuboot #asus #kgped16 #thinkpad #t400 #x230 #freesoftware #gnulinux #guix

  19. Build your own audio37 in 3 steps:

    1. Install Fish Audio S2 with UV
    2. Build a CLI wrapper for any provider
    3. Add voice cloning via custom_voices

    audio37 orchestrates it all.

    youtu.be/47rOVbW2rHw

    #AI #howto #buildinginpublic

  20. Build your own audio37 in 3 steps:

    1. Install Fish Audio S2 with UV
    2. Build a CLI wrapper for any provider
    3. Add voice cloning via custom_voices

    audio37 orchestrates it all.

    youtu.be/47rOVbW2rHw

    #AI #howto #buildinginpublic

  21. Build your own audio37 in 3 steps:

    1. Install Fish Audio S2 with UV
    2. Build a CLI wrapper for any provider
    3. Add voice cloning via custom_voices

    audio37 orchestrates it all.

    youtu.be/47rOVbW2rHw

    #AI #howto #buildinginpublic

  22. Build your own audio37 in 3 steps:

    1. Install Fish Audio S2 with UV
    2. Build a CLI wrapper for any provider
    3. Add voice cloning via custom_voices

    audio37 orchestrates it all.

    youtu.be/47rOVbW2rHw

    #AI #howto #buildinginpublic

  23. Build your own audio37 in 3 steps:

    1. Install Fish Audio S2 with UV
    2. Build a CLI wrapper for any provider
    3. Add voice cloning via custom_voices

    audio37 orchestrates it all.

    youtu.be/47rOVbW2rHw

    #AI #howto #buildinginpublic

  24. Fail2ban su Linux: come configurarlo per bloccare davvero gli attacchi brute-force

    Guida pratica a Fail2ban: installazione, jail per SSH e Nginx, integrazione con nftables e firewalld, ban persistenti e configurazione di partenza pronta per la produzione.

    spcnet.it/fail2ban-su-linux-co

  25. Next, enter through the front doors of the building.

    #PyOhio #HowTo PyOhio

  26. Next, enter through the front doors of the building.

    PyOhio

  27. Next, enter through the front doors of the building.

    #PyOhio #HowTo PyOhio

  28. Next, enter through the front doors of the building.

    #PyOhio #HowTo PyOhio

  29. Next, enter through the front doors of the building.

    #PyOhio #HowTo PyOhio

  30. Bitte, wenn ihr euren ALT-Text von KI schreiben lasst, verlangt einen kurzen Text ohne Interpretation. Mehr brauchen und wollen diejenigen nicht, die auf Screenreader angewiesen sind.

    #FotoVorschlag #HowTo

    6/6

  31. Bitte, wenn ihr euren ALT-Text von KI schreiben lasst, verlangt einen kurzen Text ohne Interpretation. Mehr brauchen und wollen diejenigen nicht, die auf Screenreader angewiesen sind.

    #FotoVorschlag #HowTo

    6/6

  32. Bitte, wenn ihr euren ALT-Text von KI schreiben lasst, verlangt einen kurzen Text ohne Interpretation. Mehr brauchen und wollen diejenigen nicht, die auf Screenreader angewiesen sind.

    #FotoVorschlag #HowTo

    6/6

  33. Bitte, wenn ihr euren ALT-Text von KI schreiben lasst, verlangt einen kurzen Text ohne Interpretation. Mehr brauchen und wollen diejenigen nicht, die auf Screenreader angewiesen sind.

    #FotoVorschlag #HowTo

    6/6

  34. Bitte, wenn ihr euren ALT-Text von KI schreiben lasst, verlangt einen kurzen Text ohne Interpretation. Mehr brauchen und wollen diejenigen nicht, die auf Screenreader angewiesen sind.

    #FotoVorschlag #HowTo

    6/6

  35. goldenen Verzierungen, der der Installation einen dekorativen, fast sakralen Rahmen gibt. Die Perspektive von unten verstärkt die monumentale Wirkung des Gewölbes und lässt es wie einen funkelnden, blauen Himmel aus Glas wirken."

    #FotoVorschlag #HowTo

    5/6

  36. Installation wie ein heller Saum ein. Die Beleuchtung von oben lässt das blaue Glas leuchten und erzeugt leichte Farbnuancen von tiefem Ultramarin bis zu helleren Türkistönen an einzelnen Stellen.

    Der unterste Rand zeigt zudem einen dunkelblau gefliesten Abschluss mit

    #FotoVorschlag #HowTo

    4/6

  37. Deckenkonstruktion, die aus zahlreichen aufgehängten Flaschen besteht. Der Großteil des Gewölbes wird von tausenden blauen Glasflaschen dominiert, die in konzentrischen Reihen angeordnet sind und ein wellenförmiges, fast organisches Muster erzeugen. Die Flaschen sind mit

    #FotoVorschlag #HowTo

    2/6

  38. So sollten ALT-Texte nicht aussehen, das ist (KI erzeugter?) Ohrenmüll.

    Viele Informationen sind doppelt. Interpretationen, Stimmungen, werden im ALT nicht gebraucht. Verschwendete Zeichen, verschwendete Zeit.

    "Das Foto zeigt eine beeindruckende, nach oben fotografierte

    #FotoVorschlag #HowTo

    1/6

  39. dem Hals nach unten montiert, sodass ihre runden Böden nach oben zeigen und ein rhythmisches, schuppenartiges Relief bilden.

    Im unteren Bildbereich bildet ein Streifen aus weißen oder hellen Flaschen einen klaren Kontrast zum übrigen blauen Feld und rahmt die

    #FotoVorschlag #HowTo

    3/6