video (@video@video.andyrush.net)
Video: Lunchtime Timelapse 1-26-17
Andy's Video Pub | original post: https://video.andyrush.net/video/lunchtime-timelapse-1-26-17/
#ActivityPub #Fediverse #ReclaimOpen25 #unf
Show Original Post
objects (@objects@crib.social)
@silverpill A testament to how slow most languages are compared to Rust! As surely your server will likewise be hammered with requests.
Still, this a design issue that must be fixed nonetheless in #Fediverse / #ActivityPub implementations, as they're not all written in Rust.
Show Original Post
m (@m@bookmarks.kvibber.com)
Website League
An island network using Fediverse technologies in allowlist-only mode.
#SocialNetwork #SocialNetworking #Fediverse #ActivityPub
Show Original Post
objects (@objects@epiktistes.com)
There are two big features in release v3.1.3 of Ktistec: auto-approve followers and a new image viewer.
Auto-approve followers is conceptually simple ("the server automatically sends an Accept activity when it receives a Follow activity") but it required extensive changes to some of the oldest code in the codebase: the inboxes and outboxes controllers. I refactored inbox and outbox side-effect processing into independent services, which made it possible to support side-effects like auto-approve follow (and also auto-follow back), without having to go through the controllers.
A more significant change for me personally was replacing the lightGallery image gallery (an external dependency) with my own implementation. It's not as slick, and not as full of features—I wrote it in two days—but it is fully free software, and that's important to me.
Added
- Add admin page for managing OAuth access tokens.
- Add support for auto-approve followers. (fixes #26)
- Add support for auto-follow back.
Fixed
- Prevent triggering actor refresh when user is anonymous.
Changed
- Replace "lightgallery" dependency with custom image viewer.
- Set OAuth access token expiry to 30 days (previously expired after 24 hours).
- Refactor inbox and outbox processing into dedicated processor services.
The OAuth changes set the groundwork for better support of the Mastodon API and the Fediverse clients that depend on it. Stay tuned!
#ktistec #fediverse #activitypub #crystallang
Show Original Post
display (@display@fed.sfl.pro.br)
Para quem curte #blambers um artigo, em #inglês, que explica a diferença entre as redes baseadas no #XMPP e no #ActivityPub
mov.im/community/pubsub.movim.…
Show Original Post
transicorn (@transicorn@mastodon.social)
@ikuturso It's late here and i need to shower and sleep but i appreciate the conversation! I genuinely am interested in #decentralization overall, whether it be #ActivityPub or #ATProto and imo i think both succeeding and bridging accounts between the two is likely the best overall future for #SocialMedia.
Show Original Post
transicorn (@transicorn@mastodon.social)
@ikuturso Sure, they are different there.
But the fact that #ActivityPub being so much older has never even come close to what #Bluesky is doing in user / account numbers is undeniable proof that overwhelmingly the average #SocialMedia user prefers Bluesky over #Mastodon and all ActivityPub projects aside from that.
Show Original Post
smallcircles (@smallcircles@social.coop)
Love it, congratulations! 😍
There are a number of #OpenScience related initiatives underway on the #ActivityPub fedi, some supported by @ngi @nlnet funding, which is great.
To avoid the pitfall of protocol decay on the app-centric #fediverse, coordination between these is necessary. So at https://coding.social we started a commons collective to discuss various cross-project concerns in a quest for alignment. Check out:
https://discuss.coding.social/c/commons-cocreation/sciencefed/98
https://matrix.to/#/#groundwork-matters:matrix.org
Show Original Post
transicorn (@transicorn@mastodon.social)
@ikuturso @keith @homegrown #Bluesky unlike #Mastodon / #ActivityPub is in its infancy and #Blacksky and other #ATProto based #PDS servers are now coming online.
That means they are only beginning to #decentralize, while ActivityPub is actively losing users #ATProto is working towards growing because of this.
That should obviously tell you something about where this is all going for the two networks.
Show Original Post
transicorn (@transicorn@mastodon.social)
As Of Right Now:
#Fediverse Stats
#Mastodon #Fedi #Stats #ActivityPub
Show Original Post
sciety (@sciety@fediscience.org)
Sciety is bridging preprints and open social networks. Our latest integration with @bonfire enables you to start a discussion on Sciety and federate anywhere; meeting researchers wherever they already are.
https://blog.sciety.org/bridging-preprints-and-the-fediverse/
#Fediverse #ActivityPub #NLnet
Show Original Post
notes (@notes@misskey.jayhsustudio.com)
💥 WD SMR 硬碟重大缺陷曝光！NAS RAID 重建災難、性能暴跌、集體訴訟全面解析 💥
2020 年，Western Digital（WD）因在 WD Red NAS 硬碟 中悄悄採用 SMR（疊瓦式磁記錄） 技術，卻未明確告知消費者，導致大規模使用者資料損毀、RAID 重建失敗的災難。
📉 根據專業媒體 ServeTheHome 實測：
RAID 重建時間：SMR 高達 120 小時以上（CMR 約 24 小時）
隨機寫入性能：SMR 僅 0.3 MB/s，比 CMR 慢 75%+
這些問題讓 NAS 用戶面臨 性能崩潰、重建失敗與資料遺失 的嚴重風險。
📄 詳細解析（含法院文件與實測數據）：
👉 WD SMR 硬碟嚴重缺陷導致集體訴訟：NAS 性能災難與 RAID 重建失敗完全解析
https://2025.data-recover.com.tw/news/WD-SMR%E7%A1%AC%E7%A2%9F%E5%9A%B4%E9%87%8D%E7%BC%BA%E9%99%B7%E5%B0%8E%E8%87%B4%E9%9B%86%E9%AB%94%E8%A8%B4%E8%A8%9F-NAS%E6%80%A7%E8%83%BD%E7%81%BD%E9%9B%A3%E8%88%87RAID%E9%87%8D%E5%BB%BA%E5%A4%B1%E6%95%97%E5%AE%8C%E5%85%A8%E8%A7%A3%E6%9E%90
⚠️ 請大家馬上檢查自己的 NAS 或桌上型硬碟！
如果你使用 WD Red、WD Blue、或同型號 SMR 機種，請立即備份資料 ⚡
預防資料遺失才是最好的防禦！
#WD #WesternDigital #SMR #CMR #NAS #RAID #DataLoss #Storage #Backup #TechNews
#WD硬碟 #SMR問題 #NAS災難 #資料備份 #集體訴訟 #資料救援 #硬碟警報 #備份很重要
#データ損失 #WD #ハードディスク #SMR問題 #NASトラブル #RAID再構築失敗 #バックアップ #注意喚起
#Fediverse #Misskey #Mastodon #ActivityPub #Tech #StorageAlert #DataRecovery #news
Show Original Post