mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

580
comptes actifs

#githubpages

1 message1 participant0 message aujourd’hui

Time to make a move? #GiveUpGitHub

My new blog post is just out #BurgeonLab

➡️ burgeonlab.com/blog/migrate-gi

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.

Open Graph image for the blog post 'Alternative to GitHub Pages: SourceHut Builds + Bunny.net'
Burgeon LabGitHub Pages Alternative: SourceHut Builds + Bunny.net
Plus via Naty

File encryption with a browser.

I've been exploring the #WebCryptoAPI and I'm impressed!

When combined with the #FileSystemAPI, it offers a seemingly secure way to #encrypt and #store files directly on your device. Think #localstorage, but with #encryption!

I know #webapps can have #security vulnerabilities since the code is served over the web, so I've #OpenSourced my demo! You can check it out, and it should even work if #selfhosted on #GitHubPages.

Live Demo: dim.positive-intentions.com/?p

Demo Code: github.com/positive-intentions

Hook Code: github.com/positive-intentions

IMPORTANT NOTES (PLEASE READ!):
* This is NOT a product. It's for #testing and #demonstration 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 #VeraCrypt. It's just a #proofofconcept to show what's possible with #browser #APIs.

dim.positive-intentions.com@storybook/core - Storybook

With the help of AI, I have set up my personal blog using GitHub Pages.
yongzs1218.github.io
Welcome to visit. You are also welcome to subscribe via RSS to get the latest posts: yongzs1218.github.io/feed.xml

在AI的幫助下,我用GitHub Pages架設了個人網誌(部落格),歡迎諸位瀏覽。
yongzs1218.github.io
也歡迎諸位通過RSS訂閱,獲取最新貼文:yongzs1218.github.io/feed.xml

Mit Hilfe von KI habe ich meinen persönlichen Blog mit GitHub Pages eingerichtet. Herzlich willkommen zum Stöbern.
yongzs1218.github.io
Sie sind auch herzlich eingeladen, über RSS zu abonnieren, um die neuesten Beiträge zu erhalten: yongzs1218.github.io/feed.xml

AIの助けを借りて、GitHub Pagesを使って個人のブログを立ち上げました。ぜひご覧ください。
yongzs1218.github.io
また、RSSを通じて購読して最新の投稿を入手することも歓迎します:yongzs1218.github.io/feed.xml

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.
yongzs1218.github.io
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: yongzs1218.github.io/feed.xml

С помощью ИИ я создал свой личный блог с использованием GitHub Pages. Приглашаю вас посетить его.
yongzs1218.github.io
Также вы можете подписаться через RSS, чтобы получать последние записи: yongzs1218.github.io/feed.xml

AI ཡི་རོགས་རམ་གྱིས་ GitHub Pages བེད་སྤྱོད་ནས་རང་གི་རྩོམ་ཡིག་གསར་པ་བཟོས་པ་ཡིན། ཁྱེད་ཚོས་ལྟ་སྤྱོད་གནང་བར་དགའ་བསུ་ཞུ།
yongzs1218.github.io
ཡང་ན RSS ཡིས་བསྟར་ཞུས་ནས་གསར་པའི་རྩོམ་ཡིག་ཐོབ་པར་དགའ་བསུ་ཞུ། yongzs1218.github.io/feed.xml

YongZS永值生’s Personal WeblogHome主頁Music production enthusiast, travelling & photography lover, I’ll post my daily life here. 音樂製作愛好者,旅行與攝影愛好者,我會將我的日常生活發布至此。
A répondu dans un fil de discussion

@infobeautiful
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.
#GitHubPages #404Error #BiocubesNet #Johns HopkinsUniversity #DataPrivacy #OnlineResources

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.

github.com/positive-intentions

positive-intentions.com/blog/i

im not an expert on #cyberSecurity. im sure there are many gaps in my knowlege in this domain.

