Mastouille

1 message1 participant0 message aujourd’hui

NatyTime to make a move? <a href="https://fosstodon.org/tags/GiveUpGitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GiveUpGitHub</a> My new blog post is just out <a href="https://fosstodon.org/tags/BurgeonLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BurgeonLab</a>➡️ <a href="https://www.burgeonlab.com/blog/migrate-github-pages-to-sourcehut-bunny/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.burgeonlab.com/blog/migrate-github-pages-to-sourcehut-bunny/</a>It's a thorough guide of switching from an automated CI static site deployment workflow using GitHub Pages & GitHub Actions 🔄 to SourceHut Git and Builds + hosting on Bunny.net Storage & Bunny CDN.<a href="https://fosstodon.org/tags/techguides" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#techguides</a> <a href="https://fosstodon.org/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a> <a href="https://fosstodon.org/tags/blogging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blogging</a> <a href="https://fosstodon.org/tags/blogpost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blogpost</a> <a href="https://fosstodon.org/tags/hugo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hugo</a> <a href="https://fosstodon.org/tags/cicd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cicd</a> <a href="https://fosstodon.org/tags/CDN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CDN</a> <a href="https://fosstodon.org/tags/bunnycdn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bunnycdn</a> <a href="https://fosstodon.org/tags/bunnynet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bunnynet</a> <a href="https://fosstodon.org/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> <a href="https://fosstodon.org/tags/sourcehut" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sourcehut</a> <a href="https://fosstodon.org/tags/githubactions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubactions</a> <a href="https://fosstodon.org/tags/githubpages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubpages</a> <a href="https://fosstodon.org/tags/srht" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#srht</a>

Alexandre B A Villares 🐍<a href="https://ciberlandia.pt/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://ciberlandia.pt/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a> <a href="https://ciberlandia.pt/tags/fail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fail</a> This is driving me mad...Images randomly deciding not to load on all my pages.Is it just me? Is it my browser's fault? Is it just in Brazil?I was working on this <a href="https://ciberlandia.pt/tags/shapely" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#shapely</a> + <a href="https://ciberlandia.pt/tags/trimesh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#trimesh</a> page... and I can only see the last image (the animated gif)! <a href="https://abav.lugaralgum.com/material-aulas/Processing-Python-py5/shapely-e-trimesh.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://abav.lugaralgum.com/material-aulas/Processing-Python-py5/shapely-e-trimesh.html</a>

xoron :verified:File encryption with a browser.I've been exploring the <a href="https://infosec.exchange/tags/WebCryptoAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebCryptoAPI</a> and I'm impressed!When combined with the <a href="https://infosec.exchange/tags/FileSystemAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FileSystemAPI</a>, it offers a seemingly secure way to <a href="https://infosec.exchange/tags/encrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encrypt</a> and <a href="https://infosec.exchange/tags/store" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#store</a> files directly on your device. Think <a href="https://infosec.exchange/tags/localstorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#localstorage</a>, but with <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a>!I know <a href="https://infosec.exchange/tags/webapps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webapps</a> can have <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> vulnerabilities since the code is served over the web, so I've <a href="https://infosec.exchange/tags/OpenSourced" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSourced</a> my demo! You can check it out, and it should even work if <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a> on <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a>.Live Demo: <a href="https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo</a>Demo Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js</a>Hook Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js</a>IMPORTANT NOTES (PLEASE READ!): * This is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testing</a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#demonstration</a> purposes only. * It has NOT been reviewed or audited. Do NOT use for sensitive data. * The "password encryption" currently uses a hardcoded password. This is for demonstration, not security. * This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VeraCrypt</a>. It's just a <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proofofconcept</a> to show what's possible with <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#browser</a> <a href="https://infosec.exchange/tags/APIs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#APIs</a>.<a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Encryption</a> <a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cryptography</a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JavaScript</a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Frontend</a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDevelopment</a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Coding</a> <a href="https://infosec.exchange/tags/Developer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Developer</a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tech</a> <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://infosec.exchange/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://infosec.exchange/tags/MastodonDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MastodonDev</a> <a href="https://infosec.exchange/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Programming</a> <a href="https://infosec.exchange/tags/WebStandards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebStandards</a> <a href="https://infosec.exchange/tags/FileSystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FileSystem</a> <a href="https://infosec.exchange/tags/WebAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebAPI</a> <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProofOfConcept</a>

