erlend_sh

joined 1 year ago
[–] erlend_sh@lemmy.world 3 points 9 hours ago (1 children)

Would love to hear about it when it’s out!

 

Homeownership on the web is highly analogous to the physical world. Modern homeownership is mostly a story of home-rentership, not real ownership.

Incredibly, this matches the online experience, even though the World Wide Web has an infinite amount of real-estate!

You deserve a home on the web that’s built to keep you safe; a magical place for virtual living that‘s yours for life, existing in a sociable web.

(Now stealth-releasing Weird v0.2 🥷)

https://writing.exchange/@erlend/113511576363997959

[–] erlend_sh@lemmy.world 4 points 5 days ago

That sounds really interesting! We’re building an OIDC server for indies with Weird – please feel free to come by and chat with us: https://blog.muni.town/muni-town/

[–] erlend_sh@lemmy.world 7 points 1 week ago* (last edited 1 week ago)

I’m aware of this library for it: https://github.com/kensanata/mastodon-archive

Dunno about any easy button-click service for it though, which is why we’re building it into Weird, which is like a CMS for your digital identity.

[–] erlend_sh@lemmy.world 37 points 3 weeks ago (7 children)

Exactly!

It’s not about Totalizing Enforcement. What it changes is the cultural norm. Not right away but over time.

An age limit on alcohol never stopped anyone of any age to acquire alcohol, but it sets the societal bar for what’s acceptable. You don’t wanna be the parents that gave your kids alcoholic beverages at 13.

It’s always a little jarring how everyone very readily believes that the Scandinavian countries are the happiest in the world, but won’t believe that the incremental policy changes we implement here have any effect 🤷‍♂️

 

How open source projects can balance Makers and Takers: lessons from Drupal's contribution credit system and recommendations for WordPress and other open source communities.

[–] erlend_sh@lemmy.world 17 points 1 month ago (5 children)

His point is there is no one protocol for the social web. The (open) social web is built on a pluriverse of protocols, like rss, email, irc, matrix, activitypub, atproto…

 

Some folks have gotten themselves together as something they’re calling the Social Web Foundation, and I’ll cut to the chase: this is an attempt by ActivityPub partisans to rebrand the confusing “fediverse” terminology, and in the process, regardless of intent, shit on everything else that’s been the social web going back twenty-five years.

[–] erlend_sh@lemmy.world 10 points 2 months ago (16 children)

One thing that seems to go unappreciated in the comments is the simplicity of this interop proposal: It is essentially about enabling quote-posting of link-aggregator(Groups) posts.

Bluesky + Frontpage will work this way, and I believe it’ll work exceedingly well. If the ap-net corner of the fediverse isn’t interested in this kind of interop, fair enough. To me however the promise of seamless interop between my social apps was what brought me to the fediverse, so that’s the version of the fediverse I will pursue.

 

Hey 👋 if you don't know us already, we're building Frontpage; an AT Procol based federated link aggregator. We shipped an initial MVP in closed beta recently and have since been thinking about the road to general availability.

This post is an RFC (Request for Comments) targeted at technically minded folks who are interested in seeing the progression of atproto for non-Bluesky/microblogging use cases. All that's to say the language that follows assumes some knowledge about how Bluesky and atproto work! I've tried to include links to explain what all of the jargon means though, so hopefully it's not entirely nonsense for folks a little less familiar!

When you post on Frontpage, we propose that a mirror post will also be created in your Bluesky account. When you comment on Frontpage, we propose that a mirror reply will be created in your Bluesky account.

Conversely, when you reply to one of these mirrored posts in Bluesky - we will show it as a reply in Frontpage.

Additionally, Bluesky likes will be translated to Frontpage votes and vice versa.

 

As a web engine, Servo primarily handles everything around scripting and layout. For embedding use cases, the Tauri community experimented with adding a new Servo backend, but Servo can also be used to build a browser.

We have a reference browser in the form of servoshell, which has historically been used as a minimal example and as a test harness for the Web Platform Tests. Nevertheless, the Servo community has steadily worked towards making it a browser in its own right, starting with our new browser UI based on egui last year.

This year, @wusyong, a member of Servo TSC, created the Verso project as a way to explore the features Servo needs to power a robust web browser. In this post, we’ll explain what we tried to achieve, what we found, and what’s next for building a browser using Servo as a web engine.

 

Back in June I wrote about an exciting confluence of digital auth tech:

(1) The commodification of #OIDC infrastructure, (2) the emergence of #FedCM, (3) and the compatibility of both with #indieauth .

In short, it is now easier than ever to log into web applications using your own website as an identity provider. Or at least, it would be, if your favorite web apps supported these agency-enhancing technologies.

https://blog.erlend.sh/indie-social-sign-in-could-go-mainstream

#opensource #indieweb #identity

https://writing.exchange/@erlend/113091679196090320

[–] erlend_sh@lemmy.world 2 points 4 months ago* (last edited 4 months ago)

Yeah I get that. What ‘works’ means in the context of local-first is flexible though. This might provide a useful framing: https://blog.jim-nielsen.com/2023/offline-is-online-with-extreme-latency/

In any case, you’re definitely right to focus on your specific use case first without trying to fit it into any specific paradigm. I’m excited to follow Habitat’s progress!

 

Speaker: Martin Kleppmann, University of Cambridge, Inc & Switch

We have come a long way since my colleagues and I published the local-first essay five years ago. In this talk I'll review where the local-first idea came from, where we are now, and what I hope the local-first community can work towards in the future.

[–] erlend_sh@lemmy.world 2 points 4 months ago (3 children)

This sounds great!

Are you familiar with the local-first tenets? Seems like a natural fit for the local nature of your app:

https://youtu.be/NMq0vncHJvU

