Mastodon

naturzukunft(3/3) the demo app is build with: <a href="https://mastodon.social/tags/springboot" class="mention hashtag" rel="tag">#springboot</a> <a href="https://mastodon.social/tags/thymeleaf" class="mention hashtag" rel="tag">#thymeleaf</a> <a href="https://mastodon.social/tags/htmx" class="mention hashtag" rel="tag">#htmx</a> <a href="https://mastodon.social/tags/tailwindui" class="mention hashtag" rel="tag">#tailwindui</a> but there is also the possibility to create another app, that is using the <a href="https://mastodon.social/tags/activitypub" class="mention hashtag" rel="tag">#activitypub</a> <a href="https://mastodon.social/tags/C2S" class="mention hashtag" rel="tag">#C2S</a> API. <a href="https://mastodon.social/tags/activitypubdev" class="mention hashtag" rel="tag">#activitypubdev</a> <a href="https://mastodon.social/tags/rdfpub" class="mention hashtag" rel="tag">#rdfpub</a>

0x1C3B00DANextGen ActivityPub Social API NextGen ActivityPub Social API #activitypub #c2s <a href="https://socialhub.activitypub.rocks/t/nextgen-activitypub-social-api/4733/2" rel="nofollow noopener" translate="no" target="_blank">https://socialhub.activitypub.rocks/t/nextgen-activitypub-social-api/4733/2</a>

Tom's Bookmarks<a href="https://github.com/andstatus/andstatus" rel="nofollow noopener" target="_blank">AndStatus</a> Open Source client that supports the ActivityPub C2S API

LaxystemShould servers embed externally-managed data, or reference it via a URL when speaking with clients?Referencing will need a way to authorize a client on remote servers, and will result in more packets; Embedding will result in lost data, useless re-serialization (wasted resources), increased reliability and trust on the home server (man-in-the-middle attacks), and larger packets.<a href="https://tech.lgbt/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> <a href="https://tech.lgbt/tags/C2S" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2S</a> <a href="https://tech.lgbt/tags/Fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fediverse</a>

django<a href="https://honk.tedunangst.com/u/tedu" class="u-url mention" rel="nofollow noopener" target="_blank">@tedu</a> predictably this fails in Mastodon but works in the <a href="https://social.coop/tags/c2s" class="mention hashtag" rel="nofollow noopener" target="_blank">#c2s</a> thing I’m building

naturzukunft<a href="https://mastodon.social/tags/Oauth2" class="mention hashtag" rel="tag">#Oauth2</a> and <a href="https://mastodon.social/tags/activitypub" class="mention hashtag" rel="tag">#activitypub</a> <a href="https://mastodon.social/tags/c2s" class="mention hashtag" rel="tag">#c2s</a> gives me sleepless nights ;-)

mariusThis usage is meant for connecting to the local storage (disk, database,etc) that is used by the projects above.However with just minimal changes it can be converted into a full blown fediverse TUI client that can connect to any instance that supports the Client to Server part of the ActivityPub protocol.<a href="https://metalhead.club/tags/C2S" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2S</a> <a href="https://metalhead.club/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a>

RayvenMXI have been thinking about processing the Create activity. My <a href="https://mastodon.world/tags/NoSQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#NoSQL</a> <a href="https://mastodon.world/tags/CosmosDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#CosmosDB</a> stores/indexes json documents. I have a Message collection that holds messages posted on the platform but I figured, why not hold the raw object like a Note and rebuild the front end to be an ActivityPub <a href="https://mastodon.world/tags/C2S" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2S</a>. This is a wonderful idea, but I think I'll save that for another time, perhaps a quality C2S would be compatible with my <a href="https://mastodon.world/tags/activitypub" class="mention hashtag" rel="nofollow noopener" target="_blank">#activitypub</a> instance. I think it will be easier to convert to my format and back again.