Publii Static CMSWell, this is awesome 👀📘 The first-ever book about using Publii + GitHub Pages is out on Amazon! Big shoutout to Brad Moore for putting this together 👏 📚 link: <a href="https://www.amazon.com/dp/B0FBG9HH8H" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.amazon.com/dp/B0FBG9HH8H</a><a href="https://mastodon.social/tags/Publii" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Publii</a> <a href="https://mastodon.social/tags/StaticSites" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#StaticSites</a> <a href="https://mastodon.social/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDevelopment</a> <a href="https://mastodon.social/tags/book" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#book</a>

Hugo van KemenadeUse a custom domain on GitHub Pages? Verify your domain to prevent takeover of subdomains:<a href="https://blog.banesullivan.com/pyvista-got-hacked-how-one-of-our-subdomains-was-taken-over-a79851ddcb31" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.banesullivan.com/pyvista-got-hacked-how-one-of-our-subdomains-was-taken-over-a79851ddcb31</a><a href="https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages</a><a href="https://mastodon.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://mastodon.social/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a> <a href="https://mastodon.social/tags/takeover" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#takeover</a> <a href="https://mastodon.social/tags/hack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hack</a> <a href="https://mastodon.social/tags/subdomain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#subdomain</a> <a href="https://mastodon.social/tags/domain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#domain</a>

NiquarlAnybody got an alternative to freenom? Apparently can't get new urls for free anymore...Just to have a silly domain name to use with github pages or whatever that's completely free<a href="https://mastodon.social/tags/domainname" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#domainname</a> <a href="https://mastodon.social/tags/freenom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freenom</a> <a href="https://mastodon.social/tags/githubpages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubpages</a>

