Notices by silverpill (silverpill@mitra.social)

I made changes on my side - Announce(Create) activities are treated as reposts now. This workaround is not difficult to implement, and if other blogging platforms don't support these activities, not catering to them might be a better long term strategy.

Of course, if Mastodon doesn't support Announce(Create), the calculation could be different, but I was told that it supports them.

@mapache It's working, thanks!

@mapache I can't follow it because instead of Accept activity it sends this (no type property):

@mkljczk I vote fedichick

@grishka They should be opt-in. Otherwise, it is a data farm and not a social network.

@sun Yeah. The wall is a collection of posts. Each post has associated conversation as collection of activities.

(I must admit, I've never used MySpace and have poor understanding how "walls" are supposed to work)

@sun Yes

@sun Conversation containers could be used to manage replies to posts on a wall.

@sun I think Smithereen's solution (FEP-400e) is sensible. Why don't you like it?

I would only tweak a couple of minor details there (e.g. use Remove instead of Delete, replace target with context).

@gabriel They will care about something other than email when that something will have billions of users. Meanwhile, ActivityPub is 10000x smaller, so we need to work 10000x harder.

@deutrino @sendpaws Cool. What are those projects?

@sendpaws Burns out but still refuses to acknowledge that alternatives to Mastodon crippleware exist.

However, unlike most rants, this one has a couple of good points. Moderation feed is good idea, I definitely should implement that.

@sun @light @liaizon

@light @liaizon Yes, but without "of ActivityPub-powered platforms" it doesn't mean much. Almost everything on the web is social in one way or another.

@liaizon Other platforms started doing that too https://ghost.org/help/social-web/

@nimda They block my mitra.social, but not public.mitra.social. Unpredictable.

@XMRbutterfly @monero

>what Kovri promised

It is not clear what the promise was. They criticize i2pd a lot, but i2pd is still alive and I've never had any issues with it, meanwhile Kovri is dead.

Better think about integrating emissary into cuprate.

@tadano

> stuck at follow requesting for the ones I tried to follow

I can look at those too

@tadano @relaystalker

>https://relay.poster.place/actor and https://relay.fedi.agency/actor

Both are yukimochi/Activity-Relay instances. The problem was reported but no response yet: https://github.com/yukimochi/Activity-Relay/issues/102

@tadano

>I try to look up relay actors half the time there's no account

I can add a command for that, but if those actors don't work in Web UI, they won't work in CLI either.

Some relays might not be compatible because they don't implement ActivityPub properly, or for some other reason, but I can talk to their maintainers if you tell me which ones are not discoverable.