@PalePimp@poa.st @boilingsteam@mastodon.cloud I could definitely see a path there. That scares the hell out of me and I hope you're wrong. But definitely possible. Thank you for sharing.
Father of two, husband, gamer, lover of free software, and willing teacher.
I reserve the right to be wrong about everything.
Founder & CEO BT Free 501(c)3 Public Charity
Donate to BT Free - https://givebutter.com/btfree
Proton Referral - https://pr.tn/ref/V1SZDGNS
Hetzner Referral - https://hetzner.cloud/?ref=X83HFgQjXhR7
@boilingsteam@mastodon.cloud it'll be interesting to see how that's supposed to work. I'm not in NY so I don't fall under those laws. But I can just grab a new OS from somewhere else as I run Linux and GrapheneOS. Any third party that houses that info will be a MASSIVE target for hackers. I think these things are years away from being implemented and practical. Just because a law exists, doesn't mean it's enforceable. It'll definitely be interesting to watch. And states will be sued and it'll take years to move through courts as this is entirely new ground. So we'll have to see how they're classifying the internet and how they justify it.
I'll say this though, I'm against this kind of thing personally, but I think all of these people are attempting g to do anything they can to dig us out of the current pit we're in. The road to hell is paved with good intentions though.
@PalePimp@poa.st @boilingsteam@mastodon.cloud definitely is a slippery slope. But if I run my own and you run your own, plus with the end to end encryption for DMs in the works, they'd need more than just these laws to get access to either of our servers. And anything public In post, well it's public.
@ozoned its very easy to pass changes once the first step is taken. You start with v1, people dont complain because there are still some workarounds and give it a few years and you won't notice they tight things up progressively and by that time it will be too late.
@boilingsteam@mastodon.cloud potentially. I'm an idealist and I'm very biased in favor of the Fediverse, but I have a difficult time believing they'd want to enforce this against my running my own for my own family, let alone them actually being able to enforce this. It absolutely could impact big open platforms like mastodon.social or even my own tubefree.org. but this is a reaction to big tech getting us into this position and finding ways to reduce their power.
@boilingsteam@mastodon.cloud yes, but that's with everything. Can you expand?
So, I've been seeing news about all of the age verification laws, and I see a LOT of scared people.
Here's the way I see it, and I'd like to honestly get people's opinion, I think they're dumb, HOWEVER, I think the laws give ud a HUGE opportunity. YOU can run your own platform and you can verify your own age. Same with your family, same with your community. This gives us power.
Are people just going to hand over their IDs to Facebook? Probably, but it won't be me. And there will be massive fraud and issues and this will force legal degradation of centralized platforms.
Thoughts?
Good day all! Upcoming episode of Fireside Fedi!
The #livestream will be on: stream.firesidefedi.live
Special Guest: @lich_silvae@masto.fediverse.games
Passionate about Ethnomusicology, Occultism, Nature, Cooking, and Social Welfare. Topics commonly include subjects not suitable for people under 18. Minors do not follow.
So don't miss it!
It will happen on 06 March 2026 at 15:00 US Eastern Time ( UTC-5 )
If by any ungodly chance you miss the show:
#PeerTube ( #VOD ): tubefree.org/@firesidefedi
freestreamers.btfree.org/eve...
#firesidefedi #fediverse #fedi #interview #freesoftware #opensource #userfreedom #freedom #resistance
Assembly Bill No. 1043 of the State of California forces every operating system vendor to implement an age verification system on "account setup". I guess it's time to break the text of it down and rant a pissed-off rant about how stupid it is. Shall we?
On the #Fediforum #GrowingTheOpenSocialWeb #unconference right now. And the diversity, the experiences in just the first 30 minutes is incredible. We have so many folks from all types of different backgrounds learning and SHARING with everyone else.
This is absolutely incredible being on this ride with you. Thank you all so much.
@_elena@mastodon.social @logan@social.logal.dev @dnpdame@mastodon.social It was nice. We all just hung out and had a drink, talked, then walked to an Italian restaurant and had dinner. Just 4 of us. But lots of fun getting out to talk with folks. 😊
@logan@social.logal.dev @dnpdame@mastodon.social and I are at Sir Walter Coffee in downtown #Raleigh for anyone interested in joining us for a #Fediverse #MeetUp .
Back corner.
Just a reminder to anyone in the #Raleigh #NC area TODAY, Feb 28th 2026, we're having a #Fediverse #MeetUp at Sir Walter Coffee, E. Davies St. Meeting there around 1800 until whenever folks care to wrap up.
NodeBB v4.9.0 — A Whole New /world!
Hello all!
(Sorry, I could not resist with the title
)
Today we are releasing NodeBB v4.9.0, on a Friday, toward the end of the day, because we like having our weekends ruined.
As usual, we recommend you update to this stable version of NodeBB, not least because it fixes a federation issue accidentally introduced last month.
There are a bunch of new features and usability improvements here, for both end users and admins. Federation improvements abound, as well as a few moderation upgrades. As usual, we fixed a ton of bugs, and even a couple open issues from the 2010s 
Here is a list of the changes and new features you should expect to see! [...]
Hello all!
(Sorry, I could not resist with the title
)
Today we are releasing NodeBB v4.9.0, on a Friday, toward the end of the day, because we like having our weekends ruined.
As usual, we recommend you update to this stable version of NodeBB, not least because it fixes a federation issue accidentally introduced last month.
There are a bunch of new features and usability improvements here, for both end users and admins. Federation improvements abound, as well as a few moderation upgrades. As usual, we fixed a ton of bugs, and even a couple open issues from the 2010s 
Here is a list of the changes and new features you should expect to see! [...]
New "World" page
/world has been updated so that is closer to a feed-reader than a topic list. While I will continue to iterate on this design over time to better promote topics, I am hoping that this proves to be more accessible of an interface compared to the old topic listing.
Your watched/tracked remote categories will be listed in a sidebar (hidden behind a drawer on mobile views) for easy access.
The default view ("Latest") continues to be a list of content from people you follow, and content shared by those same people. The other view ("Popular") shows unconstrained content, and can include content from people you don't follow.
Remote topics now unavailable to guests
After an Alibaba bot was recorded mercilessly scraping a lot of the public content served up by NodeBB, we decided to restrict access to that content to registered users.
While this would normally mean that "View Original URL" would stop working from other federates sites (since visitors are usually guests), we have added an exclusion to this logic that will continue to serve up the content to guests if at least one local user has commented on the topic.
UX change for composer and chats
@baris worked on a number of usability fixes that make the experience of using our post composer and chat interface much better. For the longest time we had issues with the composer not properly resizing when mobile keyboards opened.
Composing and replying should work much better now that we are using the latest CSS and javascript tooling to properly detect visual viewport changes.
Better notifications
@baris also updated the notifications system so that bodyLong, which usually contains post text, is now sent with all notifications. This should increase the usability of notifications (both via web, email, or push).
Cross-posting privilege
A previous release introduced the ability to cross-post content into local categories. This functionality can now be gated behind a privilege at the category level.
Guest call-to-action
@baris introduced a new guest "call-to-action" banner that will help guide guests toward registering a new account to contribute to your community 
Title-less topics
As part of the changes to /world, we also allow the creation of topics without a title. If you don't pass in a title, we will generate one for you based on the first sentence in your post. The same title generation logic was applied to remote content in the past, and now it also applies to local content.
This also means you can use the /world page to just fire off something quickly without having to do the hard work of thinking up a title. You're welcome 
Opportunistic backfill
Now that the fediverse's largest implementor, Mastodon, supports context, which enables backfill, we have implemented an opportunistic backfill feature that will check for new replies when you enter a topic. It'll also regularly check the top most popular remote topics known by the instance for new posts.
Reasons
You can now set up a recurring list of "reasons", which you can invoke on certain moderation actions. These custom reasons can be used when a user is banned, muted, or on post queue rejection.
You can set up these reasons from ACP > Manage > Users > (Gear) > Manage Custom Reasons