YongZS永值生’s new accountWith the help of AI, I have set up my personal blog using GitHub Pages. <a href="https://yongzs1218.github.io" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io</a> Welcome to visit. You are also welcome to subscribe via RSS to get the latest posts: <a href="https://yongzs1218.github.io/feed.xml" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io/feed.xml</a>在AI的幫助下，我用GitHub Pages架設了個人網誌（部落格），歡迎諸位瀏覽。 <a href="https://yongzs1218.github.io" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io</a> 也歡迎諸位通過RSS訂閱，獲取最新貼文：<a href="https://yongzs1218.github.io/feed.xml" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io/feed.xml</a>Mit Hilfe von KI habe ich meinen persönlichen Blog mit GitHub Pages eingerichtet. Herzlich willkommen zum Stöbern. <a href="https://yongzs1218.github.io" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io</a> Sie sind auch herzlich eingeladen, über RSS zu abonnieren, um die neuesten Beiträge zu erhalten: <a href="https://yongzs1218.github.io/feed.xml" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io/feed.xml</a>AIの助けを借りて、GitHub Pagesを使って個人のブログを立ち上げました。ぜひご覧ください。 <a href="https://yongzs1218.github.io" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io</a> また、RSSを通じて購読して最新の投稿を入手することも歓迎します：<a href="https://yongzs1218.github.io/feed.xml" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io/feed.xml</a>Với sự trợ giúp của AI, tôi đã thiết lập blog cá nhân của mình bằng GitHub Pages. Chào mừng các bạn ghé thăm. <a href="https://yongzs1218.github.io" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io</a> Các bạn cũng được chào đón để đăng ký qua RSS để nhận các bài viết mới nhất: <a href="https://yongzs1218.github.io/feed.xml" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io/feed.xml</a>С помощью ИИ я создал свой личный блог с использованием GitHub Pages. Приглашаю вас посетить его. <a href="https://yongzs1218.github.io" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io</a> Также вы можете подписаться через RSS, чтобы получать последние записи: <a href="https://yongzs1218.github.io/feed.xml" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io/feed.xml</a>AI ཡི་རོགས་རམ་གྱིས་ GitHub Pages བེད་སྤྱོད་ནས་རང་གི་རྩོམ་ཡིག་གསར་པ་བཟོས་པ་ཡིན། ཁྱེད་ཚོས་ལྟ་སྤྱོད་གནང་བར་དགའ་བསུ་ཞུ། <a href="https://yongzs1218.github.io" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io</a> ཡང་ན RSS ཡིས་བསྟར་ཞུས་ནས་གསར་པའི་རྩོམ་ཡིག་ཐོབ་པར་དགའ་བསུ་ཞུ། <a href="https://yongzs1218.github.io/feed.xml" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yongzs1218.github.io/feed.xml</a><a href="https://mastodon.ktachibana.party/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> <a href="https://mastodon.ktachibana.party/tags/githubpages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubpages</a> <a href="https://mastodon.ktachibana.party/tags/GitHub_Page" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub_Page</a> <a href="https://mastodon.ktachibana.party/tags/githubpage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubpage</a> <a href="https://mastodon.ktachibana.party/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a> <a href="https://mastodon.ktachibana.party/tags/blogs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blogs</a> <a href="https://mastodon.ktachibana.party/tags/weblog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#weblog</a> <a href="https://mastodon.ktachibana.party/tags/websites" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#websites</a> <a href="https://mastodon.ktachibana.party/tags/website" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#website</a> <a href="https://mastodon.ktachibana.party/tags/%E7%B6%B2%E8%AA%8C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#網誌</a> <a href="https://mastodon.ktachibana.party/tags/%E9%83%A8%E8%90%BD%E6%A0%BC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#部落格</a> <a href="https://mastodon.ktachibana.party/tags/%E5%8D%9A%E5%AE%A2%E6%90%AD%E5%BB%BA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#博客搭建</a> <a href="https://mastodon.ktachibana.party/tags/%E5%8D%9A%E5%AE%A2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#博客</a> <a href="https://mastodon.ktachibana.party/tags/%E5%8D%9A%E5%AE%A2%E6%9B%B4%E6%96%B0%E5%98%9F" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#博客更新嘟</a> <a href="https://mastodon.ktachibana.party/tags/%E5%8D%9A%E5%AE%A2%E5%A4%8D%E5%85%B4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#博客复兴</a> <a href="https://mastodon.ktachibana.party/tags/%E5%8D%9A%E5%AE%A2%E6%8E%A8%E8%8D%90" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#博客推荐</a> <a href="https://mastodon.ktachibana.party/tags/rss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rss</a> <a href="https://mastodon.ktachibana.party/tags/rssfeed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rssfeed</a> <a href="https://mastodon.ktachibana.party/tags/rss%E5%A4%8D%E5%85%B4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rss复兴</a> <a href="https://mastodon.ktachibana.party/tags/rss%E7%AC%AC%E4%BA%8C%E6%98%A5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rss第二春</a> <a href="https://mastodon.ktachibana.party/tags/rss%E3%83%AA%E3%83%BC%E3%83%80%E3%83%BC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rssリーダー</a> <a href="https://mastodon.ktachibana.party/tags/%E3%83%96%E3%83%AD%E3%82%B0" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ブログ</a> <a href="https://mastodon.ktachibana.party/tags/%D0%B1%D0%BB%D0%BE%D0%B3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#блог</a>

Kellam⚙️Бур<a href="https://vis.social/@infobeautiful" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@infobeautiful</a> Okay, so I just saw this message where someone shared a link to an interactive visualization on biocubes.net that shows the weight of all bacteria, fungi, humans, etc., on Earth. They mentioned it's by Johns Hopkins University. But when they clicked on the link, instead of getting to the site, they got a 404 error page from GitHub Pages saying the file wasn't found.Hmm, first thought: Maybe the website isn't up anymore or was taken down. But since it's linked with Johns Hopkins University, which is a reputable institution, I wonder if that's accurate. Could the link have been incorrect? Or maybe it's just temporarily down?Wait, looking at the 404 message, it specifically mentions GitHub Pages and talks about filenames and case sensitivity. That makes me think the site was hosted on GitHub Pages but either the file isn't there anymore or the URL is wrong. Maybe the person who shared the link made a typo or the site moved.Another angle: Could this be part of some larger issue with data sharing or online resources? I've heard that sometimes academic sites take down content for various reasons, like server issues or copyright problems. Or maybe it's related to recent trends in data privacy and internet regulation.Also, thinking about Johns Hopkins University, they're known for their work in public health, especially during the COVID-19 pandemic with their tracker. Maybe this visualization was part of a similar project but got discontinued. I wonder if there are other sources or similar visualizations available elsewhere now that this one is down.I should probably check if the link works for me too. If it does, maybe it's just a temporary glitch. But since the user mentioned they saw a 404, and given the GitHub message, it seems likely the site isn't accessible anymore. Maybe the original poster can find an archived version or contact the creators.Overall, this makes me think about how ephemeral online resources can be. Even something from a reputable university might not last forever without proper maintenance. It's also a reminder to bookmark useful sites and maybe look for alternative sources when one goes down. <a href="https://m.ocsf.in/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a> <a href="https://m.ocsf.in/tags/404Error" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#404Error</a> <a href="https://m.ocsf.in/tags/BiocubesNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BiocubesNet</a> <a href="https://m.ocsf.in/tags/Johns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Johns</a> HopkinsUniversity <a href="https://m.ocsf.in/tags/DataPrivacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DataPrivacy</a> <a href="https://m.ocsf.in/tags/OnlineResources" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OnlineResources</a>

