CSS styling

[ghost]

It seems that the CSS in the website represents brutalism, in which can cause eyestrain (contrast... #fff and #000... yada yada) This is not recommended under normal use. I have a Framework in development that should allow theming as well as Jamstacking.

After this, i have a plan to create a blog/forum template that is fully built with noSQL along side others.

I am available to help but overhauling the CSS takes a lot of time.

anti-edit society

You must convert this from a format to text and then use 2 cyphers in the correct order. One was used in an American Civil War with the codename "manchester" and the other was used by a person that was killed in 49AD.

[whippingdot]

Nope only since you came

[ghost]

@whippingdot well, firefish was the one who invited me originally so i dont know whats going through his head

[whippingdot]

I don't know why you locked the conversation cause everyone here I am pretty sure is a collaborator...maybe not stringent i don't know but fine

[firefish111]

it says precisely why I locked the conversation: too heated

[firefish111]

@whippingdot well, firefish was the one who invited me originally so i dont know whats going through his head

I invited you back in April because you asked, you only asked to be invited again come June, and this is becoming the entire Tr1angular thing but worse. Trying to perfect projects which, I and others have been perfecting since Christmas? Here, newcomers are lower down the hierarchy, than people who have been here since the beginning. I'm sorry.

[firefish111]

@StringentDev https://github.com/DASM-Project/DASM/issues/18

[whippingdot]

hey can he still be in the org without you guys fighting? It is ok if he wants to make the project better - but he just shouldn't add commits randomly and do stuff like that. He did create an issue asking if he could change it...?

[firefish111]

hey can he still be in the org without you guys fighting? It is ok if he wants to make the project better - but he just shouldn't add commits randomly and do stuff like that. He did create an issue asking if he could change it...?

Yeah that's fine, if he gets into the teams he deserves to be in, because he's only learning nodejs, I had to make an entire tutorial to teach him stuff. He also tried to revive a dead project, virra, as DASM. You see, when he asked to be invited the first time, I had invited his old account, @Lethdev2019, and then we got annoyed at each other and he asked to be invited again after I told him about the tr1angular incident.

[iop3]

im not a mod, why can i close issues..? or every member of a org can close issues in that org?

[firefish111]

ye, these permissions suck, i trieed to fix it with the nidejs team and deleting and recreatnig was the only qway i know how

[ghost]

hey can he still be in the org without you guys fighting? It is ok if he wants to make the project better - but he just shouldn't add commits randomly and do stuff like that. He did create an issue asking if he could change it...?

Yeah that's fine, if he gets into the teams he deserves to be in, because he's only learning nodejs, I had to make an entire tutorial to teach him stuff. He also tried to revive a dead project, virra, as DASM. You see, when he asked to be invited the first time, I had invited his old account, @Lethdev2019, and then we got annoyed at each other and he asked to be invited again after I told him about the tr1angular incident.

I was never in the group to begin with as i'd have been in a team by them... and the tutorial came WAAAY after i learnt most of the stuff. To correct that, DASM was temporary, as the name did not quite look nice, It is called Vera, as the "ir" part was bugging me.

Also if you are trying to change perms, you have to go into org settings. Another way could be creating a team with admin perms whilst taking it off the others.

[ghost]

Also i tried reviving Virra, which worked successfully as work is being done again. Oh btw, Gcc did not like printf so i had to use puts instead as it must be a literal string

[ghost]

@whippingdot well, firefish was the one who invited me originally so i dont know whats going through his head

I invited you back in April because you asked, you only asked to be invited again come June, and this is becoming the entire Tr1angular thing but worse. Trying to perfect projects which, I and others have been perfecting since Christmas? Here, newcomers are lower down the hierarchy, than people who have been here since the beginning. I'm sorry.

It does not mean i will apply it without permission. I'm not that bad... I think... Also... I'm pretty sure that tutorial was in C not nodejs @firefish111 as i commented that it "looks just like javascript" which to be honest it does...

Besides, im waaaay underqualified to go into the C team.

[whippingdot]

im not a mod, why can i close issues..? or every member of a org can close issues in that org?

bruh issues are not supposed to be created by the people in the org, they are supposed to be created by external people. The people in the org are supposed to follow up on the issues and close it 🤦

[whippingdot]

hey can he still be in the org without you guys fighting? It is ok if he wants to make the project better - but he just shouldn't add commits randomly and do stuff like that. He did create an issue asking if he could change it...?

Yeah that's fine, if he gets into the teams he deserves to be in, because he's only learning nodejs, I had to make an entire tutorial to teach him stuff. He also tried to revive a dead project, virra, as DASM. You see, when he asked to be invited the first time, I had invited his old account, @Lethdev2019, and then we got annoyed at each other and he asked to be invited again after I told him about the tr1angular incident.

I was never in the group to begin with as i'd have been in a team by them... and the tutorial came WAAAY after i learnt most of the stuff. To correct that, DASM was temporary, as the name did not quite look nice, It is called Vera, as the "ir" part was bugging me.

Also if you are trying to change perms, you have to go into org settings. Another way could be creating a team with admin perms whilst taking it off the others.

I never allowed him to change perms though. He isn't telling me what he changed

[iop3]

im not a mod, why can i close issues..? or every member of a org can close issues in that org?

bruh issues are not supposed to be created by the people in the org, they are supposed to be created by external people. The people in the org are supposed to follow up on the issues and close it 🤦

im a idiot, thanks for pointing that out @whippingdot

[ghost]

hey can he still be in the org without you guys fighting? It is ok if he wants to make the project better - but he just shouldn't add commits randomly and do stuff like that. He did create an issue asking if he could change it...?

Yeah that's fine, if he gets into the teams he deserves to be in, because he's only learning nodejs, I had to make an entire tutorial to teach him stuff. He also tried to revive a dead project, virra, as DASM. You see, when he asked to be invited the first time, I had invited his old account, @Lethdev2019, and then we got annoyed at each other and he asked to be invited again after I told him about the tr1angular incident.

I was never in the group to begin with as i'd have been in a team by them... and the tutorial came WAAAY after i learnt most of the stuff. To correct that, DASM was temporary, as the name did not quite look nice, It is called Vera, as the "ir" part was bugging me. Also if you are trying to change perms, you have to go into org settings. Another way could be creating a team with admin perms whilst taking it off the others.

I never allowed him to change perms though. He isn't telling me what he changed

🤷‍♂️ are you sure you did not allow that?

[firefish111]

Another way could be creating a team with admin perms whilst taking it off the others.

well I was experimenting basically, found that the team has admin perms, recreated without, and now I think we should do the same for every team

[whippingdot]

hey can he still be in the org without you guys fighting? It is ok if he wants to make the project better - but he just shouldn't add commits randomly and do stuff like that. He did create an issue asking if he could change it...?

Yeah that's fine, if he gets into the teams he deserves to be in, because he's only learning nodejs, I had to make an entire tutorial to teach him stuff. He also tried to revive a dead project, virra, as DASM. You see, when he asked to be invited the first time, I had invited his old account, @Lethdev2019, and then we got annoyed at each other and he asked to be invited again after I told him about the tr1angular incident.

I was never in the group to begin with as i'd have been in a team by them... and the tutorial came WAAAY after i learnt most of the stuff. To correct that, DASM was temporary, as the name did not quite look nice, It is called Vera, as the "ir" part was bugging me. Also if you are trying to change perms, you have to go into org settings. Another way could be creating a team with admin perms whilst taking it off the others.

I never allowed him to change perms though. He isn't telling me what he changed

🤷‍♂️ are you sure you did not allow that?

No i mean like i didn't allow him verbally - he has the perms to do it

[whippingdot]

I made him a mod @StringentDev

[whippingdot]

Another way could be creating a team with admin perms whilst taking it off the others.

well I was experimenting basically, found that the team has admin perms, recreated without, and now I think we should do the same for every team

WHAT DO YOU MEAN BY ADMIN PERMS PLEASE EXPLAIN

If it means that they can edit any repository in that team, then I think you should leave it that way cause I want contributions from everyone without having to manually invite 30 people...

[firefish111]

Another way could be creating a team with admin perms whilst taking it off the others.

well I was experimenting basically, found that the team has admin perms, recreated without, and now I think we should do the same for every team

WHAT DO YOU MEAN BY ADMIN PERMS PLEASE EXPLAIN

If it means that they can edit any repository in that team, then I think you should leave it that way cause I want contributions from everyone without having to manually invite 30 people...

there are things called pull requests

[ghost]

Another way could be creating a team with admin perms whilst taking it off the others.

well I was experimenting basically, found that the team has admin perms, recreated without, and now I think we should do the same for every team

WHAT DO YOU MEAN BY ADMIN PERMS PLEASE EXPLAIN If it means that they can edit any repository in that team, then I think you should leave it that way cause I want contributions from everyone without having to manually invite 30 people...

there are things called pull requests

that is true... and is a pretty good idea... BUT I am talking about setting write perms to read perms. You can also set individual access to repos!

[firefish111]

Another way could be creating a team with admin perms whilst taking it off the others.

well I was experimenting basically, found that the team has admin perms, recreated without, and now I think we should do the same for every team

WHAT DO YOU MEAN BY ADMIN PERMS PLEASE EXPLAIN If it means that they can edit any repository in that team, then I think you should leave it that way cause I want contributions from everyone without having to manually invite 30 people...

there are things called pull requests

that is true... and is a pretty good idea... BUT I am talking about setting write perms to read perms. You can also set individual access to repos!

that's a lot of quotes

[whippingdot]

Another way could be creating a team with admin perms whilst taking it off the others.

well I was experimenting basically, found that the team has admin perms, recreated without, and now I think we should do the same for every team

WHAT DO YOU MEAN BY ADMIN PERMS PLEASE EXPLAIN If it means that they can edit any repository in that team, then I think you should leave it that way cause I want contributions from everyone without having to manually invite 30 people...

there are things called pull requests

that is true... and is a pretty good idea... BUT I am talking about setting write perms to read perms. You can also set individual access to repos!

It would take a long time...but if a lot of people really think so...

Another way could be creating a team with admin perms whilst taking it off the others.

well I was experimenting basically, found that the team has admin perms, recreated without, and now I think we should do the same for every team

WHAT DO YOU MEAN BY ADMIN PERMS PLEASE EXPLAIN If it means that they can edit any repository in that team, then I think you should leave it that way cause I want contributions from everyone without having to manually invite 30 people...

there are things called pull requests

that is true... and is a pretty good idea... BUT I am talking about setting write perms to read perms. You can also set individual access to repos!

that's a lot of quotes

Replying to your comment before this one - I know they are called PRs, but I am talking about repos in teams

[firefish111]

yeah everybody pull requests each commit, nobody except admins have access to commiting to master. THATS HOW ITS SUPPOSED TO WORK

[whippingdot]

i replied somewhere else

[firefish111]

very helpful

[ghost]

Why do I look at this comment chain and cringe at myself?

I do that a lot anyways so no change there

[zplusfour]

ded

[firefish111]

uncle jesus' casino

[whippingdot]

ded

I agree. I can try to revive but my life just isn't as free as before. I don't want to have the responsibility of checking in each day as I also want to improve my coding skills