An homage to @evan@cosocial.ca 's past moustache 🙂
CC: @mapache@hachyderm.io @dansup@mastodon.social @matt@writing.exchange @vagrantc@floss.social @benpate@mastodon.social @ozoned#FediCon #FediCon2026 #FOSSY #FOSSY2026 #FireSideFedi
Remote
@reiver ⊼ (Charles) 
@reiver@mastodon.social
mastodon 4.8.0-nightly.2026-10-06I make things for #Fediverse #smallNet
Talk about #ActivityPub #FediDev #FediverseUX #P2P #Privacy #SpreadFediverse
I post #SciFiArt
Vlog at #AllYourBases #FinalForm
Work on #AssetFlow #FediCon #FediverseAcademy #FediverseCity #FingerProtocol #GreatApe #Microdon #ProToGo #SpaceMonkey
Life-cast at @reiver@firefish.lol
Code in #golang
I like to understand things. I like to make things.
The meaning of life — first survive, then reproduce 🌞
Formal b/g: comp sci, math, ai. Pro b/g: soft eng, ml, research
2453 Followers
1387 Following
50 Posts
Joined April 12, 2022
Web-Site:
Alt (Science Fedi):
Source-Code:
Google is apparently testing a new reCAPTCHA method that prompts you to turn on your device's camera to prove you are human by scanning your hands.
I assume this will eventually be mandatory, just like the current reCAPTCHA.
https://reclaimthenet.org/googles-new-recaptcha-wants-your-camera-access-and-21-points-of-your-hand
#DontBeEvil #Google #Privacy #Spying #Surveillance
Boosted by @fedicat@pc.cafe
Live Stream URL for the afternoon of day 2 of FediCon.
https://ubc.ca.panopto.com/Panopto/Pages/Viewer.aspx?id=c182c3eb-e0a7-41a3-9d27-b49c01766b07
#FediCon #FediCon2026 #FOSSY #FOSSY2026
OH: We should call it [the Fediverse] the "Sexy Social Web".
#FediForum #FediForum2026
The hash-tag to talk about Fediverse Payments is:
#AssetFlow
(It also includes transferring things that are non-money, too. Thus the generic name.)
#FediForum #FediForum2026
Boosted by @dansup@mastodon.social
RE: https://techhub.social/@fedicon/116688319685513603
See you there?
...
🌐 FediCon
📍 UBC campus, Vancouver (Canada)
🗓️ August 6th to 9th
🎟️ Get your FOSSY ticket, which gets you into FediCon:
https://2026.fossy.ca/attend/tickets/#FediCon #FediCon2026 #FOSSY #FOSY2026
"You don't make money with the Open Social Web, you make money because of the Open Social Web."
⸺ @j12t@j12t.social#FediForum #FediForum2026
And, it's done! Another fantastic FediForum! 🎉
#FediForum #FediForum2026
🙂
Replying to
I can think of different ways to support resumable uploads with ActivityPub, but — just to see what others are doing —
PeerTube seems to have resumable uploads already.
PeerTube seems to use this protocol for it:
https://github.com/kukhariev/node-uploadx/blob/master/proto.md
I like that it uses Content-Range in the protocol. I would have done the similar.
#ActivityPub #ActivityStreams #FediDev
RE: https://mastodon.social/@reiver/116494697560528377
I need a hoodie or sticker with:
"I'm on the Sexy Social Web"
🙂
#FediForum #FediForum2026
Quoting
OH: We should call it [the Fediverse] the "Sexy Social Web".
#FediForum #FediForum2026
Open quoted postReplying to
Just thinking out loud —
If we wanted to support resumable uploads in C2S API, then — we probably need some URL to upload the file chunks to.
…
When a user POST to their own outbox, the HTTP "201 Created" response will have a "Location" header that provides a URL.
Maybe that could be used as the upload URL.
Or, maybe the JSON-LD document at that URL might contain a URL under the "object" field that could be used as the upload URL.
Other options too
#ActivityPub #ActivityStreams #FediDev
Early Bird Tickets for FediCon (and FOSSY) are available today:
🎟️ https://2026.fossy.ca/attend/tickets/
Get them while they are still available.
#FediForum #FediForum2026 #FediCon #FediCon2026 #FOSSY #FOSSY2026
Up first on Day 3 of FediForum was @evan@cosocial.ca showing off tags.pub
#FediForum #FediForum2026 #TagsPub
❤️ Love FediForum —
Then you won’t want to miss FediCon this August ⚡
FediCon is an in-person gathering all about the Fediverse & the social web — the people, the ideas, and the future.
🎟️ Get your ticket:
https://2026.fossy.ca/attend/tickets/
📅 August 6–9, 2026
📍 UBC campus in Vancouver, BC, Canada
#FediCon #FediCon2026 #FediForum #FediForum2026 #FOSSY #FOSSY2026
Up fourth on Day 3 of FediForum is @mayel and @ivan showing off Bonfire.
#FediForum #FediForum2026 #bonfire
🌐 FediCon 2026 is coming up — and Early Bird (discounted) tickets are still available!
We want FediCon to be open and accessible, which is why there is also an affordable (Reduced fare) ticket option for those who want it.
Come be part of the conversations shaping the Fediverse and the future of the Social Web.
📅 August 6–9, 2026
📍 UBC campus, Vancouver, BC, Canada
🎟️ Get your FOSSY ticket here:
https://2026.fossy.ca/attend/tickets/
#FediCon #FediCon2026 #FOSSY #FOSSY2026 #FediDev #Fediverse
Replying to
RE: https://mastodon.social/@reiver/114002434643920102
4/
Related (in quote-boost).
#ActivityPub #ActivityStreams #FediDev
Replying to
There is a comparison that can be made between ActivityPub and Event-Sourcing.
3/
With ActivityPub, Activities are often applied to an object. That object gets assigned an ID in the form of a URL.
(And, by URL I mean URL, URI, IRI, etc.)
One doesn't have to read through all the Activities in an inbox, outbox, etc to get the final state of an object.
One can just get the JSON-LD document from the object's ID URL to get the final state.
#ActivityPub #ActivityStreams #EventSourcing #FediDev
Replying to
There is a comparison that can be made between ActivityPub and Event-Sourcing.
2/
With Event-Sourcing, you can "project" the events to get another (often more peformant) view of the data in the events.
Without having to incur the cost of having to read all the events to figure out the final state.
...
#ActivityPub #ActivityStreams #EventSourcing #FediDev
Replying to
@evan@cosocial.ca
I created an issue for it:
https://github.com/w3c/activitypub/issues/578
Let me know if it needs more information.
Replying to
@silverpill@mitra.social
Like I said, people are of course able to decide for themselves.
Including disagreeing with me.
...
But, I feel "building in open" should not be in the same place as specifications documenting standards.
RE: https://techhub.social/@fedicon/116500456409160887
🎟️ FediCon tickets are now on sale!
https://2026.fossy.ca/attend/tickets/
See you there?
#FediCon #FediCon2026 #FOSSY #FOSSY2026
Replying to
5/
People are of course able to decide for themselves which of №1, №2, and №3 they feel are acceptable scenarios for publishing specifications under organizational bodies (e.g., IETF) and community groups (e.g., FEP), but —
But, I feel only №1 and №2 are acceptable scenarios.
I.e., I feel that specifications published under organizational bodies (e.g., IETF) and community groups (e.g., FEP), should be DOCUMENTING not inventing.
...
Replying to
2/
An example of №1 is the (now old) finger-protocol. The finger-protocol existed at least 6 years before the first specification about the finger-protocol (IETF RFC-742) was first published.
I.e., the finger-protocol existed first, and the specification came much later.
...
@ozoned
Can you list out what you discovered were the missing features from the point of view of (I think you said) Twitch streamers.
#FediForum #FediForum2026
Up second on Day 3 of FediForum is Imani Maia showing the latest UX and UI improvements of Mastodon.
#FediForum #FediForum2026
RE: https://mastodon.social/@reiver/111179148569130717
A thread relevant for FediForum —
About Fediverse JoinFests — similar to Linux InstallFests from decades ago.
#FediForum #FediForum2026
Replying to
@evan@cosocial.ca
The "uploadMedia" endpoint?
I assumed resumable uploads would be incompatible with that API endpoint.
If it isn't incompatible, could use that.
Replying to
@evan@cosocial.ca
Done:
https://github.com/w3c/activitypub/issues/577
(Let me know if you need more information added to it.)
Replying to
3/
An example of №2 is the (now old) DVD format.
Prior to DVD, there were incompatible but similar technologies, such as: MMCD, and SD.
The same individuals who were behind MMCD, and SD (incompatible formats) got together (in a working-group) and agreed to interoperate.
DVD was the result of that.
And, the DVD specification(s) documented their agreements on how to interoperate.
...
Replying to
4/
An example of №3 is ERC-223.
ERC-223 was meant as a replacement for ERC-20. A single person invented ERC-223 without involving all the people who implemented or were using ERC-20.
ERC-223 was largely ignored.
Live Stream URL for FediCon morning:
https://ubc.ca.panopto.com/Panopto/Pages/Viewer.aspx?id=ab020a7c-7e24-4438-a5fc-b49c01762870
#FediCon #FediCon2026 #FOSSY #FOSSY2026
Replying to
6/
That doesn't mean inventing has no value. (It does.)
But, I feel that the repository of specifications under organizational bodies (e.g., IETF) and community groups (e.g., FEP) are not the place for them.
.
Replying to
@julian
I am asking the question because —
My understanding of JSON-LD (which could be mistaken) is that —
Because "preferredUsername" is (assumingly) a xsd:string, then "preferredUsernameMap" is automatically also valid.
(I.e., the *Map construct is a JSON-LD thing.)
.
It is again a tough choice on what to chose to go to for the first Unconference session (session 7) of Day 3 of FediForm, but — I am going to go to —
"Growth of the Open Social Web"
#FediForum #FediForum2026
Replying to
@liaizon
FWIW, people have created (multiple) alternatives to the ICANN Internet domain system.