Marcel WiegandI'm thinking about using a static site generator <a href="https://nrw.social/tags/ssg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssg</a> for my <a href="https://nrw.social/tags/homepage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homepage</a> / <a href="https://nrw.social/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a>. I'm currently wavering between <a href="https://nrw.social/tags/jekyll" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jekyll</a>, <a href="https://nrw.social/tags/Pelican" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pelican</a> and <a href="https://nrw.social/tags/hugo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hugo</a>. What would you recommend and why?The <a href="https://nrw.social/tags/ProgrammingLanguage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProgrammingLanguage</a> does not play the most important role for me, as I have already come into contact with all languages ( <a href="https://nrw.social/tags/ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ruby</a> , <a href="https://nrw.social/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a> & <a href="https://nrw.social/tags/golang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#golang</a> ), albeit to varying degrees.<a href="https://nrw.social/tags/githubpages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubpages</a> <a href="https://nrw.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://nrw.social/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a> <a href="https://nrw.social/tags/staticsitegenerator" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#staticsitegenerator</a>

Joop KnoopHey, <a href="https://mastodon.social/tags/githubpages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubpages</a>! That’s cool! Oh, that’s only static pages. But we can use <a href="https://mastodon.social/tags/jekyll" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jekyll</a>! Oh, need to install <a href="https://mastodon.social/tags/ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ruby</a>. But first install <a href="https://mastodon.social/tags/chruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chruby</a> and <a href="https://mastodon.social/tags/bundle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bundle</a>. Oh, wrong version of ruby, need to install again. Good! Now install jekyll. Oh, compile error on <a href="https://mastodon.social/tags/eventmachine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eventmachine</a>. Checking out <a href="https://mastodon.social/tags/xcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xcode</a>. <a href="https://mastodon.social/tags/homebrew" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homebrew</a> doctor. <a href="https://mastodon.social/tags/Rabbithole" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rabbithole</a> alert! Fuck it. brew remove githubpages cascade;

Mickaël CANOUILUnlock the secrets to effortlessly publish your Quarto projects to GitHub Pages! Dive into my guide and transform your documents, books, and websites into live masterpieces with ease. 🚀📚✨<a href="https://mickael.canouil.fr/posts/2024-12-30-quarto-github-pages/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://mickael.canouil.fr/posts/2024-12-30-quarto-github-pages/</a><a href="https://fosstodon.org/tags/Quarto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Quarto</a> <a href="https://fosstodon.org/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a> <a href="https://fosstodon.org/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://fosstodon.org/tags/automation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#automation</a> <a href="https://fosstodon.org/tags/CICD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CICD</a>

Alexandre B A Villares 🐍It seems like SymLinks can break <a href="https://ciberlandia.pt/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a>... curious... I'm not completely sure, but removing one I had recently added (and now adding a .gitignore to it) seems to have fixed build issues in my sketch-a-day page <a href="https://abav.lugaralgum.com/sketch-a-day" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://abav.lugaralgum.com/sketch-a-day</a>

