#nightlybuild — Public Fediverse posts

I really like the idea of #ViewModes in Drupal. So I wrote a little #plugin for @getkirby to make use of this concept. It‘s based on content representations, literally a #nightlybuild and needs some more testing. Nevertheless I already published it …

https://github.com/flokosiol/kirby-viewmode

LibreCAD has no #DarkTheme native support yet, but latest #nightlybuild for #Linux got #Dark splash + #UI of some dialogs has been a bit cleaned up now: https://github.com/LibreCAD/LibreCAD/releases/tag/2.2.2_alpha-latest

Dark #theme support issue: https://github.com/LibreCAD/LibreCAD/issues/1144#issuecomment-2307104652

📑 #Tutorial How To Make LibreCAD's PDF Interactive
☕ https://buymeacoffee.com/app4soft/how-to-make-librecad-pdf-interactive
:patreon: https://www.patreon.com/posts/how-to-make-pdf-110453183?utm_campaign=postshare_creator&utm_content=join_link

🤝 Thanks for buying me a coffee & becoming my Patron!

#2d #3d #cad #cam #librecad #freecad #b3d #blender #blender3d #scribus #drawing #drafting #draft #draw

LibreCAD has no #DarkTheme native support yet, but latest #nightlybuild for #Linux got #Dark splash + #UI of some dialogs has been a bit cleaned up now: https://github.com/LibreCAD/LibreCAD/releases/tag/2.2.2_alpha-latest

Dark #theme support issue: https://github.com/LibreCAD/LibreCAD/issues/1144#issuecomment-2307104652

📑 #Tutorial How To Make LibreCAD's PDF Interactive
☕ https://buymeacoffee.com/app4soft/how-to-make-librecad-pdf-interactive
:patreon: https://www.patreon.com/posts/how-to-make-pdf-110453183?utm_campaign=postshare_creator&utm_content=join_link

🤝 Thanks for buying me a coffee & becoming my Patron!

#2d #3d #cad #cam #librecad #freecad #b3d #blender #blender3d #scribus #drawing #drafting #draft #draw

LibreCAD has no #DarkTheme native support yet, but latest #nightlybuild for #Linux got #Dark splash + #UI of some dialogs has been a bit cleaned up now: https://github.com/LibreCAD/LibreCAD/releases/tag/2.2.2_alpha-latest

Dark #theme support issue: https://github.com/LibreCAD/LibreCAD/issues/1144#issuecomment-2307104652

📑 #Tutorial How To Make LibreCAD's PDF Interactive
☕ https://buymeacoffee.com/app4soft/how-to-make-librecad-pdf-interactive
:patreon: https://www.patreon.com/posts/how-to-make-pdf-110453183?utm_campaign=postshare_creator&utm_content=join_link

🤝 Thanks for buying me a coffee & becoming my Patron!

#2d #3d #cad #cam #librecad #freecad #b3d #blender #blender3d #scribus #drawing #drafting #draft #draw

LibreCAD has no #DarkTheme native support yet, but latest #nightlybuild for #Linux got #Dark splash + #UI of some dialogs has been a bit cleaned up now: https://github.com/LibreCAD/LibreCAD/releases/tag/2.2.2_alpha-latest

Dark #theme support issue: https://github.com/LibreCAD/LibreCAD/issues/1144#issuecomment-2307104652

📑 #Tutorial How To Make LibreCAD's PDF Interactive
☕ https://buymeacoffee.com/app4soft/how-to-make-librecad-pdf-interactive
:patreon: https://www.patreon.com/posts/how-to-make-pdf-110453183?utm_campaign=postshare_creator&utm_content=join_link

🤝 Thanks for buying me a coffee & becoming my Patron!

#2d #3d #cad #cam #librecad #freecad #b3d #blender #blender3d #scribus #drawing #drafting #draft #draw

Reading Time: 2 minutesTable of Contents

1. Mastodon and Firefish
2. A change in tact
3. ClassicPress and WordPress Are Viable Options
4. Sub-Domains count

After my first post about playing with ClassicPress and the Fediverse it was suggested that I try the nightly build of ClassicPress so I did. The result can be seen here.

Mastodon and Firefish

I have tested integration with the fediverse via Mastodon.social but also firefish.social and mastodon.social is faster, but mastodon.social eventually catches up. I tried posting a blog post, and commenting on blog posts and it works although not instantly. You need to wait for the changes to be propagated to where they are needed.

A change in tact

