fef e3f97f60a6 change reaction api to match other interactions ... Status reactions had an API similar to that of announcement reactions, using PUT and DELETE at a single endpoint. I believe that for statuses, it makes more sense to follow the convention of the other interactions and use separate POST endpoints for create and destroy respectively.		2022-12-09 23:08:42 +01:00
..
v1	change reaction api to match other interactions	2022-12-09 23:08:42 +01:00
v2	Merge branch 'main' into glitch-soc/merge-upstream	2022-11-14 08:35:55 +01:00
web	Refactor formatter (#17828)	2022-03-26 02:53:34 +01:00
base_controller.rb	Add 'private' to Cache-Control, match Rails expectations (#20608)	2022-11-16 04:56:30 +01:00
oembed_controller.rb	Fix OEmbed leaking information about existence of non-public statuses (#12930)	2020-01-24 00:20:51 +01:00