article (@article@aptest1.ocus.top)
Another test article for federation - this time with content
This is a test 3 article to make sure that the #activitypub integration works in #madblog.
Let's see if @blacklight@mastodon.online gets mentioned!
And let's add some math:
And a Mermaid graph - because why not:
And a code block:
print("Hello, world!")
And a big shoutout to @fabio@manganiello.eu too!
Show Original Post
article (@article@aptest1.ocus.top)
Another test article for federation - this time with content
This is a test 2 article to make sure that the #activitypub integration works in #madblog.
Let's see if @blacklight@mastodon.online gets mentioned!
And let's add some math:
And a Mermaid graph - because why not:
And a code block:
print("Hello, world!")
And a big shoutout to @fabio@manganiello.eu too!
And @nemo@mas.to give me a shout if you read me!
Show Original Post
article (@article@aptest1.ocus.top)
Another test article for federation - this time with content
This is a test 2 article to make sure that #activitypub integration works.
Let's see if @blacklight@mastodon.online gets mentioned!
And a big shoutout to @fabio@manganiello.eu too!
Show Original Post
r (@r@fed.brid.gy)
If you consider how many people are passive "consumers" of news and large "accounts" are only interested in distribution, serious RSS clients would seem like the only workhorse we ever really needed
Fancy #atproto and #activitypub protocols are a sort of RSS++, much ado for not all *that* much gain
RE: https://bsky.app/profile/did:web:pluralistic.net/post/3mgigzad4bl2l
Show Original Post
mariusor (@mariusor@metalhead.club)
Resurrected the nodeinfo helper service for the #FedBOX generic #ActivityPub service.
Hopefully this will lead to better integration with other federated services, but I find very little practical use for these hamfisted .well-known APIs integrated into the fediverse...
Show Original Post
johan (@johan@tilde.zone)
Посмотрите, какую федиверсину ребята прилят!
Насколько я понял, они хотят сделать мобильный однопользовательский #ActivityPub-сервер+клиент в одном флаконе, который будет общаться с остальными по этому протоколу, но, не имея белого IP, использовать для этого их сервис-релей, подключаясь через WebRTC. При этом все посты, картинки и прочая медия — хранится локально, можно иметь собственный домен и использовать любой такой релей.
Выглядит круто?
Только я не нашел, как скачать .apk
Show Original Post
CartyBoston (@CartyBoston@mastodon.roundpond.net)
When I wanted to learn #activitypub I downloaded #mastodon and used it as a reference, I had never coded in Ruby.
So thank you for that Eugen and team.
Anyway I built a console to watch all of the messages on my instance fly by, it was *fascinating*, one could see instantly why activitypub is the one.
It was a while ago, I think the code resides on a MacBook that I will soon decide is e-waste.
That's my story, over and over.
Show Original Post
smallcircles (@smallcircles@social.coop)
When looking through the lens of Social experience design we can say that the fediverse-we-have and the #ActivityPub social network promise in the W3C specs, have become diverged to the extent they are hard forks.
A #SX solution is said to exist as soon as you can write it down on a sticky note in the form of a vision, need, objective, or solution.
The AS/AP fediverse sticky note reads: "The future of social networking is decentralized".
The fediverse-we-have note reads: "Decentralized microblogging"
Besides that both sticky notes express a tech focus, exist in the technosphere not sociosphere, they express no vision.. A place where we want to be, and why. There is complete misconception both on technical, let alone social direction, and that leads to endless confusion and again those mismatched expectations.
App devs now try to hammer their apps onto "Decentralized microblogging" in hopes "future of social networking" somehow emerges. That is unlikely.
Show Original Post
nick (@nick@hhmx.de)
I send you this post as answer using my own #ActivityPub based #Fediverse server software, that is totally hand-coded by myself... 😉
@tante@tldr.nettime.org @emilymbender@dair-community.social @cwebber@social.coop
Show Original Post
NfNitLoop (@NfNitLoop@mastodon.social)
RE: https://indieweb.social/@laurenshof/116103545853411360
This thread talks about going back to an #ActivityPub users's home server to validate a user's content, because you can't trust that the event you got for it is unmodified.
But you can't trust what the home server tells you the content of the message is either! There's nothing stopping a home server from serving a modified version of your content every time it's requested, say, to inject ads into it, or censor bits it doesn't like.
Or to just completely fabricate new content from you.
Show Original Post
apps (@apps@toot.fedilab.app)
RE: https://mastodon.social/@HolosSocial/116183535316096143
Some news from #HolosSocial development. The latest release moves media processing to the device. Videos are transcoded locally before upload. Users can store media on their own S3 or WebDAV server, and the resulting URLs are used directly in #ActivityPub activities. The relay server handles neither transcoding nor media storage. Each user brings their own resources to the #Fediverse.
Show Original Post
HolosSocial (@HolosSocial@mastodon.social)
Here is the new feature that allows you to save your #ActivityPub media in your own cloud, giving you more sovereignty over your data. Your media stays available even when your device is offline.
Show Original Post