Andy's latest activity
- 2y ·
-
Public·
-
desu.social
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
- 2y ·
-
Public·
-
desu.social
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
@dansup I have a question about a possible backend refactor I wanted to do for Pixelfed.
I noticed all API code is inside a single file per API version, wouldn't it be cleaner to have a version namespace and API controllers for each feature?
Before attempting this I thought I'd ask you if you even want such a change because the controller has been growing since I first saw it! 🙂
…See more
@dansup I have a question about a possible backend refactor I wanted to do for Pixelfed.
I noticed all API code is inside a single file per API version, wouldn't it be cleaner to have a version namespace and API controllers for each feature?
Before attempting this I thought I'd ask you if you even want such a change because the controller has been growing since I first saw it! 🙂
See less
@dansup I have a question about a possible backend refactor I wanted to do for Pixelfed.
I noticed all API code is inside a single file per API version, wouldn't it be cleaner to have a version namespace and API controllers for each feature?
Before attempting this I thought I'd ask you if you even want such a change because the controller has been growing since I first saw it! 🙂
@dansup I have a question about a possible backend refactor I wanted to do for Pixelfed.
I noticed all API code is inside a single file per API version, wouldn't it be cleaner to have a version namespace and API controllers for each feature?
Before attempting this I thought I'd ask you if you even want such a change because the controller has been growing since I first saw it! 🙂
- 2y ·
-
Public·
-
desu.social
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
@Gargron @thebiologist837 @hobs @rickrau @mdyshel This sounds like a mishap and confusion with mastodon.technology (the admin of which mentioned a family member falling terminally in in their shutdown announcement)
…See more
@Gargron @thebiologist837 @hobs @rickrau @mdyshel This sounds like a mishap and confusion with mastodon.technology (the admin of which mentioned a family member falling terminally in in their shutdown announcement)
See less
@Gargron @thebiologist837 @hobs @rickrau @mdyshel This sounds like a mishap and confusion with mastodon.technology (the admin of which mentioned a family member falling terminally in in their shutdown announcement)
@Gargron @thebiologist837 @hobs @rickrau @mdyshel This sounds like a mishap and confusion with mastodon.technology (the admin of which mentioned a family member falling terminally in in their shutdown announcement)
- 24d ·
-
Public·
-
desu.social
Is it just me or is blocking on Loops broken right now?
…See more
Is it just me or is blocking on Loops broken right now?
See less
Is it just me or is blocking on Loops broken right now?
Is it just me or is blocking on Loops broken right now?
- 9mo ·
-
Public·
-
desu.social
@dansup If someone wants to redo what your camera does, they will eventually find a way regardless of you open sourcing it or not!
publishing different builds to what your open source code is has multiple drawbacks:
* no replicable builds: we as a community never can be sure what you push to the store
* the release process gets over-complicated for you too, because you need to bring in the different camera into the OSS code locally for each release
…See more
@dansup If someone wants to redo what your camera does, they will eventually find a way regardless of you open sourcing it or not!
publishing different builds to what your open source code is has multiple drawbacks:
* no replicable builds: we as a community never can be sure what you push to the store
* the release process gets over-complicated for you too, because you need to bring in the different camera into the OSS code locally for each release
See less
@dansup If someone wants to redo what your camera does, they will eventually find a way regardless of you open sourcing it or not!
publishing different builds to what your open source code is has multiple drawbacks:
* no replicable builds: we as a community never can be sure what you push to the store
* the release process gets over-complicated for you too, because you need to bring in the different camera into the OSS code locally for each release
@dansup If someone wants to redo what your camera does, they will eventually find a way regardless of you open sourcing it or not!
publishing different builds to what your open source code is has multiple drawbacks:
* no replicable builds: we as a community never can be sure what you push to the store
* the release process gets over-complicated for you too, because you need to bring in the different camera into the OSS code locally for each release
…See more
See less
- 9mo ·
-
Public·
-
desu.social
@dansup I assume this has to do with the plans of offering hosting for Pixelfed, and ease of configuring when no server access is given
but stuff like this should be handled in a hosting panel outside of the main app then.
adding so much logic into the application to keep those values safe, when easier options are already there is a bit...counter-productive. and error-prone as well, and you don't want these secrets to get into the wrong hands!
…See more
@dansup I assume this has to do with the plans of offering hosting for Pixelfed, and ease of configuring when no server access is given
but stuff like this should be handled in a hosting panel outside of the main app then.
adding so much logic into the application to keep those values safe, when easier options are already there is a bit...counter-productive. and error-prone as well, and you don't want these secrets to get into the wrong hands!
See less
@dansup I assume this has to do with the plans of offering hosting for Pixelfed, and ease of configuring when no server access is given
but stuff like this should be handled in a hosting panel outside of the main app then.
adding so much logic into the application to keep those values safe, when easier options are already there is a bit...counter-productive. and error-prone as well, and you don't want these secrets to get into the wrong hands!
@dansup I assume this has to do with the plans of offering hosting for Pixelfed, and ease of configuring when no server access is given
but stuff like this should be handled in a hosting panel outside of the main app then.
adding so much logic into the application to keep those values safe, when easier options are already there is a bit...counter-productive. and error-prone as well, and you don't want these secrets to get into the wrong hands!
…See more
See less
- 9mo ·
-
Public·
-
desu.social
@dansup you should have stopped after the first line.
just having storage credentials in ENV is enough, they never really need to be in the database.
…See more
@dansup you should have stopped after the first line.
just having storage credentials in ENV is enough, they never really need to be in the database.
See less
@dansup you should have stopped after the first line.
just having storage credentials in ENV is enough, they never really need to be in the database.
@dansup you should have stopped after the first line.
just having storage credentials in ENV is enough, they never really need to be in the database.
…See more
See less
- 12mo ·
-
Public·
-
desu.social
@dansup Misskeys codebase is feature-rich (or bloated, rather) and everyone has a different idea of how to improve it.
if people don't like the direction a fork is taking development-wise, they either fork Misskey, or that fork, and then make their own set of changes.
…See more
@dansup Misskeys codebase is feature-rich (or bloated, rather) and everyone has a different idea of how to improve it.
if people don't like the direction a fork is taking development-wise, they either fork Misskey, or that fork, and then make their own set of changes.
See less
@dansup Misskeys codebase is feature-rich (or bloated, rather) and everyone has a different idea of how to improve it.
if people don't like the direction a fork is taking development-wise, they either fork Misskey, or that fork, and then make their own set of changes.
@dansup Misskeys codebase is feature-rich (or bloated, rather) and everyone has a different idea of how to improve it.
if people don't like the direction a fork is taking development-wise, they either fork Misskey, or that fork, and then make their own set of changes.