Search
139 results for “thisismissem”
-
-
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
-
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.
-
@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 @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.
-
Wrote my first programming related blog post in a little while: How to redirect the user back to the previously requested URL after login with Adonis.js:
-
@[email protected] re: “issue might be with what you're federating out maybe”, possibly except that regardless of what I’m federating out, the point in my reply to @[email protected] is that #Mastodon is still getting it half-right, which is a bug in Mastodon regardless of what I’m federating out.
Either Mastodon should be treating my hashtags precisely as hashtags, (re)linking them to the local tagSpace *and* ignoring them for link previews, or it should be treating them “purely” as links, and not changing their default/published hyperlink and considering them for a link-preview.
Re: “help to have the activities json representation” — my understanding is that should be automatically discoverable from my post permalink, so all that should be needed for a bug report is my post permalink. Perhaps @snarfed.org can clarify since I’m using https://fed.brid.gy/ to provide that representation.
Either way, is there a validator for the “activities json representation” that we can use to test a particular post permalink, have it auto-discover an activities json representation, and report back what it finds and the validity thereof?
For example, since my posts use the h-entry standard, I am able to validate my post permalinks using the IndieWebifyMe h-entry validator:
https://indiewebify.me/validate-h-entry/?url=https%3A%2F%2Ftantek.com%2F2024%2F132%2Ft1%2F
Which finds and validates that I have marked up my hashtags/categories correctly.
Re: “@[email protected]'s Mention there got federated as a Link instead of as a Mention (since replying to this post didn't automatically include flaki's handle)” — this too sounds like a (different) Mastodon bug, since I believe @[email protected] was notified of my reply and mention of their handle. Perhaps Mastodon is getting it half-right: notifying but not canoeing¹?
Did you receive a notification in your Mastodon instance/client of this reply and its mention of your @[email protected]? Or only one but not the other?
#federate #federating #federated #hashTag #hashTags #atMention #atAtMention
Post glossary:
h-entry
https://microformats.org/wiki/h-entry
IndieWebifyMe
https://indiewebify.me/
References:
¹ https://indieweb.org/canoe -
Handlebars.js is the worst templating language in existence, but, if you have to use it, and need some sort of "global" value in your templates, e.g., a csrf_token, then you can use this:
https://gist.github.com/ThisIsMissEm/014a2d6ddb0ba53bebfb7be04870c46b
I'm sorry for writing this code, it's a horrible hack. But maybe it'll be useful to you.
-
I do really want to thank @nivenly (and especially @esk) for sponsoring the work to fix the critical security vulnerability found in @pixelfed earlier in February:
https://hachyderm.io/@thisismissem/112022457133862143
Nivenly stepped up, even though they don't have a stake in Pixelfed, they just wanted to see the Fediverse be safer, more secure and all that.
Without their support, I wouldn't have been able to dedicate the time to handling that (since I'm a freelancer)
-
I do really want to thank @nivenly (and especially @esk) for sponsoring the work to fix the critical security vulnerability found in @pixelfed earlier in February:
https://hachyderm.io/@thisismissem/112022457133862143
Nivenly stepped up, even though they don't have a stake in Pixelfed, they just wanted to see the Fediverse be safer, more secure and all that.
Without their support, I wouldn't have been able to dedicate the time to handling that (since I'm a freelancer)
-
I do really want to thank @nivenly (and especially @esk) for sponsoring the work to fix the critical security vulnerability found in @pixelfed earlier in February:
https://hachyderm.io/@thisismissem/112022457133862143
Nivenly stepped up, even though they don't have a stake in Pixelfed, they just wanted to see the Fediverse be safer, more secure and all that.
Without their support, I wouldn't have been able to dedicate the time to handling that (since I'm a freelancer)
-
I do really want to thank @nivenly (and especially @esk) for sponsoring the work to fix the critical security vulnerability found in @pixelfed earlier in February:
https://hachyderm.io/@thisismissem/112022457133862143
Nivenly stepped up, even though they don't have a stake in Pixelfed, they just wanted to see the Fediverse be safer, more secure and all that.
Without their support, I wouldn't have been able to dedicate the time to handling that (since I'm a freelancer)
-
I do really want to thank @nivenly (and especially @esk) for sponsoring the work to fix the critical security vulnerability found in @pixelfed earlier in February:
https://hachyderm.io/@thisismissem/112022457133862143
Nivenly stepped up, even though they don't have a stake in Pixelfed, they just wanted to see the Fediverse be safer, more secure and all that.
Without their support, I wouldn't have been able to dedicate the time to handling that (since I'm a freelancer)
-
iF I may add the same due to their track record of #FraudAsAService & #CSAMHosting #FreeWebHostingCulture as a #meme*
* #EEE #OligarchPlatforms #moderation #NoNews Type call it what it is #Propaganda Systems
📰🗞️📡🛰️📺 -
@thisismissem @sgf "blame" is not the same thing as "assigning responsibility".
A good red flag for this is teams that say "We do #blameless #postmortems by not naming anyone in the postmortem".
No! You know you have a blameless postmortem culture when you *can* name people in postmortems without it causing problems.
This can be exceptionally hard to achieve, but it's worth it.
Edit: see also @danslimmon https://blog.danslimmon.com/2023/04/20/its-fine-to-use-names-in-post-mortems/
-
@thisismissem which part of "the framework around them" do you miss?
Like if it's just the declarative DOM manipulation there are many dom-diffing libs. #lithtml #haunted #morphdom #virtualdom.
-
I've been a long-time advocate for #HumaneTechnology. Social coding commons adds something to that to become "humane and harmonious technology". Humane by default. #Humanity is an intrinsic value of the movement. And harmonious by #SocialCoding. Coding is social, and first of all deals with people coordinating to find solutions that align with and satisfy stakeholder needs. Coding happens somewhere in the process, an impl detail.
A core principle of Social experience design is Sustainability, which is holistic in nature via the (adapted) Circles of Sustainability model. https://coding.social/blog/reimagine-social/#circles-of-sustainability
With this in place a #SX software solution will cycle through its Free software development lifecycle i.e. #FSDL, which drives a tailored development based on needs and lifecycle phase. https://coding.social/blog/reimagine-social/#free-software-development-lifecycle
Together this completely avoids a pure technology-driven development, ensuring Needs-driven development, and a natural NIMBY of inhumane technology and practices.
-
Here's the diagram btw: https://social.coop/@smallcircles/116113963712755122
The problem of #SolidProject knowing what it is, is more an inherited problem of #LinkedData / #SemanticWeb knowing what it is.
Semantic web always was "if only all information on the web were semantic and machine-readable, then...". And there it stopped. Presumably magic would happen.
And perhaps it would. But to make such a big leap, a paradigm shift of the entire web, along the way you have inspire a whole lot of people to set the (r)evolution in motion and keep it going.
If you look at what linked data is, it is a very low-level format. Nice if you have it, but now what are you going to build with it? There are some good application areas, but the case for linked data elsewhere is not a given.
Still today there are regular discussions on 'what would be the killer app for Solid' or linked data in general. Saw some interest for LLM's fed semantic data to make them more deterministic. I'm not interested.
-
I made a diagram yesterday that contrasts #ActivityPub and #SolidProject that is I think interesting to consider.
In the past I've been very active on the Solid forum, and tried to get a collab going with #SocialHub community. A number of points that existed then, are still issues today I think.
Like, though anyone could participate in the standards process via chat, the Solid team and Inrupt were not really interested in their community, hardly giving attention while people were building interesting stuff there.
Also at the time basically all available code was Javascript, making Solid uninteresting or hard to access for other language devs.
But I think biggest issue was that Solid didn't know what it was. It was positioned as 'personal data vault' on the landing page then (but not using this term), but was 'secretly' TBL's desire to reboot the #SemanticWeb. The new web would be all 'Solid apps'. But the adoption strategy for that didn't exist.
-
@risottobias @thisismissem @reiver
Ditto. I would love to implement a Web Annotation client in my work.
Maybe we start tracking this with a hashtag? #WebAnnotations