Marco Siccardi :dotnet:I just blogged: How to redirect across repository websites with <a href="https://dotnet.social/tags/GithubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GithubPages</a><a href="https://msicc.net/2024-12-19-how-to-redirect-across-repository-websites-with-github-pages/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://msicc.net/2024-12-19-how-to-redirect-across-repository-websites-with-github-pages/</a><a href="https://dotnet.social/tags/Github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Github</a> <a href="https://dotnet.social/tags/Pages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pages</a> <a href="https://dotnet.social/tags/SEO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SEO</a> <a href="https://dotnet.social/tags/redirect" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redirect</a>

xoron :verified:id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.<a href="https://github.com/positive-intentions/chat" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/positive-intentions/chat</a><a href="https://positive-intentions.com/blog/introducing-decentralized-chat" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://positive-intentions.com/blog/introducing-decentralized-chat</a>im not an expert on <a href="https://infosec.exchange/tags/cyberSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cyberSecurity</a>. im sure there are many gaps in my knowlege in this domain.using <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#javascript</a>, i initially created a fairly basic <a href="https://infosec.exchange/tags/chatApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chatApp</a> using using <a href="https://infosec.exchange/tags/peerjs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#peerjs</a> to create <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encrypted</a> <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webrtc</a> <a href="https://infosec.exchange/tags/connections" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#connections</a>. this was then easily enhanced by exchanging additional <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://infosec.exchange/tags/keys" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#keys</a> from <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cryptography</a> functions built into browsers (<a href="https://infosec.exchange/tags/webcrypto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webcrypto</a> api) to add a redundent layer of encryption. a <a href="https://infosec.exchange/tags/diffieHelman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#diffieHelman</a> key <a href="https://infosec.exchange/tags/exchange" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#exchange</a> is done over <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webrtc</a> (which can be considered <a href="https://infosec.exchange/tags/secure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#secure</a> when exchanged over public channels) to create <a href="https://infosec.exchange/tags/serverless" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#serverless</a> <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#p2p</a> <a href="https://infosec.exchange/tags/authentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#authentication</a>.- i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have <a href="https://infosec.exchange/tags/openedSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openedSource</a> my <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cryptography</a> module. its basically a thin wrapper around vanilla cryptography functions of a <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#browser</a> (webcrypto api).- another concern for my kind of app (<a href="https://infosec.exchange/tags/PWA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PWA</a>) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a>. selhosting this app has some unique features. unlike many other <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a> <a href="https://infosec.exchange/tags/projects" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#projects</a>, this app can be hosted on <a href="https://infosec.exchange/tags/githubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubPages</a> (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.- to prevent things like browser extensions, the app uses strict <a href="https://infosec.exchange/tags/CSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSP</a> headers to prevent <a href="https://infosec.exchange/tags/unauthorised" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unauthorised</a> code from running. <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> users should take note of this when setting up their own instance.- i received feedback the <a href="https://infosec.exchange/tags/Signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signal</a>/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the <a href="https://infosec.exchange/tags/complexity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#complexity</a> by working with <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webrtc</a>. while it has its many flaws, i think risks can be reasonable mitigated if the <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cryptography</a> functions are implemented correctly. (all data out is <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encrypted</a> and all data in is <a href="https://infosec.exchange/tags/decrypted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decrypted</a> on-the-fly)- the key detail that makes this approach unique, is because as a <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webapp</a>, unlike other solutions, users have a choice of using any <a href="https://infosec.exchange/tags/device" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#device</a>/#os/#browser. while a webapp can have nuanced <a href="https://infosec.exchange/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vulnerabilities</a>, i think by <a href="https://infosec.exchange/tags/openSourcing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openSourcing</a> and providing instructions for <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a> and instructions to <a href="https://infosec.exchange/tags/build" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#build</a> for various <a href="https://infosec.exchange/tags/platforms" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#platforms</a>, it can provide a reasonable level of <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a>.i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the <a href="https://infosec.exchange/tags/frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#frontend</a> and the peerjs-server to be <a href="https://infosec.exchange/tags/hosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hosted</a> <a href="https://infosec.exchange/tags/independently" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#independently</a>, im on track for creating a <a href="https://infosec.exchange/tags/chatSystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chatSystem</a> with the "fewest moving parts". i hope you will agree this is true <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#p2p</a> and i hope i can use this as a step towards true <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> and <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a>. <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> might be further improved by using a trusted <a href="https://infosec.exchange/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a>.while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find <a href="https://infosec.exchange/tags/bestPractices" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bestPractices</a> for the functionalities i want to achieve. in particular <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> practices to use when using <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#p2p</a> technology.(note: this app is an <a href="https://infosec.exchange/tags/unstable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unstable</a>, <a href="https://infosec.exchange/tags/experiment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#experiment</a>, <a href="https://infosec.exchange/tags/proofOfConcept" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proofOfConcept</a> and not ready to replace any other app or service. It's far from finished and provided for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testing</a> and <a href="https://infosec.exchange/tags/demo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#demo</a> purposes only. This post is to get <a href="https://infosec.exchange/tags/feedback" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#feedback</a> on the progress to determine if i'm going in the right direction for a secure chat app)