Initially I was going to try using a different domain but I struggled with getting the SSL certificates to work so I decided to create the subdomain ClassicPress.main-vision.com for ClassicPress tests and blog.main-vision.com for WordPress. In the case of ClassicPress I wanted to be able to play around, without making too much noise with my daily blog.

With the WordPress blog I wanted to test whether the webfinger json file for individual users would work, and it does, at least partially. When I looked up the usernames on webfinger it did show the users, but mastodon and Firefish do not detect them.

ClassicPress and WordPress Are Viable Options

I spent most of yesterday playing around with the two, and seeing if ideas worked, and so far the answer is "yes, if you're patient" but that's because the idea is still relatively new so progress has to be made. WordPress does work well, and ClassicPress is close behind. If you write a post, and check for comments the next day, then it works fine.

Sub-Domains count

The other question was whether it had to be example.com or whether subdomain.example.com would work and the answer is that subdomains work. If your blog instance is two or three subdirectories deep, then subdomains are a good alternative to manually generating webfinger files.

#classicpress-2 #experimenting #fediverse #firefish #mastodon #nightlybuild

https://www.main-vision.com/richard/blog/classicpress-and-the-fediverse-part-deux/

Reading Time: 2 minutes

After my first post about playing with ClassicPress and the Fediverse it was suggested that I try the nightly build of ClassicPress so I did. The result can be seen here.

Mastodon and Firefish

I have tested integration with the fediverse via Mastodon.social but also firefish.social and mastodon.social is faster, but mastodon.social eventually catches up. I tried posting a blog post, and commenting on blog posts and it works although not instantly. You need to wait for the changes to be propagated to where they are needed.

A change in tact

Initially I was going to try using a different domain but I struggled with getting the SSL certificates to work so I decided to create the subdomain ClassicPress.main-vision.com for ClassicPress tests and blog.main-vision.com for WordPress. In the case of ClassicPress I wanted to be able to play around, without making too much noise with my daily blog.

With the WordPress blog I wanted to test whether the webfinger json file for individual users would work, and it does, at least partially. When I looked up the usernames on webfinger it did show the users, but mastodon and Firefish do not detect them.

ClassicPress and WordPress Are Viable Options

I spent most of yesterday playing around with the two, and seeing if ideas worked, and so far the answer is "yes, if you're patient" but that's because the idea is still relatively new so progress has to be made. WordPress does work well, and ClassicPress is close behind. If you write a post, and check for comments the next day, then it works fine.

Sub-Domains count

The other question was whether it had to be example.com or whether subdomain.example.com would work and the answer is that subdomains work. If your blog instance is two or three subdirectories deep, then subdomains are a good alternative to manually generating webfinger files.

#classicpress-2 #experimenting #fediverse #firefish #mastodon #nightlybuild

https://www.main-vision.com/richard/blog/classicpress-and-the-fediverse-part-deux/

Reading Time: 2 minutesTable of Contents

1. Mastodon and Firefish
2. A change in tact
3. ClassicPress and WordPress Are Viable Options
4. Sub-Domains count

After my first post about playing with ClassicPress and the Fediverse it was suggested that I try the nightly build of ClassicPress so I did. The result can be seen here.

Mastodon and Firefish

I have tested integration with the fediverse via Mastodon.social but also firefish.social and mastodon.social is faster, but mastodon.social eventually catches up. I tried posting a blog post, and commenting on blog posts and it works although not instantly. You need to wait for the changes to be propagated to where they are needed.

A change in tact

Initially I was going to try using a different domain but I struggled with getting the SSL certificates to work so I decided to create the subdomain ClassicPress.main-vision.com for ClassicPress tests and blog.main-vision.com for WordPress. In the case of ClassicPress I wanted to be able to play around, without making too much noise with my daily blog.

With the WordPress blog I wanted to test whether the webfinger json file for individual users would work, and it does, at least partially. When I looked up the usernames on webfinger it did show the users, but mastodon and Firefish do not detect them.

ClassicPress and WordPress Are Viable Options

I spent most of yesterday playing around with the two, and seeing if ideas worked, and so far the answer is "yes, if you're patient" but that's because the idea is still relatively new so progress has to be made. WordPress does work well, and ClassicPress is close behind. If you write a post, and check for comments the next day, then it works fine.

Sub-Domains count

The other question was whether it had to be example.com or whether subdomain.example.com would work and the answer is that subdomains work. If your blog instance is two or three subdirectories deep, then subdomains are a good alternative to manually generating webfinger files.

#classicpress-2 #experimenting #fediverse #firefish #mastodon #nightlybuild

https://www.main-vision.com/richard/blog/classicpress-and-the-fediverse-part-deux/