Registration queue now applies for SSO plugins
This issue, open since 2016 is finally fixed. SSO plugins don't automatically bypass the registration queue anymore. This was a common vector for spammers to bypass registration limitations.
Additional features and bug fixes
- An improvement to auto-installation of plugins
- Removed many remote tids and pids stored in the db for no reason (thanks @baris)
- A regression that caused nodebb-to-nodebb federation to fail (and possibly many others)
- Notifications can now be passed custom icons
- ACP privilege selector now no longer shows remote categories
- Improvements to mentions to better handle periods at end of sentences, or names within names
- All cached used internally are now exposed in the admin panel for better management.
- Sitemap cache duration is now configurable
- Infinite scrolling now works on
/world - Slug generation errors when you mixed and matched
-and. - Topic pruning applies to all remote cids now, not just cid -1
- Chats list updated properly now, when new messages are received, chat messages now properly backfilled upon reconnection
- NodeBB now federates Delete on both deletion and purge
For the full changelog, please take a look at the closed issues list for this milestone, or take a gander at the much less impressive CHANGELOG.md in our repository root.
Just a reminder to anyone in the #Raleigh #NC area tomorrow, Feb 28th 2026, we're having a #Fediverse #MeetUp at Sir Walter Coffee, E. Davies St. Meeting there around 1800 until whenever folks care to wrap up.
@ozoned @nicol Yes, P2P, but the platform's settings calls it "sharing system": https://open.movie/w/rdot9DoygXTXzLM4ZnJjTf?modal=quick-settings
@candide@vis.social @nicol@social.coop No. That's not what I'm thinking of. I'm thinking of Video Redundancies. Do you have that enabled and another Peertube is serving the content instead of fetching from yours?
@JenJen@mastodon.art is running a Kickstarter for some AWESOME, nsfw, glitter stickers if folks want to support a creator on the Fediverse.
@candide@vis.social @nicol@social.coop "turned off the sharing system" do you mean the P2P? I had that on mine by default, and while I love the idea, as well as others being able to replicate videos through Peertube, we found that it causes too many issues. You can't count on the quality of connection of anyone else and then folks pulling from flakey connections only see issues and think it's the video.
Also I was wrong about the follow. I hadn't followed open.movie on my tubefree.org. I do now though! 😄
@nicol@social.coop @candide@vis.social i can watch the videos without issue.
I'd always suggest federating your Peertube, for instance my TubeFree.org asked to follow yours, but I don't think it it would solve this issue.
I'm guessing a client side issue or ISP block. Maybe try a VPN or switching to cellular or WiFi.
Federated End-to-End Encrypted Messaging is Coming Soon
One of the Social Web Foundation's initiatives for improving ActivityPub will soon be a reality for the network.
Support for end-to-end encrypted messaging in ActivityPub has been stated as a long-term goal by the Social Web Foundation, but the network might be gaining support for it sooner than anyone expected. Ben Pate, the lead dev of Emissary, posted to the network earlier this week:
Since January, Bonfire and Emissary have been working on true E2EE in ActivityPub, using the MLS protocol — which is a successor to Signal protocol with better support for very large groups.
Anyway, here’s today’s progress video of where I am. Here’s what works: exchanging public keys, creating groups, sending/receiving messages and replies, and realtime notifications.
There’s a lot more to do. We’re planning on general availability in June, so right now we’re about 1/3 of the way into the project.
Funding for this feature was secured through the Sovereign Tech Fund, with leadership provided by the Social Web Foundation. Emissary and Bonfire are both working on this project, and are due to provide deliverables by June 2026. The result of this work will eventually provide a clear standard in a future version of the ActivityPub protocol spec. A December 2025 draft of the existing spec can be read here.
A Quick Demo
Ben was nice enough to record a quick demo for people to get a visual representation of where things are currently, and what support for encrypted messaging looks like.
https://clip.place/w/ajgJ5Hi69bbbxHCK3nXNdj
What’s Next?
For now, implementers are working hard to iron out wrinkles and resolve outstanding points of ambiguity. The demo above already showcases a working product, although a number of client-side bells and whistles could be added for things like read receipts, native support for different content types, and autocomplete for looking up contacts.
The spec currently appears to propose an idea that client implementers could leverage end-to-end encryption through a future version of the ActivityPub API. While the proposal spec is relatively fleshed-out, it would benefit greatly from community feedback.