diff --git a/content/note/604931a1/index.md b/content/note/604931a1/index.md
new file mode 100644
index 00000000..f6832e9b
--- /dev/null
+++ b/content/note/604931a1/index.md
@@ -0,0 +1,23 @@
+---
+date: '2021-03-10 20:52:49'
+draft: false
+pleromaurl: 'https://social.nipponalba.scot/notice/A54w4ZcbY2G3Shkrdw'
+posttype: note
+sensitive: 'false'
+slug: 604931a1
+visibility: public
+title: note
+---
+There are a few downsides that I'll need to consider if I do switch my activitypub identity to my website using bridgy fed, aside from current compatability issues with non-mastodon sites..
+
+I'll not have the multi-level blocking functionality offered by a fully-fledged activity pub app.. but on the flip side I do control the proxy server so can probably block domains quite easily.. could follow tusky's lead and Rick roll them..
+
+I won't be able to follow people from my account.. but can follow their RSS/atom/microformats streams and interact with their public posts..
+
+Only public posts, both reading and writing.. the latter not being an issue but the former is a little disappointing.
+
+I'll need to do some testing once pleroma compatibility works to check if I can CW posts.. I can with my syndication script.. and I really value that feature.
+
+On the plus side I wouldn't have to perform software breaking updates and then figure out why shit doesn't work and my database SBC would be under considerably less stress.
+
+Bridgy fed is just a first step though, at some point I would like to work out how to properly integrate activitypub into my site so that I could have a little more control over it.