Damian Yerrick<a href="https://hackers.town/@inversephase" class="u-url mention" rel="nofollow noopener" target="_blank">@inversephase</a> "MSTDN: Fediverse Developer Network" sounds like a website that documents ActivityPub and related client-to-server (<a href="https://peoplemaking.games/tags/c2s" class="mention hashtag" rel="nofollow noopener" target="_blank">#c2s</a>) protocols. Imagine <a href="https://peoplemaking.games/tags/MDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#MDN</a> for <a href="https://peoplemaking.games/tags/FediDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#FediDev</a>.

Gi7w0rm<a href="https://infosec.exchange/tags/WormsWeeklyIoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#WormsWeeklyIoC</a> have been released. This week features <a href="https://infosec.exchange/tags/RecordBreaker" class="mention hashtag" rel="nofollow noopener" target="_blank">#RecordBreaker</a>/#racconv2, <a href="https://infosec.exchange/tags/Amadey" class="mention hashtag" rel="nofollow noopener" target="_blank">#Amadey</a> <a href="https://infosec.exchange/tags/Botnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Botnet</a>, and a rework of my <a href="https://infosec.exchange/tags/Rhadamanthys" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rhadamanthys</a> <a href="https://infosec.exchange/tags/Stealer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Stealer</a> <a href="https://infosec.exchange/tags/IoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IoC</a> gathering. Find all indicators here: <a href="https://github.com/Gi7w0rm/MalwareConfigLists/tree/main" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Gi7w0rm/MalwareConfigLists/tree/main</a>The proudest release this week is 85 new <a href="https://infosec.exchange/tags/Rhadamanthys" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rhadamanthys</a> <a href="https://infosec.exchange/tags/Stealer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Stealer</a> <a href="https://infosec.exchange/tags/C2s" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2s</a> not prior known to <a href="https://infosec.exchange/tags/Threatfox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Threatfox</a>. I invite you all to vet those to make sure my new method of gathering works correctly :) Together with this week's <a href="https://infosec.exchange/tags/Raccoon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Raccoon</a> <a href="https://infosec.exchange/tags/IoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IoC</a>, they are all in <a href="https://infosec.exchange/tags/OTX" class="mention hashtag" rel="nofollow noopener" target="_blank">#OTX</a> as well.<a href="https://otx.alienvault.com/user/@Gi7w0rm/pulses" rel="nofollow noopener" translate="no" target="_blank">https://otx.alienvault.com/user/@Gi7w0rm/pulses</a>Interesting side note: One of the <a href="https://infosec.exchange/tags/IoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IoC</a> for <a href="https://infosec.exchange/tags/Rhadamanthys" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rhadamanthys</a> <a href="https://infosec.exchange/tags/Stealer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Stealer</a> is IP: 104.156.149[.]126.This IP has been attributed as an Indicator of <a href="https://infosec.exchange/tags/Sandworm" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sandworm</a> / GRU Unit 74455 by Google: <a href="https://blog.google/threat-analysis-group/ukraine-remains-russias-biggest-cyber-focus-in-2023/" rel="nofollow noopener" translate="no" target="_blank">https://blog.google/threat-analysis-group/ukraine-remains-russias-biggest-cyber-focus-in-2023/</a>Stay safe out there <3

Alek<a href="https://mastodon.social/@kidehen" class="u-url mention" rel="nofollow noopener" target="_blank">@kidehen</a> I dont know about <a href="https://101010.pl/tags/c2s" class="mention hashtag" rel="nofollow noopener" target="_blank">#c2s</a>, can you please explain a bit more? Thanks!

Kingsley Uyi Idehen<a href="https://101010.pl/@tarkowski" class="u-url mention">@tarkowski</a>,"But he also openly declares that “Benevolent Dictator for Life” is his preferred governance model. Which is worrying, because one person should not be making decisions about a network used by millions of people. And participatory governance should be more than collective petitions to a “benevolent dictator”Isn't required when open standards exist. I don't understand the reluctance re implementing the missing <a href="https://mastodon.social/tags/C2S" class="mention hashtag" rel="tag">#C2S</a> aspect of <a href="https://mastodon.social/tags/ActivityPub" class="mention hashtag" rel="tag">#ActivityPub</a>./cc <a href="https://mastodon.social/@Gargron" class="u-url mention">@Gargron</a> <a href="https://mastodon.social/@nilaypatel" class="u-url mention">@nilaypatel</a>

Kingsley Uyi Idehen<a href="https://social.technoetic.com/@steve" class="u-url mention">@steve</a>,Yes, I understand that. We (<a href="https://mastodon.social/@openlink" class="u-url mention">@openlink</a>) have also built a generic <a href="https://mastodon.social/tags/ActivityPub" class="mention hashtag" rel="tag">#ActivityPub</a> client and server -- hence my concern about why this isn't a <a href="https://mastodon.social/@Mastodon" class="u-url mention">@Mastodon</a> option. Why not add consistent ActivityPub protocol support on the <a href="https://mastodon.social/tags/C2S" class="mention hashtag" rel="tag">#C2S</a> front alongside what exists on the <a href="https://mastodon.social/tags/S2S" class="mention hashtag" rel="tag">#S2S</a> front. This can all co-exist with the Mastodon native <a href="https://mastodon.social/tags/API" class="mention hashtag" rel="tag">#API</a> thereby increases choice on the front and backend side of thing re the burgeoning <a href="https://mastodon.social/tags/Fediverse" class="mention hashtag" rel="tag">#Fediverse</a> 😀 /cc <a href="https://social.sdf.org/@tallship" class="u-url mention">@tallship</a> <a href="https://mastodon.social/@Gargron" class="u-url mention">@Gargron</a> <a href="https://mstdn.social/@peepstein" class="u-url mention">@peepstein</a> <a href="https://mastodon.social/@blaine" class="u-url mention">@blaine</a> <a href="https://mastodon.social/@atomicpoet" class="u-url mention">@atomicpoet</a>

HelgeThe question about Client To Server can be boiled to: Should ActivityPub Servers convert the json-ld objects making up the Activity in their own proprietary format? If you say yes, you get Mastodon. If you say no, you get a Client To Server implementation. Once people start using ActivityPub for things Mastodon cannot convert, you will start missing stuff on it. You already miss me posting strange test activities, you will also miss me sending a Read of the next Recipe, I look up on the internet and then convert into an Object using <a href="https://umai.noeldemartin.com/" rel="nofollow noopener" target="_blank">Umai</a>. However, that will be just me being me !!!

LisPi<a href="https://outerheaven.club/users/vyivel" class="u-url mention" rel="nofollow noopener" target="_blank">@vyivel</a> There seems to be a significant lack of implementations that bother to correctly implement it in all of its required parts for usefulness.<a href="https://activitypub.rocks/implementation-report/" rel="nofollow noopener" target="_blank">https://activitypub.rocks/implementation-report/</a>The few that apparently do it right I've never seen in the wild.<a href="https://mastodon.top/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> <a href="https://mastodon.top/tags/C2S" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2S</a>

Sebastian Lasse<a href="https://digitalcourage.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> <a href="https://digitalcourage.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fediverse</a> <a href="https://digitalcourage.social/tags/C2S" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2S</a> <a href="https://digitalcourage.social/tags/wikidata" class="mention hashtag" rel="nofollow noopener" target="_blank">#wikidata</a> <a href="https://digitalcourage.social/tags/wikipedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#wikipedia</a> <a href="https://digitalcourage.social/tags/wikibase" class="mention hashtag" rel="nofollow noopener" target="_blank">#wikibase</a> The last week we finished the first version of the ActivityPub “Atlas Cache” which is a huge ActivityVocabulary Collection with all the Infos about well known Places on Planet Earth (1.8 mio.) It would be used as a base for a very huge project and for a cool transport thing. But it is fully Open Source. Small question: Do independent git hosters have size restrictions and could I buy more storage? Recommendations? [we need to move from the one]Big question: How would you think about enhancing our ActivityPub _Client_ with an ability to proxy wikidata. <a href="https://github.com/redaktor/mediaproxy" rel="nofollow noopener" target="_blank">https://github.com/redaktor/mediaproxy</a>You could search and federate wikipedia if it knows which main `type` in AP it is and then sign the object from your client and use it as template or federate it. We can say in the Object what it describes from wikidata. Since any wikipedia page has a wikidata item, we can federate wikipedia. Your instance would just need to sync back.

LisPi<a href="https://stop.voring.me/@thatonecalculator" class="u-url mention" rel="nofollow noopener" target="_blank">@thatonecalculator</a> <a href="https://mastodon.social/@gwynnion" class="u-url mention" rel="nofollow noopener" target="_blank">@gwynnion</a> Well hey, points for both Pleroma/Akkoma & *Key getting it right.They also got <a href="https://mastodon.top/tags/C2S" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2S</a> support right, unlike <a href="https://mastodon.top/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a> (which intentionally fails to implement it).

LisPi<a href="https://tearoom.tearmoon.com/@mia" class="u-url mention" rel="nofollow noopener" target="_blank">@mia</a> So much of the ecosystem expecting <a href="https://mastodon.top/tags/MastoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#MastoAPI</a> instead of <a href="https://mastodon.top/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> <a href="https://mastodon.top/tags/C2S" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2S</a> is quite obnoxious indeed (and that's made worse by <a href="https://mastodon.top/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a>'s support of <a href="https://mastodon.top/tags/C2S" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2S</a> being fundamentally & voluntarily/intentionally crippled & broken).

LisPi<a href="https://mastodon.social/@shoq" class="u-url mention" rel="nofollow noopener" target="_blank">@shoq</a> <a href="https://mastodon.social/@Mention" class="u-url mention" rel="nofollow noopener" target="_blank">@Mention</a> Technically, that's just a Twitter mentions-like problem Mastodon & other implementations imported.You can perfectly well create <a href="https://mastodon.top/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> Activity objects with such text without adding the names to to & cc fields, but Mastodon doesn't support <a href="https://mastodon.top/tags/C2S" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2S</a> so...Personally my ideal client for <a href="https://mastodon.top/tags/Fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fediverse</a> is nearly indistinguishable from the client one would use for <a href="https://mastodon.top/tags/Usenet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Usenet</a>

LisPi<a href="https://cdrom.tokyo/users/ZalophuszJaponicus" class="u-url mention" rel="nofollow noopener" target="_blank">@ZalophuszJaponicus</a> <a href="https://mastodon.grin.hu/@grin" class="u-url mention" rel="nofollow noopener" target="_blank">@grin</a> <a href="https://mk.absturztau.be/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@delta</a> Very aesthetic, but does it the other problems mentioned?It does at least address the incomplete/mostly-missing <a href="https://mastodon.top/tags/C2S" class="mention hashtag" rel="nofollow noopener" target="_blank">#C2S</a> <a href="https://mastodon.top/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> implementation that <a href="https://mastodon.top/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a> suffers from...

Recent searches

Search options

Administered by:

Server stats:

#c2s