Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.
Picking uncontested private IP subnets with usage data via 
@archArch 
https://lobste.rs/s/vtfzri #networking
https://blog.benjojo.co.uk/post/picking-unused-rfc1918-ip-space
怪文書すぎる
おおくのみなさんが松屋との出会いを記されてい... | 松屋研究会 https://matsuken.matsuyafoods.co.jp/chats/jc8zgocylljw5s5t
松屋来たら店内放送でこれ読まれてて死んだ。店内放送で怪文書を読むな。
◯◯県の郷土クン煮 故郷の味
Twitter's new encrypted DM system stores your private key material on Twitter-owned services, protected with nothing more than a 4-digit PIN. If hostile, or if legally compelled to, Twitter could easily decrypt all your messages. It's also MITMable and doesn't secure metadata. Use Signal.
#Fediverse松屋倶楽部 作るか
🎉 What if the Fediverse met... in real life?
🎤 FediCon — August 1st & 2nd in Vancouver 🇨🇦
Talks. Demos. Panels. Real humans.
Get on the early bird list.
See you there?
#FediCon #Fediverse #OpenSocial #OpenSocialWeb #SocialWeb #DeSo #FeSo #LoSo
As Pixelfed adopts webpush in a future release, it will open up push notifications to 3rd party apps!
We love our vibrant app ecosystem, and want to give them the same access as our official apps.
Let the people pick ✨
Please move along, nothing to see here 🙈
But yes I just uploaded my Fediverse promo video to my self-hosted #PeerTube in case tomorrow I encounter technical glitches and need to share a link. The video is set to private (for now!), I will change its status to public on Monday. Sooo excited, it's finally happeniiiiiing.
Thank you 
@samaabergSamuel Aaberg @TheLifeofTarzanRiyen P for your help with this!
仕事しんどすぎてリーダーと長話してたんだけど結論『キックボクシングを始める』になったので筋肉がすべてを解決する可能性に賭けるぜ私は
'계엄 비판' 비평 뺀 서울시립미술관, 왜?... "정치적 검열"
입력2025.06.04 16:3022면
서울시립미술관 '계엄 비판' 비평 제외 논란
해당 글쓴 남웅 평론가 "정치적 검열" 반발
평론가 8인 "나쁜 선례... 부정적 영향 우려" m.hankookilbo.com/News/Read/Am...
'계엄 비판' 비평 뺀 서울시립미술관, 왜?... "정...
The new Pixelfed webUI solves almost every reported issue, your feedback has been pivotal to the evolution in so many respects.
Best of all, we're adopting a new design system by our talented lead designer and custom (nuxt inspired) frontend to supercharge development.
It's beautiful, but also way more resilient, with better offline/network connectivity support, webpush integration and client caching for faster loads
It's way more open and features new discovery tools to find friends + topics
The new Pixelfed web experience is so much better, I can't wait to ship it so you can experience it too ✨
うまトマは塩味つよいのでご飯は多めがおすすめです
いらないと思ってたけどやっぱり修士号欲しいかもしれない
The new Pixelfed UI uses our next generation APIs that better fit our platform.
The MastoAPI has been useful to Pixelfed so we could support 3rd party apps, however it's not quite suited for our use case.
That being said, we don't plan on dropping MastoAPI support anytime soon, and if we do, will give a 1 year phase out warning.
尹 파면에 짐 싼 대통령실 직원들…줄줄이 공기업 이직
2025.06.05 오후 12:00
5월 퇴직공직자 취업심사 67건 결과 발표
www.news1.kr/politics/pre...
尹 파면에 짐 싼 대통령실 직원들…줄줄이 공기업 이직
[이재명시대] 새 정부, ‘게관위 폐지’ 칼 빼든다...게임 거버넌스 전면 개편
입력 2025.06.04 19:19
www.ftoday.co.kr/news/article...
[이재명시대] 새 정부, ‘게관위 폐지’ 칼 빼든다.....
ちなみに今日も松屋のネギマヨ辣牛めしを食べている
우리인생 서버에 문제가 생긴 건지 내 계정에 문제가 생긴 건지 내 폰에 문제가 생긴 건지 
うまトマハンバーグ定食
尹 파면에 짐 싼 대통령실 직원들…줄줄이 공기업 이직
2025.06.05 오후 12:00
5월 퇴직공직자 취업심사 67건 결과 발표
www.news1.kr/politics/pre...
尹 파면에 짐 싼 대통령실 직원들…줄줄이 공기업 이직
あれ？京浜東北線のLCDのUIマイナーチェンジしてる？
我也有下班照
Join us at #FediForum today — an unconference about the ActivityPub ecosystem. We’ll be doing a live demo and proposing a session:
Behind the Bonfire: building a fediverse app in public
Curious how a fediverse app actually gets made? We’ll share the journey to Bonfire 1.0, talk about deployment, governance, and what building in public really looks like — the good, the hard, and the weird.
1/2
This is a chance to poke at the process, challenge assumptions, and have an open conversation. Bring your curiosity, hard questions, and ideas about co-design, funding, burnout, moderation, and the messy realities of open-source work.
Let’s dig into how fediverse apps get built, maintained, and shaped by their communities.
See you there! 🔗 https://fediforum.org
As Pixelfed adopts webpush in a future release, it will open up push notifications to 3rd party apps!
We love our vibrant app ecosystem, and want to give them the same access as our official apps.
Let the people pick ✨
Join us at #FediForum today — an unconference about the ActivityPub ecosystem. We’ll be doing a live demo and proposing a session:
Behind the Bonfire: building a fediverse app in public
Curious how a fediverse app actually gets made? We’ll share the journey to Bonfire 1.0, talk about deployment, governance, and what building in public really looks like — the good, the hard, and the weird.
1/2
💻 🎹 🕹️ ✏️ Creative Code Stammtisch 📷 🔬💃 🎛️
First Friday of every month.
A free event that is part casual hangout, part show-and-tell. We are open and welcoming to everyone interested in using code for creative self-expression. Folks of all backgrounds and skill levels are welcome!
https://www.meetup.com/creativecodeberlin/events/306813232/
[Artwork by 
@action_ioNuño de la Serna]
[이재명시대] 새 정부, ‘게관위 폐지’ 칼 빼든다...게임 거버넌스 전면 개편
입력 2025.06.04 19:19
www.ftoday.co.kr/news/article...
[이재명시대] 새 정부, ‘게관위 폐지’ 칼 빼든다.....
10年くらいらしい 
ヌートリアの平均寿命って何年なんですかね？
@thisismissemEmelia 👸🏻 Congratulations!
I'm still kind of obsessed with the idea of turning the profile color into a federatable actor property and creating an FEP to let server platforms (and ultimately clients) display people's profiles with visual accents in their chosen color.
It's not MySpace level of customization, but giving people a sense of ownership of "their" space is nice.
Would that be a waste of time or would any other platform want to buy in? 
@julian@community.nodebb.org 
@dansup 
@renchapRenaud Chaput 
@rimu
@julian@fietkau.socialJulian Fietkau @thisismissemEmelia 👸🏻 @julian@community.nodebb.org @dansup @renchapRenaud Chaput It'd need to be two colors - one for light mode and another for dark.
...maybe you'd need a corresponding text color too, for when the accent is used as a button background, etc. A light and a dark mode text color.
...and then again, many clients have multiple themes with different color schemes. It'd be hard to ensure the custom accent looks ok on all of them.
uspol meme, climate meme
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 (@thisismissemEmelia 👸🏻) 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 (@thisismissemEmelia 👸🏻) 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 (
@ntekNTSK) 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:latestgit pullpnpm installpnpm run prodEnvironment Variables: Update your configuration if you're using deprecated variables:
ASSET_URL_BASE with STORAGE_URL_BASEFS_ASSET_PATH with FS_STORAGE_PATHSECRET_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.
@thisismissemEmelia 👸🏻 Congratulations!
I'm still kind of obsessed with the idea of turning the profile color into a federatable actor property and creating an FEP to let server platforms (and ultimately clients) display people's profiles with visual accents in their chosen color.
It's not MySpace level of customization, but giving people a sense of ownership of "their" space is nice.
Would that be a waste of time or would any other platform want to buy in? @julian@community.nodebb.org @dansup @renchapRenaud Chaput @rimu
今週末はなんにもない！
今週末はなんにもない！
Switch 2の本体スピーカー、めちゃくちゃ音良くなっててびっくりした
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 (@thisismissemEmelia 👸🏻) 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 (@thisismissemEmelia 👸🏻) 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 (@ntekNTSK) 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:latestgit pullpnpm installpnpm run prodEnvironment Variables: Update your configuration if you're using deprecated variables:
ASSET_URL_BASE with STORAGE_URL_BASEFS_ASSET_PATH with FS_STORAGE_PATHSECRET_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.
DC류에서 10번 신고하면 계정 정지되는 걸 악용해서, 여성 길드 / 여성 유저만 조직적으로 신고하는 움직임이 있다고. "나랑 안 놀아줘"를 원한으로 승화시킨 집단이라.. 10대여도 무섭고 2030이면 더 무섭다.
んふ
ヌートリアの平均寿命って何年なんですかね？
おぉー鮫嶋ちゃんに票が集まってるのちょっと意外かも？
鮫嶋「意外ってなんだ噛むぞ！」
RE: https://misskey.io/notes/a8mn53cu8zsh00fs
#我ながら天才的なキャラデザ4選
いいぞっ
三枚目:透け感のある衣装/四枚目:水着程度の肌露出.下半身が蛸の魔女
Edit: Demo posted! https://mastodon.social/@dansup/114630057595469062
Building the new Pixelfed compose UI for web, it solves nearly every issue I’m aware of!
Boost and like if you want me to post a demonstration ✨
