
yamanoku
@yamanoku@hollo.yamanoku.net
主催する勉強会についての紹介記事を出しました。よければご覧になってみてください。
「オンラインよもやま会」とは何か?生まれたきっかけについて
@yamanoku@hollo.yamanoku.net · 106 following · 135 followers
一児の父です。会社員。
Pronouns | Home | |
---|---|---|
he/him |
@yamanoku@hollo.yamanoku.net
主催する勉強会についての紹介記事を出しました。よければご覧になってみてください。
「オンラインよもやま会」とは何か?生まれたきっかけについて
@yamanoku@hollo.yamanoku.net
GitHub Copilotとか使ってます?の質問に「俺Vimmerなんで…」で会話が終了してしまった話しましたっけ?
@yamanoku@hollo.yamanoku.net
日報まとめをNotebookLMに食わせてポッドキャスト化すると、褒めてくるのがなんかむず痒くなる
https://notebooklm.google.com/notebook/731ee3fa-282d-4695-9a42-c08774783f62?authuser=0
@yamanoku@hollo.yamanoku.net · Reply to yamanoku's post
もちろん自分だけがもつ感覚ではないと思うけど(近しい人はいると思う)、圧倒的多数の人と比較するとって思いがあります
@yamanoku@hollo.yamanoku.net
自分の感覚としてSNSは情報収集にちょっと娯楽が流れてくるようなもんで捉えてる この感覚は人とは違うのかもなと最近の気づきになってる(遅)
@yamanoku@hollo.yamanoku.net
position: sticky が効かない原因を CSS 仕様から読み解く – スクロールコンテナーと包含ブロック - Katashin .info
@yamanoku@hollo.yamanoku.net
Vibe Codingで頑張りました(Claude Codeが)
awesome-japanese-a11y-companies/mcp at main · yamanoku/awesome-japanese-a11y-companies
https://github.com/yamanoku/awesome-japanese-a11y-companies/tree/main/mcp
https://hollo.yamanoku.net/@yamanoku/01974a94-1cc1-7131-8b61-8272538b1733
@yamanoku@hollo.yamanoku.net
awesome-japanese-a11y-companiesをリモートMCPサーバーで提供してみるというアイデアができたので作ってみよう
https://github.com/yamanoku/awesome-japanese-a11y-companies/issues/52
@yamanoku@hollo.yamanoku.net
claude code でローカルなMCPサーバーを叩けるようにする
@yamanoku@hollo.yamanoku.net
Arc Browserはなぜ開発終了したのか、開発会社のThe Browser Companyが経緯を説明 - GIGAZINE
@yamanoku@hollo.yamanoku.net
プロジェクトにおける政治について - Speaker Deck
https://speakerdeck.com/ichimichi/puroziekutoniokeruzheng-zhi-nituite
@yamanoku@hollo.yamanoku.net
KDDI、視覚障がい者のスマホ支援「スマホ操作サポートシール」無償配布 - ケータイ Watch
@yamanoku@hollo.yamanoku.net
0.6.2で修正されてElkでもログインできるようになりました!ありがとう!
https://hollo.social/@hollo/01974982-0ea3-7848-a33f-3b0b2e3e2f3f
@hollo@hollo.social
🚨 Known Issue: Elk (@elk) login may fail on Hollo instances upgraded from 0.5.x to 0.6.x with 401 Unauthorized
errors. Fresh 0.6.x installs work fine. Other clients (Phanpy, Moshidon) are unaffected.
We're investigating: https://github.com/fedify-dev/hollo/issues/167
Workaround: Use alternative clients like Phanpy (@phanpy) for now.
@yamanoku@hollo.yamanoku.net
awesome-japanese-a11y-companiesをリモートMCPサーバーで提供してみるというアイデアができたので作ってみよう
https://github.com/yamanoku/awesome-japanese-a11y-companies/issues/52
@AureoleArk@misskey.io
お仕事とプライベートでCursorエディタのアカウントを簡単に切り替えたい人向けのスクリプト作ったので共有する
Windows
https://gist.github.com/SanMurakami/577cd3e1fd0661b1277729ca7eeafc50
Mac
https://gist.github.com/SanMurakami/213428dc56205e661e187a6184dcd236
@yamanoku@hollo.yamanoku.net
油断するとあっという間に前髪フロントエンドになる
@yamanoku@hollo.yamanoku.net
Railwayに依存するのもそろそろ卒業かな〜…
@hollo@hollo.social
What client apps do you use with #Hollo?
Option | Voters |
---|---|
Elk | 1 (33%) |
Phanpy | 1 (33%) |
Moshidon | 1 (33%) |
Subway Tooter | 0 (0%) |
Mona | 0 (0%) |
Nightfox DAWN | 0 (0%) |
Tusker | 0 (0%) |
Woolly | 0 (0%) |
@yamanoku@hollo.yamanoku.net
Moshidonは大丈夫な感じなんだけどな 使えるクライアントが数台あると安心感あるね
@hollo@hollo.social
🚨 Known Issue: Elk (@elk) login may fail on Hollo instances upgraded from 0.5.x to 0.6.x with 401 Unauthorized
errors. Fresh 0.6.x installs work fine. Other clients (Phanpy, Moshidon) are unaffected.
We're investigating: https://github.com/fedify-dev/hollo/issues/167
Workaround: Use alternative clients like Phanpy (@phanpy) for now.
@yamanoku@hollo.yamanoku.net · Reply to 洪 民憙 (Hong Minhee)'s post
@hongminhee 最新版(latest)でデプロイしてるんですけどログインできなかったですね… Oauthの理解が浅いのですが、Elk側(クライアント)の方でも解消が必要なのかもしれません
@yamanoku@hollo.yamanoku.net · Reply to yamanoku's post
@yamanoku@hollo.yamanoku.net · Reply to yamanoku's post
今はPhanpyに移動してポストしてます
@yamanoku@hollo.yamanoku.net
あとElkでログインできなくなったなー
@yamanoku@hollo.yamanoku.net
Hollo@0.6.1でRedeployしたらRailwayで設定しているSECRET_KEYが短くてエラーになってた…(元が32文字だったのが44文字以上必要になった) https://github.com/fedify-dev/hollo/pull/126
SECRET_KEY再設定したらデプロイできるようになった
@yamanoku@hollo.yamanoku.net
自分専用のCosense MCPサーバー作ってみようかな
@yamanoku@hollo.yamanoku.net · Reply to yamanoku's post
エンタメ部門優勝やったー
@yamanoku@hollo.yamanoku.net
TwoGate RubyKaigi×TSKaigi After Talk
https://scrapbox.io/lacolaco/TwoGate_RubyKaigi×TSKaigi_After_Talk
@yamanoku@hollo.yamanoku.net
大手アダルト動画サイトのPornhubがフランスから撤退して30分でVPNサービスの登録者数が1000%増加、TikTokのアメリカ撤退時より凄まじい数字 - GIGAZINE
@yamanoku@hollo.yamanoku.net
フロントエンドカンファレンス北海道公式ウェブサイトの乗っ取りについて経緯と原因、現況のご報告|フロントエンドカンファレンス北海道実行委員会
@yamanoku@hollo.yamanoku.net
久々に見に来たら破産手続きしとる…でも父と会話できてよかったね…
【第43話】FX戦士くるみちゃん|カドコミ (コミックウォーカー)
@yamanoku@hollo.yamanoku.net
Hollo v0.6.0リリースめでたい!前回から続けてちょこっと関わらせてもらいました。 https://hollo.social/@hollo/01973f15-68c5-70d8-9392-4201fc446e38
@hollo@hollo.social
We're excited to announce Hollo 0.6.0, a significant release that brings enhanced security, better user experience, and important infrastructure improvements to your single-user microblogging setup.
This release prioritizes security with comprehensive OAuth 2.0 improvements that align with current best practices. We've implemented several critical RFC standards that significantly strengthen the authorization process:
OAuth 2.0 Authorization Code Flow with Access Grants — We've overhauled the OAuth implementation to properly separate authorization codes from access token issuance, providing better security isolation throughout the authentication process.
RFC 7636 PKCE (Proof Key for Code Exchange) Support — Hollo now supports PKCE with the S256 code challenge method, which prevents authorization code interception attacks. This is particularly important for public clients and follows the latest OAuth 2.0 security recommendations outlined in RFC 9700 (OAuth 2.0 Security Current Best Practices).
RFC 8414 OAuth Authorization Server Metadata — We've added support for OAuth Authorization Server metadata endpoints, allowing clients to automatically discover Hollo's OAuth capabilities and configuration. This makes integration smoother and helps clients adapt to your server's specific OAuth setup.
Enhanced Profile Scope Support — The new /oauth/userinfo
endpoint and expanded profile scope support provide applications with standardized ways to access user profile information, improving compatibility with a wider range of OAuth-compliant applications.
These OAuth improvements not only make Hollo more secure but also position it at the forefront of federated social media security standards. We encourage other fediverse projects to adopt these same standards to ensure the entire ecosystem benefits from these security enhancements.
Special thanks to Emelia Smith (@thisismissem) for spearheading these critical OAuth security improvements and ensuring Hollo stays ahead of the curve on authentication best practices.
We've significantly improved how Hollo handles media storage configuration, making it more flexible and future-ready:
New Environment Variables — The storage system now uses STORAGE_URL_BASE
(replacing the deprecated ASSET_URL_BASE
) and FS_STORAGE_PATH
for local filesystem storage (replacing FS_ASSET_PATH
). These changes provide clearer naming and better organization.
Improved Security Requirements — The SECRET_KEY
environment variable now requires a minimum of 44 characters, ensuring sufficient entropy for cryptographic operations. You'll need to update your configuration if your current secret key is shorter.
Network Binding Control — The new BIND
environment variable lets you specify exactly which network interface Hollo should listen on, giving you more control over your server's network configuration.
Thanks to Emelia Smith (@thisismissem) for leading these infrastructure improvements.
Customizable Profile Themes — You can now personalize your profile page with different theme colors. Choose from the full range of Pico CSS color options to make your profile uniquely yours.
Enhanced Administration Dashboard — The dashboard now displays the current Hollo version at the bottom, making it easier to track which version you're running. You can also sign out directly from the dashboard for better session management.
Improved Post Presentation — Shared posts on profile pages now have better visual separation from original content, and the sharing timestamp is clearly displayed. This makes it much easier to distinguish between your original thoughts and content you've shared from others.
Better Image Accessibility — Alt text for images is now displayed within expandable details sections, improving accessibility while keeping the interface clean.
Syntax Highlighting — Code blocks in Markdown posts now feature beautiful syntax highlighting powered by Shiki, supporting a comprehensive range of programming languages. This makes technical discussions much more readable.
Enhanced Character Limit — The maximum post length has been increased from 4,096 to 10,000 characters, giving you more space to express your thoughts in detail.
Thanks to RangHo Lee (@rangho_220) for the version display feature and Okuto Oyama (@yamanoku) for the image accessibility improvements.
EXIF Metadata Removal — Hollo now automatically strips EXIF metadata from uploaded images before storing them, protecting your privacy by removing potentially sensitive location and device information.
Public API Endpoints — Following Mastodon's approach, certain API endpoints are now publicly accessible without authentication, making Hollo more compatible with various client applications and improving the overall federation experience.
Thanks to NTSK (@ntek) for the privacy-focused EXIF metadata stripping implementation.
Node.js 24+ Requirement — This release requires Node.js 24.0.0 or later. We've also upgraded to Fedify 1.5.3 and @fedify/postgres 0.3.0 for improved performance and compatibility.
Test Coverage & Quality Assurance — The codebase now includes comprehensive testing infrastructure and test coverage. We're committed to expanding this coverage and integrating testing more deeply into our development and release workflows. This also provides an excellent opportunity for first-time contributors to get involved by writing tests.
Cross-Origin Request Support — OAuth and well-known endpoints now properly support cross-origin requests, aligning with Mastodon's behavior and improving client compatibility.
Cleaner Token Endpoint — The scope parameter is now properly optional for the OAuth token endpoint, clarifying that it only affects client credentials flows (not authorization code flows, where it was already ignored).
This release represents a major step forward in making Hollo not just a great single-user microblogging platform, but also a leader in federated social media security standards. The OAuth improvements we've implemented should serve as a model for other fediverse projects.
We're particularly excited about the OAuth security enhancements, which demonstrate our commitment to staying ahead of security best practices. As the federated web continues to evolve, we believe these standards will become increasingly important for maintaining user trust and ensuring secure interactions across the fediverse.
Upgrading to Hollo 0.6.0 is straightforward, but there are a few important considerations:
docker pull ghcr.io/fedify-dev/hollo:latest
git pull
pnpm install
pnpm run prod
Environment Variables: Update your configuration if you're using deprecated variables:
ASSET_URL_BASE
with STORAGE_URL_BASE
FS_ASSET_PATH
with FS_STORAGE_PATH
SECRET_KEY
is at least 44 characters longSession Reset: Due to the OAuth security improvements, existing user sessions may be invalidated during the upgrade. You'll likely need to log in again through your client apps (like Phanpy, Moshidon, etc.) after upgrading. This is a one-time inconvenience that ensures you benefit from the enhanced security features.
Thank you to everyone who contributed to this release, and to the community for your continued support. Hollo 0.6.0 brings significant improvements to security, usability, and the overall experience of running your own corner of the fediverse.