75
submitted 4 months ago* (last edited 4 months ago) by erlend_sh@lemmy.world to c/fediverse@lemmy.world
 

I think this is the most important (WIP) Fediverse Enhancement Proposal of this year for the #ActivityPub protocol:

FEP-7952: Roadmap for Actor and Object Portability — by @by_caballero@mastodon.social and @dmitri@social.coop

It ties a lot of elementary building blocks for #nomadicidentity neatly together, most succinctly summed up by one particularly magic feature:

Bring-your-own Actor ID! 🪪💫

Actor profiles can now be hosted separately from the instance (including as a static JSON object on a personal website), which in turn enables service providers to offer their users a “BYO (Bring Your Own) domain name” feature.

That’s really all I ever needed from the notion of a ‘single-user instance’. All I want to manage on my own is my identity; I don’t want to take on the full burden of managing a whole AP server.

In this paradigm, someone’s tiny personal website could also be their Actor-ID Provider, and nothing more. That ID could in turn be used to as a (reasonably nomadic) account on any FEP-7952 compatible instance.

From @by_caballero@mastodon.social:

the idea is to detach the Actor object (which could be operated by a microserver that consumes almost zero resources, and basically just operates a big redirect table like a link-shortener) from the Service Provider, to be a little more like email (in the use case where you point a domain that you own and configure at protonmail or mailgun or some other provider) or SMS service (in that regulation enables you to keep your number when you switch phone co’s).

We will prototype the micro-Actor in the coming months, but we have no idea how long it would take for implementations like WordPress or forks of Mastodon/Misskey/Pleroma to offer support for this kind of externalized/self-managed Actor. We are hoping existing servers will find it interesting to offer a “service-provider mode” for the nomadic/domain-owning user class, for many reasons. In the meantime, we might also prototype a Fedify-powered server that only allows external Actors to create accounts.

Mastodon: https://writing.exchange/@erlend/112684879834557152

[–] erlend_sh@lemmy.world 12 points 6 months ago* (last edited 6 months ago)

This is certainly not spam but rather a blog response, a time honored practice as old as blogging itself.

OP’s article links to the source article (albeit via its fedipost rather than its blog post; maybe best to link both) and contributes to the online discourse with a long form reply, detailing a possible solution.

Mischaracterizing such a clearly well-intentioned contribution as “blog spam” is disingenuous.

edit: thanks for retracting your comment. I hope my retort won’t dissuade you from continuing to engage in this community :)

 

Social bookmarking is a novel use case for ActivityPub and I’m super excited about it. I heckin’ love links and lists! I wanna use them for everything.

Things like Bookwyrm are cool, but it’s not what I want. I just wanna link the thing. Books, films, podcasts, articles, songs.., they’re all just resource recommendations which can be encapsulated by links.

 

To free ourselves of our current predicament, we must simultaneously de-centralize and re-centralize identity.

  • Decentralize ownership.
  • Recentralize agency.

By de-centralizing the ownership of identity away from platform monopolies and back to individuals, we can re-centralize the agency of personhood.

The central authority of ones digital identity must first and foremost be the individual themself. That's how we regain our digital sovereignty.

 

In the glory days of web 1.0, social websites would prominently link out to their digital neighbors via lists known as webrings; magical doorways to an expansive hinterland of digital villages.

Let's envision what a truly federated chat like Matrix could do to improve the cross-connectivity of chat channels. Most of these features are already possible, they just haven't been implemented yet in a community-oriented client experience.

 

I suspect the fedi-collective has more negotiating power in this moment than it realizes. We may as well make some asks, see how Meta responds, and they in turn will see how the public, the media and the regulators respond to them in this bold new era of pervasive Big Tech skepticism.

Money can mitigate the risk of Threads:

'coopting the fediverse': $200k for Test Suite. 'overburdening moderators': $200k for moderation. 'locking in users': $200k for Nomadic Identity

A bit of internet reparations.

https://writing.exchange/@erlend/112163747418805861

[–] erlend_sh@lemmy.world 4 points 8 months ago

It will still have made the rounds, since it trended on HN: https://news.ycombinator.com/item?id=39667026

[–] erlend_sh@lemmy.world 1 points 1 year ago

I think Lemmy should come up with a meta cross post type. Where the post only exists once, but it's indexed in multiple communities, and moderators of those communities can remove the cross post. Without affecting the original post.

This is effectively how the Community-following-Community proposal works. I’ll repost what I commented in this thread:

I still believe the best solution is the ability for Communities to follow other Communities. That is essentially a fully automated version of this sibling proposal.

This has been explained in great detail by ‘jamon’ here:

https://github.com/LemmyNet/lemmy-ui/issues/1113#issuecomment-1595273502

This basically lets Communities opt to federate directly with other Communities, abiding by the same network dynamics as the fediverse at large, I.e. cross-network moderation by (de)federation.

Here’s a succinct description of the problem that C-C following solves:

If you are an active user (not moderator) of Lemmy, the requirement for this becomes apparent almost immediately. One of the biggest strengths of these forum are communities-at-scale. Being able to easily post and interact with large groups of people is the benefit to the user that makes Lemmy (and all other social media) appealing.

As a user, I recently wanted to post to AskLemmy. Almost every single instance has thier own separate AskLemmy implementation. Naturally, I'd tend to post to the one with the most users. But inherently, I'm missing the majority of users by only being able to post to one. I.E., I posted to AskLemmy@lemmy.ml (which had 3k users), but by doing that, I'm missing out on the users from lemm.ee, behaw, lemmy.world which in total are far more than 3k.

There is already a FEP for this functionality: https://socialhub.activitypub.rocks/t/fep-d36d-sharing-content-across-federated-forums/3366?u=erlend_sh

view more: next ›