Embed Notice

@dansup
if you make now (as far as I understood) pixelfed the same tech stack as loops, does it make sense to move duplicate/similar code to an extra library? In theory it's only backend functionality, which can be tested with unit tests. You then need just frontend tests in pixelfed/loops for it to see if it works.
But maybe it's too complex to keep it working for both? Especially if you have (at one point hopefully) different separate teams to take care of loops and pixelfed. Just an idea.