Reading Time: 2 minutes

After my first post about playing with ClassicPress and the Fediverse it was suggested that I try the nightly build of ClassicPress so I did. The result can be seen here.

Mastodon and Firefish

I have tested integration with the fediverse via Mastodon.social but also firefish.social and mastodon.social is faster, but mastodon.social eventually catches up. I tried posting a blog post, and commenting on blog posts and it works although not instantly. You need to wait for the changes to be propagated to where they are needed.

A change in tact

Initially I was going to try using a different domain but I struggled with getting the SSL certificates to work so I decided to create the subdomain ClassicPress.main-vision.com for ClassicPress tests and blog.main-vision.com for WordPress. In the case of ClassicPress I wanted to be able to play around, without making too much noise with my daily blog.

With the WordPress blog I wanted to test whether the webfinger json file for individual users would work, and it does, at least partially. When I looked up the usernames on webfinger it did show the users, but mastodon and Firefish do not detect them.

ClassicPress and WordPress Are Viable Options

I spent most of yesterday playing around with the two, and seeing if ideas worked, and so far the answer is "yes, if you're patient" but that's because the idea is still relatively new so progress has to be made. WordPress does work well, and ClassicPress is close behind. If you write a post, and check for comments the next day, then it works fine.

Sub-Domains count

The other question was whether it had to be example.com or whether subdomain.example.com would work and the answer is that subdomains work. If your blog instance is two or three subdirectories deep, then subdomains are a good alternative to manually generating webfinger files.

#classicpress-2 #experimenting #fediverse #firefish #mastodon #nightlybuild

https://www.main-vision.com/richard/blog/classicpress-and-the-fediverse-part-deux/

Reading Time: 2 minutes

After my first post about playing with ClassicPress and the Fediverse it was suggested that I try the nightly build of ClassicPress so I did. The result can be seen here.

Mastodon and Firefish

I have tested integration with the fediverse via Mastodon.social but also firefish.social and mastodon.social is faster, but mastodon.social eventually catches up. I tried posting a blog post, and commenting on blog posts and it works although not instantly. You need to wait for the changes to be propagated to where they are needed.

A change in tact

Initially I was going to try using a different domain but I struggled with getting the SSL certificates to work so I decided to create the subdomain ClassicPress.main-vision.com for ClassicPress tests and blog.main-vision.com for WordPress. In the case of ClassicPress I wanted to be able to play around, without making too much noise with my daily blog.

With the WordPress blog I wanted to test whether the webfinger json file for individual users would work, and it does, at least partially. When I looked up the usernames on webfinger it did show the users, but mastodon and Firefish do not detect them.

ClassicPress and WordPress Are Viable Options

I spent most of yesterday playing around with the two, and seeing if ideas worked, and so far the answer is "yes, if you're patient" but that's because the idea is still relatively new so progress has to be made. WordPress does work well, and ClassicPress is close behind. If you write a post, and check for comments the next day, then it works fine.

Sub-Domains count

The other question was whether it had to be example.com or whether subdomain.example.com would work and the answer is that subdomains work. If your blog instance is two or three subdirectories deep, then subdomains are a good alternative to manually generating webfinger files.

#classicpress-2 #experimenting #fediverse #firefish #mastodon #nightlybuild

https://www.main-vision.com/richard/blog/classicpress-and-the-fediverse-part-deux/

Also have this bonus timelapse of the #NightlyBuild (~70x speed to fit in the time limit of Twitter)
[Better video quality than the other toot]

Also have this bonus timelapse of the #NightlyBuild (~70x speed to fit in the time limit of Twitter)

I did a quick #NightlyBuild today and migrated the previous flying leads construction of my ESP32 CO₂ sensor onto a perfboard.
I also added a 24V PWM output to control a radial-flow fan I mounted below my radiator to increase its heating performance.

I did a quick #NightlyBuild today and migrated the previous flying leads construction of my ESP32 CO₂ sensor onto a perfboard.
I also added a 24V PWM output to control a radial-flow fan I mounted below my radiator to increase its heating performance.

I did a quick #NightlyBuild today and migrated the previous flying leads construction of my ESP32 CO₂ sensor onto a perfboard.
I also added a 24V PWM output to control a radial-flow fan I mounted below my radiator to increase its heating performance.

4 years ago I saw @aral speak at a tiny "after work conference" called #NightlyBuild in Cologne, Germany.

He talked about #IndieWeb and how decentralised systems are the future. Back then I had not much fate into these technologies and I was very wrong.

I believe 100% that the next step in the evolution of the web is decentralized.