Search
289 results for “thisismissem”
-
-
-
-
-
Yes, I agree.
I think the important thing is that we get in a position where the ecosystem as a whole is able to make rational technology decisions that make the most sense and which fulfill clear objectives. But in order to be able to do that we first have to have a clear picture of where we are today, what we have established, where pain points are, and where we want to be tomorrow. Then work strategically along a shared (technnology) vision on ecosystem level, top-down. While individual developers drive experiment and introduce technology innnovations to be incorporated, bottom up.
Who dares imagine the fediverse of 5 years in the future. Or 10. Or ...
Who dares to #ReimagineSocialNetworking?
-
Yes, I agree.
I think the important thing is that we get in a position where the ecosystem as a whole is able to make rational technology decisions that make the most sense and which fulfill clear objectives. But in order to be able to do that we first have to have a clear picture of where we are today, what we have established, where pain points are, and where we want to be tomorrow. Then work strategically along a shared (technnology) vision on ecosystem level, top-down. While individual developers drive experiment and introduce technology innnovations to be incorporated, bottom up.
Who dares imagine the fediverse of 5 years in the future. Or 10. Or ...
Who dares to #ReimagineSocialNetworking?
-
Yes, I agree.
I think the important thing is that we get in a position where the ecosystem as a whole is able to make rational technology decisions that make the most sense and which fulfill clear objectives. But in order to be able to do that we first have to have a clear picture of where we are today, what we have established, where pain points are, and where we want to be tomorrow. Then work strategically along a shared (technnology) vision on ecosystem level, top-down. While individual developers drive experiment and introduce technology innnovations to be incorporated, bottom up.
Who dares imagine the fediverse of 5 years in the future. Or 10. Or ...
Who dares to #ReimagineSocialNetworking?
-
Yes, I agree.
I think the important thing is that we get in a position where the ecosystem as a whole is able to make rational technology decisions that make the most sense and which fulfill clear objectives. But in order to be able to do that we first have to have a clear picture of where we are today, what we have established, where pain points are, and where we want to be tomorrow. Then work strategically along a shared (technnology) vision on ecosystem level, top-down. While individual developers drive experiment and introduce technology innnovations to be incorporated, bottom up.
Who dares imagine the fediverse of 5 years in the future. Or 10. Or ...
Who dares to #ReimagineSocialNetworking?
-
Yes, I agree.
I think the important thing is that we get in a position where the ecosystem as a whole is able to make rational technology decisions that make the most sense and which fulfill clear objectives. But in order to be able to do that we first have to have a clear picture of where we are today, what we have established, where pain points are, and where we want to be tomorrow. Then work strategically along a shared (technnology) vision on ecosystem level, top-down. While individual developers drive experiment and introduce technology innnovations to be incorporated, bottom up.
Who dares imagine the fediverse of 5 years in the future. Or 10. Or ...
Who dares to #ReimagineSocialNetworking?
-
I just responded in the other thread about #ForgeFed way of dealing with Issues and PR's, emphasizing the actor model in the #ActivityPub specs.
Guess it depends on the nature of your extension and its desired functionality how you model things, but ForgeFed chose to have a dedicated actor, a TicketTracker, to manage the collection. Big advantage is that it become a truly encapsulated service with its own business logic, fronted by an AP actor for interoperable network communication.
-
I was looking at #ForgeFed which is a very sizable #ActivityPub extension (constituting the "Code forge" app domain in app-centric view, but arguably "Software development" top-level business domain in a service-oriented fedi).
The way that things are modeled here adheres more to the actor model where there's a Factory actor, which in turn creates resource actors that expose various sub-domains. For instance for the management of Issues and PR's there's a TicketTracker actor to obtain via a Factory actor on a forge instance. Though I'm not sure whether I'd modeled that in similar fashion, it is a fascinating direction where we focus much more on good protocol extension design.
All in all AS/AP offers a very granular foundation that allows for very interesting architectures, if only we dare explore them and do not dogmatically stick to some engrained notion how "social media" ought to be. I see #SocialMedia as but a small subset of #SocialNetworking.
-
#moderation is a shit job. always was, always will be. it's a human problem, no tech can dispel the chore. someone always has to be there, moderating
of course tooling can help immensely. the tooling shifts and manages the chore. that shift can be in good ways. also maybe unintentional bad ways
you know all this
i'm just laying it out so i can say:
on #bluesky, and on #mastodon, as you say, #blocklists create new terrible problems
i'm saying this tooling shift is a bad idea
-
#moderation is a shit job. always was, always will be. it's a human problem, no tech can dispel the chore. someone always has to be there, moderating
of course tooling can help immensely. the tooling shifts and manages the chore. that shift can be in good ways. also maybe unintentional bad ways
you know all this
i'm just laying it out so i can say:
on #bluesky, and on #mastodon, as you say, #blocklists create new terrible problems
i'm saying this tooling shift is a bad idea
-
#moderation is a shit job. always was, always will be. it's a human problem, no tech can dispel the chore. someone always has to be there, moderating
of course tooling can help immensely. the tooling shifts and manages the chore. that shift can be in good ways. also maybe unintentional bad ways
you know all this
i'm just laying it out so i can say:
on #bluesky, and on #mastodon, as you say, #blocklists create new terrible problems
i'm saying this tooling shift is a bad idea
-
#moderation is a shit job. always was, always will be. it's a human problem, no tech can dispel the chore. someone always has to be there, moderating
of course tooling can help immensely. the tooling shifts and manages the chore. that shift can be in good ways. also maybe unintentional bad ways
you know all this
i'm just laying it out so i can say:
on #bluesky, and on #mastodon, as you say, #blocklists create new terrible problems
i'm saying this tooling shift is a bad idea
-
sure, a #blocklist can be capricious and abusive, and subject to pique
but the overarching concept is that anyone makes a blocklist, and makes it as rigorous and comprehensive, or random and shoddy, as they want
and then people subscribe to it or not depending upon its quality (or lack thereof: is the theoretical harm in that a problem if it is self-imposed?)
if #bluesky corporate polices that, then what we get is they've removed the entire premise of #composableModeration
-
I'm probably not going to make it to #BerlinFediDay today, having stomach issues today and I'm exhausted.
Maybe tomorrow I'll be able to meet up with people.
https://hachyderm.io/@thisismissem/115313933685468305 -
#fediforumfriday: this week I've mostly been working on a side project experimenting with OAuth for decentralized & distributed web; To bootstrap this, rather than writing it all from scratch, I worked on reusing the atproto/oauth-provider package, which provides a LOT of functionality (including user registration & authorisation flows)
The OAuth profile is basically OAuth 2.1 + Client ID Metadata Documents + Pushed Authorization Requests + DPoP binding (prevents token theft) + Protected Resource Metadata (discover the authorization server from the resource)
The cool thing? All the SDKs for AT Proto for implementing OAuth servers & clients should mostly be reusable, easing adoption.
https://bsky.app/profile/thisismissem.social/post/3lyz3uigtn22g
I was also involved in conversations that lead to FEP-8967, which recommends software use Link objects in the attachment's to Objects (i.e, Notes) that the software or publisher wishes to prioritise the display of (rather than parsing out the first link in the content). This would also work for previews for links being federated in the future.
https://socialhub.activitypub.rocks/t/fep-8967-generating-link-previews-for-attached-links/5598
Besides that, just a lot of other conversations going on.
-
@thisismissem @adonisframework Yes, I saw it, but it sadly uses uses also old style decorators from TS with `emitDecoratorMetadata: true`.
My implementation does not use `emitDecoratorMetadata: true`!I also orientate myself currently a bit between #nestjs, #quarkus and #springboot.
-
@thisismissem Edited. Also - this may be a good opportunity to understand how #PeopleWithDisabilities feel about being excluded from almost every forum/convention because we need #COVIDSafe protocols.
-
So
Jumped, or was pushed?
mhmm...
"New York CNN —
#LindaYaccarino is stepping down as CEO of #X after two years leading #ElonMusk’s social media company.
#Yaccarino’s departure comes one day after the company’s #Grok #Chatbot began pushing antisemitic tropes in responses to users. It’s not clear that the events were connected."
And:
"It’s not clear whether Yaccarino, as head of the social media business, had any control over Grok or the company’s other #AI operations."
-
@thisismissem @rauschma oh neat - figured as much from reading the spec page.
FWIW, I'm particularly interested in learning how something like #fediscovery would work for projects like the Fedidevs project that @anze3db created, which aggregates disparate posts for things like events. See the FOSDEM and Djangocon Europe examples below:
https://fedidevs.com/fosdem25/
https://fedidevs.com/djangoconeu25/Anyway, maybe i'll catch you there 👍
-
@thisismissem OMG, spicy!
Also this is why we are keeping our #sextech research offline :3 -
@thisismissem OMG, spicy!
Also this is why we are keeping our #sextech research offline :3 -
@thisismissem OMG, spicy!
Also this is why we are keeping our #sextech research offline :3 -
@thisismissem OMG, spicy!
Also this is why we are keeping our #sextech research offline :3 -
@thisismissem “After 12 years of coding, I’d somehow become worse at my own craft”
Bingo. And that's why the #ProCraft movement needs to fight this dangerous technology with everything we've got.
(Alas I can't agree with the author when they say this: “I’m not suggesting we abandon AI tools—that ship has sailed.” Personally, I'm waiting for the ship to sink right into the ocean.)
-
-
@thisismissem @jaz @ocdtrekkie @mdm @mekkaokereke @jwildeboer
Sorry about the tags. I'm just listing this thread as #mastodonServer #mastodonInstance #mastodonAdmin because it seems full of useful resources for the novice and intermediate server wrangler.
-
@thisismissem @jaz @ocdtrekkie @mdm @mekkaokereke @jwildeboer
Sorry about the tags. I'm just listing this thread as #mastodonServer #mastodonInstance #mastodonAdmin because it seems full of useful resources for the novice and intermediate server wrangler.