Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mostr.pub/objects/d77ce4fb503f54f3a204468080e80cb5dbc6bcccc1263d60d614193b85397d68">Andrew (b17c59874dc05d7f6ec975bce04770c8b7fa9d37f3ad0096fdb76c9385d68928@mostr.pub)'s status on Friday, 29-Sep-2023 23:36:52 JST</a><a href="https://mostr.pub/users/b17c59874dc05d7f6ec975bce04770c8b7fa9d37f3ad0096fdb76c9385d68928" title="b17c59874dc05d7f6ec975bce04770c8b7fa9d37f3ad0096fdb76c9385d68928@mostr.pub"><img src="https://gnusocial.jp/theme/gnusocialjp/default-avatar-stream.png" width="48" height="48" alt="Andrew" style="position: absolute; left: 0; top: 0;">Andrew</a><div><ul><li></ul></div></section><article><a href="https://gleasonator.com/users/alex">@alex</a>  <br><br>I sent over a merge request to update Mostr's regex check to support the formatting used by BridgyFed's Bluesky &lt;=&gt; Mastodon bridge. This would in theory allow Bluesky profiles to be more seamlessly bridged to Nostr through BridgyFed/Mostr! <br><br><br><a href="https://gitlab.com/soapbox-pub/mostr/-/merge_requests/69">https://gitlab.com/soapbox-pub/mostr/-/merge_requests/69</a></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2117822#notice-4158167">In conversation</a><time datetime="2023-09-29T23:36:52+09:00" title="Friday, 29-Sep-2023 23:36:52 JST">about a year ago</time> <span>from <span><a href="https://mostr.pub/objects/d77ce4fb503f54f3a204468080e80cb5dbc6bcccc1263d60d614193b85397d68" rel="external" title="Sent from mostr.pub via ActivityPub">mostr.pub</a></span></span><a href="https://mostr.pub/objects/d77ce4fb503f54f3a204468080e80cb5dbc6bcccc1263d60d614193b85397d68">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: gitlab.com</div><h5><a href="https://gitlab.com/soapbox-pub/mostr/-/merge_requests/69">Updated handle regex to support the formatting used by bridgyfeds bluesky mastodon bridge (!69) · Merge requests · Soapbox / Mostr · GitLab</a></h5><div></div></header><div>https://github.com/snarfed/bridgy-fed/issues/381#issuecomment-1735683326  Big milestone, shipped Bluesky =&gt; fediverse user discovery! Search for @[handle]@atproto.brid.gy (eg @jay.bsky.team@atproto.brid.gy) in any fediverse server....</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Andrew (b17c59874dc05d7f6ec975bce04770c8b7fa9d37f3ad0096fdb76c9385d68928@mostr.pub)'s status on Friday, 29-Sep-2023 23:36:52 JSTAndrew
- Alex Gleason
@alex

I sent over a merge request to update Mostr's regex check to support the formatting used by BridgyFed's Bluesky <=> Mastodon bridge. This would in theory allow Bluesky profiles to be more seamlessly bridged to Nostr through BridgyFed/Mostr!

https://gitlab.com/soapbox-pub/mostr/-/merge_requests/69
In conversationabout a year ago from mostr.pubpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: gitlab.com
  Updated handle regex to support the formatting used by bridgyfeds bluesky mastodon bridge (!69) · Merge requests · Soapbox / Mostr · GitLab
  https://github.com/snarfed/bridgy-fed/issues/381#issuecomment-1735683326 Big milestone, shipped Bluesky => fediverse user discovery! Search for @[handle]@atproto.brid.gy (eg @jay.bsky.team@atproto.brid.gy) in any fediverse server....

Public

Embed Notice

HTML Code

Corresponding Notice