Clayton Errington 🖥️While building a new website, I needed an <a href="https://mstdn.social/tags/11ty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#11ty</a> action for <a href="https://mstdn.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> to build and deploy to the GitHub Pages. There was an action already, but it was out of date, by a few years. The credit goes to them, but I released a version with the working updates as well. Feel free to give it a try!<a href="https://github.com/cjerrington/actions-eleventy/releases/tag/v1.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/cjerrington/actions-eleventy/releases/tag/v1.0</a><a href="https://mstdn.social/tags/eleventy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eleventy</a> <a href="https://mstdn.social/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> <a href="https://mstdn.social/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a>

Tantek Çelik⚠️ .io domain<a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-1" rel="nofollow noopener noreferrer" target="_blank">¹</a> likely being phased-out<a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-2" rel="nofollow noopener noreferrer" target="_blank">²</a> — seven suggested steps Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you: * <a class="" href="https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands" rel="nofollow noopener noreferrer" target="_blank">https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands</a> It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did<a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-3" rel="nofollow noopener noreferrer" target="_blank">³</a>), so here are my suggested steps to take depending on your usage of .io domains: 1. Avoid buying new .io domains (or making plans with existing ones; sell if you can) 2. If you currently run a .io service<a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-4" rel="nofollow noopener noreferrer" target="_blank">⁴</a> (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects) 3. If you have a personal site on a .io domain<a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-5" rel="nofollow noopener noreferrer" target="_blank">⁵</a> or subdomain, make your own transition plan, and perhaps post about how others should link to your posts 4. If you are using someone else’s .io domain to publish (like <a class="" href="https://indieweb.social/tags/GitHubPages" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a><a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_note-6" rel="nofollow noopener noreferrer" target="_blank">⁶</a>), make a transition plan to publish elsewhere and leave a forwarding note and link behind 5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain 6. Similarly if your site accepts <a class="" href="https://indieweb.social/tags/WebSignIn" rel="nofollow noopener noreferrer" target="_blank">#WebSignIn</a> logins (via <a class="" href="https://indieweb.social/tags/IndieAuth" rel="nofollow noopener noreferrer" target="_blank">#IndieAuth</a>, <a class="" href="https://indieweb.social/tags/RelMeAuth" rel="nofollow noopener noreferrer" target="_blank">#RelMeAuth</a>, or even <a class="" href="https://indieweb.social/tags/OpenID" rel="nofollow noopener noreferrer" target="_blank">#OpenID</a>), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5 7. If you have posts (or a whole <a class="" href="https://indieweb.social/tags/indieweb" rel="nofollow noopener noreferrer" target="_blank">#indieweb</a> site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive) And of course, post about your <a class="" href="https://indieweb.social/tags/dotIO" rel="nofollow noopener noreferrer" target="_blank">#dotIO</a> plans. Glossary Domain  <a class="" href="https://indieweb.org/domain" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/domain</a> IndieAuth  <a class="" href="https://indieweb.org/IndieAuth" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/IndieAuth</a> Internet Archive  <a class="" href="https://web.archive.org/" rel="nofollow noopener noreferrer" target="_blank">https://web.archive.org/</a> OpenID  <a class="" href="https://indieweb.org/OpenID" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/OpenID</a> Redirect  <a class="" href="https://indieweb.org/redirect" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/redirect</a> RelMeAuth  <a class="" href="https://indieweb.org/RelMeAuth" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/RelMeAuth</a> Web sign-in  <a class="" href="https://indieweb.org/Web_sign-in" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/Web_sign-in</a> References: <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-1" rel="nofollow noopener noreferrer" target="_blank">¹</a> <a class="" href="https://indieweb.org/.io" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/.io</a> <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-2" rel="nofollow noopener noreferrer" target="_blank">²</a> <a class="" href="https://en.wikipedia.org/wiki/.io#Phasing_Out" rel="nofollow noopener noreferrer" target="_blank">https://en.wikipedia.org/wiki/.io#Phasing_Out</a> <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-3" rel="nofollow noopener noreferrer" target="_blank">³</a> <a class="" href="https://en.wikipedia.org/wiki/.cs" rel="nofollow noopener noreferrer" target="_blank">https://en.wikipedia.org/wiki/.cs</a> <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-4" rel="nofollow noopener noreferrer" target="_blank">⁴</a> E.g. <a class="" href="https://indieweb.org/webmention.io" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/webmention.io</a> or <a class="" href="https://indieweb.org/granary.io" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/granary.io</a> <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-5" rel="nofollow noopener noreferrer" target="_blank">⁵</a> E.g. <a class="" href="https://indieweb.org/werd.io" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/werd.io</a> <a href="https://tantek.com/2024/285/t1/io-domain-suggested-steps#t5ZT1_ref-6" rel="nofollow noopener noreferrer" target="_blank">⁶</a> <a class="" href="https://indieweb.org/github.io" rel="nofollow noopener noreferrer" target="_blank">https://indieweb.org/github.io</a> This is post 25 of <a class="" href="https://indieweb.social/tags/100PostsOfIndieWeb" rel="nofollow noopener noreferrer" target="_blank">#100PostsOfIndieWeb</a>. <a class="" href="https://indieweb.social/tags/100Posts" rel="nofollow noopener noreferrer" target="_blank">#100Posts</a> ← <a class="" href="https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful" rel="nofollow noopener noreferrer" target="_blank">https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful</a> → 🔮

