wikiyu's latest activity
- 3mo ·
-
Public·
-
infosec.exchange
Years ago when i was younger i would suggest "procedure" approach -> move all DB stuff to as encapsulated procedures as possible (crud)
then making a migration BUT with stay on application side to procedures that are changed with migration.
Now? I dont know, i didnt thought about stuff like that for at least 4? 5? years as i am doing a bit different part of it development now then then.
…See more
Years ago when i was younger i would suggest "procedure" approach -> move all DB stuff to as encapsulated procedures as possible (crud)
then making a migration BUT with stay on application side to procedures that are changed with migration.
Now? I dont know, i didnt thought about stuff like that for at least 4? 5? years as i am doing a bit different part of it development now then then.
See less
Years ago when i was younger i would suggest "procedure" approach -> move all DB stuff to as encapsulated procedures as possible (crud)
then making a migration BUT with stay on application side to procedures that are changed with migration.
Now? I dont know, i didnt thought about stuff like that for at least 4? 5? years as i am doing a bit different part of it development now then then.
Years ago when i was younger i would suggest "procedure" approach -> move all DB stuff to as encapsulated procedures as possible (crud)
then making a migration BUT with stay on application side to procedures that are changed with migration.
Now? I dont know, i didnt thought about stuff like that for at least 4? 5? years as i am doing a bit different part of it development now then then.
- 12mo ·
-
Public·
-
infosec.exchange
@dansup now i am thinking about blocking own instance... and it looks as stupid (on first look) as allowing admin account to migrate to another server.
And that second one is sth that i needed to hack few days ago to migrate from selfhosted to infosexchange
…See more
@dansup now i am thinking about blocking own instance... and it looks as stupid (on first look) as allowing admin account to migrate to another server.
And that second one is sth that i needed to hack few days ago to migrate from selfhosted to infosexchange
See less
@dansup now i am thinking about blocking own instance... and it looks as stupid (on first look) as allowing admin account to migrate to another server.
And that second one is sth that i needed to hack few days ago to migrate from selfhosted to infosexchange
@dansup now i am thinking about blocking own instance... and it looks as stupid (on first look) as allowing admin account to migrate to another server.
And that second one is sth that i needed to hack few days ago to migrate from selfhosted to infosexchange
…See more
See less
- 12mo ·
-
Public·
-
infosec.exchange
@dansup i have a hope that it will be blocking per-user and not per-instance (which in most cases different then legal/pr0n/hardcore lack of moderation is not needed)
…See more
@dansup i have a hope that it will be blocking per-user and not per-instance (which in most cases different then legal/pr0n/hardcore lack of moderation is not needed)
See less
@dansup i have a hope that it will be blocking per-user and not per-instance (which in most cases different then legal/pr0n/hardcore lack of moderation is not needed)
@dansup i have a hope that it will be blocking per-user and not per-instance (which in most cases different then legal/pr0n/hardcore lack of moderation is not needed)
…See more
See less
- 12mo ·
-
Public·
-
infosec.exchange
@feditips why the hell block instead of silence instance so people can talk to eachother but we have to acceot each follow request?
…See more
@feditips why the hell block instead of silence instance so people can talk to eachother but we have to acceot each follow request?
See less
@feditips why the hell block instead of silence instance so people can talk to eachother but we have to acceot each follow request?
@feditips why the hell block instead of silence instance so people can talk to eachother but we have to acceot each follow request?