Software developer / ellipse tool’s number one fan. He/him. Hosted in Azure with microblog.pub.
@prefetcher@sh.itjust.works Very nice! I might switch my single-user server to something like this someday - it’d be nice to have something I know how to make changes to. Also looks like the database and cache dependencies all run through ASP.NET Core stuff so they could be replaced (although I know from experience that just because you’re using Cosmos DB thru EF Core doesn’t mean you can write your schema the same way!)
@jaagruk@mander.xyz microblog.pub has RSS feeds. you do need to self-host it though. That’s what I’m running on this account if you want to see an example
@ALostInquirer@lemm.ee I think part of it is the “branding” of Mastodon - if everyone someone follows uses a Mastodon server, they might just think of “Mastodon” as the social network they want to join, and never really consider that other people on the network might be using something like Firefish or Pixelfed or microblog.pub. After all, most Mastodon servers’ web UIs look pretty much the same and the default Mastodon name and graphics are often pretty prominent.
I don’t think this is usually an issue, but there are some Mastodon instances out there whose names are `mastodon.[something] and I think that can mislead people into thinking that’s the one they “should” join just because it seems “official”.
@Crul@lemm.ee @thegiddystitcher@lemm.ee neat, I never realized that micro.blog could federate itself in addition to crossposting to mastodon.
@carlnewton@feddit.uk one advantage to a system like this, is that you don’t need it to catch on in a bunch of different communities for it to work. It can catch on even in one place, and it will already be useful for the people there.