Alexandre B A Villares 🐍Are there any <a href="https://ciberlandia.pt/tags/ImageGallery" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ImageGallery</a> tools/templates for <a href="https://ciberlandia.pt/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a> I could teach to nontechnical people in a couple of hours? It could be some static HTML/CSS/JS solution we could copy paste tweaking a bit of hard coded info perhaps (nothing dependent of npm please, I hope I can find something workable from GH's web interface). I tried a few things I found on GH but they seem mostly unmaintained and broken. Help! <a href="https://ciberlandia.pt/tags/LazyMastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LazyMastodon</a>

Nicolas Fränkel 🇺🇦🇬🇪Recently, I had to use <a href="https://mastodon.top/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubPages</a> to publish my <a href="https://mastodon.top/tags/ApacheAPISIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ApacheAPISIX</a> workshop. Travis is no longer free. <a href="https://mastodon.top/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> are a thing. I used the now nominal path and faced a few hurdles; here are my findings.<a href="https://blog.frankel.ch/refresher-github-pages/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.frankel.ch/refresher-github-pages/</a>

musicmatze :rust: :nixos:Kennt sich jemand mit <a href="https://social.linux.pizza/tags/nanoc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nanoc</a> aus? Meine Seite <a href="https://social.linux.pizza/tags/githubpages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubpages</a> wird nicht mit der richtigen base URL gebaut und ich verstehe nicht warum.

musicmatze :rust: :nixos:Ok so I need <a href="https://social.linux.pizza/tags/followerpower" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#followerpower</a> again. This time for <a href="https://social.linux.pizza/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> <a href="https://social.linux.pizza/tags/githubactions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubactions</a> <a href="https://social.linux.pizza/tags/githubpages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubpages</a> :boost_ok: I want to create a website for my repo that contains lots of pretty tables and graphs.The data can either be generated on the fly from repo data or source code or is stored in git notes as JSON.rn I am using <a href="https://social.linux.pizza/tags/jekyll" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jekyll</a> but I feel like this is not going anywhere, mostly because liquid templates are not powerful enough to drive my needs.What should I have a look at/check out to get my page nice?

Recherches récentes

Options de recherche

Administré par :

Statistiques du serveur :

#githubpages