Goofed Home

@badtuple I've debated making something that does that, but haven't ever pulled the trigger on it. I don't know of any other projects in this regard, but projects like NodeBB (and the threadiverse more generally) have done interesting work that could be adapted.

Now let’s talk about Fediprofile.

@badgefed issues recognition to recipients identified by a profile URL.

It intentionally does not allow email addresses (even hashed ones).

This avoids security issues and allows recipients to be identified using public profiles. Privacy at it's best.

Any URL can be used as a profile:

• LinkedIn
• Mastodon
• GitHub
• personal websites
• Instagram (ugh, eww)
• etc...

If that URL also happens to be an ActivityPub actor (for example a Mastodon or PixelFed profile), the user will also receive a mention or notification when a badge is issued.

--

Many people already receive badges across different identities.

For example, I personally have badges tied to:

• my LinkedIn
• my personal website
• gaming profiles

This is where the concept of a badge wallet or badge backpack becomes useful.

A place to collect them all. (POKEMON!)

Activitypub micropayments idea:
what if instead of some digital token like Taler or Monero, I send a digital “cheque” instead, which is a signed payment intent, signed with the other actor’s e.g. Liberapay pubkey.

At the end of the month, the other person can take all these micropayment cheques and prove to liberapay that other people owe you money, and everything is settled in one transaction.

#Activitypub #micropayments #taler #liberapay

@Profpatsch

Cool idea. Apple does something similar with their App Store payments. You buy a bunch of things and they hold the charges for a day or two, then charge it all at once.

It would be more difficult in a decentralized environment, though, if I’m aggregating charges for/from many different people.

Activitypub micropayments idea:
what if instead of some digital token like Taler or Monero, I send a digital “cheque” instead, which is a signed payment intent, signed with the other actor’s e.g. Liberapay pubkey.

At the end of the month, the other person can take all these micropayment cheques and prove to liberapay that other people owe you money, and everything is settled in one transaction.

#Activitypub #micropayments #taler #liberapay

@hongminhee @COSCUP
If there's any kind of travel bursary, I'd be delighted to speak.

@hongminhee @COSCUP woooooooooooo! Let me know if @swf can help in any way

@evan@cosocial.ca @swf@socialwebfoundation.org That means a lot, thank you! I’d love to take you up on that—will send you a DM with some specifics shortly.

@julian Ahh, thanks Julian! That makes sense. That’s pretty much the same guidance I got from Claude and ChatGPT too. If I go for Apple at some point, I won’t be able to just wrap the site and call it a day. I’d need to build out more native functionality, and I’m not going to pretend I fully understand that path yet haha.

@julian Also I didn't answer the question fully. I'm doing this in phases. I started with PWA as this is all still very early, and I am trying to prove people want to use the app. I don't have the full plan mapped out but know I would need to make changes for the Apple review if I go that route.

@shinmera There is only a proposal:

https://fediverse.codeberg.page/fep/fep/a427/

@shinmera GoToSocial has a Mastodon migration tool, I see it’s archived though https://github.com/VyrCossont/slurp/

@shinmera when my main acces domain moved from mastodon to social I just changed the settings and made everything redirect there. Probably only broke the I stances that can't handle webfinger and the alias domain stuff thingy

@shinmera oh I missed that, awesome!

@julian What about automated export and import of the posts? So that they at least exist in the new history, even if other federated servers will still point to the old domains?

@shinmera @julian there's no support for importing toots from other instances. Your export is only an archive.