using #javascript, i initially created a fairly basic #chatApp using using #peerjs to create #encrypted #webrtc #connections. this was then easily enhanced by exchanging additional #encryption #keys from #cryptography functions built into browsers (#webcrypto api) to add a redundent layer of encryption. a #diffieHelman key #exchange is done over #webrtc (which can be considered #secure when exchanged over public channels) to create #serverless #p2p #authentication.

- i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have #openedSource my #cryptography module. its basically a thin wrapper around vanilla cryptography functions of a #browser (webcrypto api).

- another concern for my kind of app (#PWA) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for #selfhosting. selhosting this app has some unique features. unlike many other #selfhosted #projects, this app can be hosted on #githubPages (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 #CSP headers to prevent #unauthorised code from running. #selfhosting users should take note of this when setting up their own instance.

- i received feedback the #Signal/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the #complexity by working with #webrtc. while it has its many flaws, i think risks can be reasonable mitigated if the #cryptography functions are implemented correctly. (all data out is #encrypted and all data in is #decrypted on-the-fly)

- the key detail that makes this approach unique, is because as a #webapp, unlike other solutions, users have a choice of using any #device/#os/#browser. while a webapp can have nuanced #vulnerabilities, i think by #openSourcing and providing instructions for #selfhosting and instructions to #build for various #platforms, it can provide a reasonable level of #security.

i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the #frontend and the peerjs-server to be #hosted #independently, im on track for creating a #chatSystem with the "fewest moving parts". i hope you will agree this is true #p2p and i hope i can use this as a step towards true #privacy and #security. #security might be further improved by using a trusted #VPN.

while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find #bestPractices for the functionalities i want to achieve. in particular #security practices to use when using #p2p technology.

(note: this app is an #unstable, #experiment, #proofOfConcept and not ready to replace any other app or service. It's far from finished and provided for #testing and #demo purposes only. This post is to get #feedback on the progress to determine if i'm going in the right direction for a secure chat app)

GitHubGitHub - positive-intentions/chat: Decentralized chatDecentralized chat. Contribute to positive-intentions/chat development by creating an account on GitHub.

⚠️ .io domain¹ likely being phased-out² — seven suggested steps

Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you:
* https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands

It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did³), 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 (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 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 #GitHubPages), 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 #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), 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 #indieweb 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 #dotIO plans.

Glossary

Domain
 https://indieweb.org/domain
IndieAuth
 https://indieweb.org/IndieAuth
Internet Archive
 https://web.archive.org/
OpenID
 https://indieweb.org/OpenID
Redirect
 https://indieweb.org/redirect
RelMeAuth
 https://indieweb.org/RelMeAuth
Web sign-in
 https://indieweb.org/Web_sign-in


References:

¹ https://indieweb.org/.io
² https://en.wikipedia.org/wiki/.io#Phasing_Out
³ https://en.wikipedia.org/wiki/.cs
E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io
E.g. https://indieweb.org/werd.io
https://indieweb.org/github.io


This is post 25 of #100PostsOfIndieWeb. #100Posts

https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful
🔮

tantek.com⚠️ .io domain^1 likely being phased-out^2 — seven suggested steps Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you: * https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did^3), 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^4 (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^5 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 #GitHubPages^6), 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 #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), 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 #indieweb 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 #dotIO plans. Glossary Domain https://indieweb.org/domain IndieAuth https://indieweb.org/IndieAuth Internet Archive https://web.archive.org/ OpenID https://indieweb.org/OpenID Redirect https://indieweb.org/redirect RelMeAuth https://indieweb.org/RelMeAuth Web sign-in https://indieweb.org/Web_sign-in References: ^1 https://indieweb.org/.io ^2 https://en.wikipedia.org/wiki/.io#Phasing_Out ^3 https://en.wikipedia.org/wiki/.cs ^4 E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io ^5 E.g. https://indieweb.org/werd.io ^6 https://indieweb.org/github.io This is post 25 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful → 🔮 - Tantek

Ok so I need #followerpower again. This time for #github #githubactions #githubpages :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 #jekyll 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?