Join 75,000+ Looksmaxxing Members!

Register a FREE account today to become a member. Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox.

  • DISCLAIMER: DO NOT ATTEMPT TREATMENT WITHOUT LICENCED MEDICAL CONSULTATION AND SUPERVISION

    This is a public discussion forum. The owners, staff, and users of this website ARE NOT engaged in rendering professional services to the individual reader. DO NOT use the content of this website as an alternative to personal examination and advice from licenced healthcare providers. DO NOT begin, delay, or discontinue treatments and/or exercises without licenced medical supervision. Learn more

Fear me .com

foidslayer

نحن الذين بنينا حصوننا من جماجم
Contributor ★
Reputable ★★★
Established ★★★
Joined
Dec 21, 2025
Messages
11,455
Solutions
7
Reputation
33,583
F48BC039-4FC3-453D-8A12-E3D394F1F261.webp
credits to @Notnotnotover0

@TonyDr better be careful
 
Register to hide this ad
i3 is a tiling window manager, completely written from scratch. The target platforms are GNU/Linux and BSD operating systems, our code is Free and Open Source Software (FOSS) under the BSD license. i3 is primarily targeted at advanced users and developers. Based upon the experiences we made when wanting to hack/fix wmii, we agreed upon the following goals for i3:

  1. Write well readable, well documentedcode. Create additional documentation on how to extend i3 by explaining its internal workings.
    This includes being modifiable by people who do know how to program but who are not necessarily familiar with all of X11’s internals. That is, document why things happen and when they happen so that the user gets a picture of the whole process a Window Manager is responsible of by just reading the source code.
  2. Use xcb instead of Xlib. xcb has a much cleaner API and should be faster in quite a lot of situations.
  3. Implement multi-monitor correctly, that is by assigning each workspace to a virtual screen. Especially make sure that attaching and detaching new monitors like video projectors works during operation and does the right thing. Also provide support for rotated monitors.
  4. Use a tree structure to arrange windows, enabling more flexible layouts than the column-based approach used by other window managers.
  5. Implement different modes, like in vim. You can use different keybindings when in the 'resize' mode than when you are in the default mode, for example.
  6. Implement an IPC interface for other programs. Provide subscription to certain events and accept commands.
    This approach should be more lightweight than wmii’s usage of the 9P filesystem. Furthermore, core functionality does not depend on a separate program, so that i3 runs faster, especially when your system is under load.
  7. Be UTF-8 clean.
  8. The usual elitism amongst minimal window managers: Don’t be bloated, don’t be fancy (simple borders are the most decoration we want to have).
    However, we do not enforce unnecessary limits such as a maximum amount of source lines of code. If it needs to be a bit bigger, it will be.
  9. Do not add further complexity when it can be avoided. We are generally happy with the feature set of i3 and instead focus on fixing bugs and maintaining it for stability. New features will therefore only be considered if the benefit clearly outweighs the additional complexity, and we encourage users to implement features using the IPC whenever possible.
In addition to these stated goals, we try our best to uphold the following values when considering contributions to the project:

  • Never break configuration files or existing workflows. Breaking changes require a major version bump (v4 → v5).
  • Keep mental complexity low: once you know i3’s key features, other features should be easy to understand.
  • Only add features which benefit many people, instead of going to great lengths to support rarely used workflows.
  • Only documented behavior is supported. Clear documentation is a requirement for contributions.
 
i3 is a tiling window manager, completely written from scratch. The target platforms are GNU/Linux and BSD operating systems, our code is Free and Open Source Software (FOSS) under the BSD license. i3 is primarily targeted at advanced users and developers. Based upon the experiences we made when wanting to hack/fix wmii, we agreed upon the following goals for i3:

  1. Write well readable, well documentedcode. Create additional documentation on how to extend i3 by explaining its internal workings.
    This includes being modifiable by people who do know how to program but who are not necessarily familiar with all of X11’s internals. That is, document why things happen and when they happen so that the user gets a picture of the whole process a Window Manager is responsible of by just reading the source code.
  2. Use xcb instead of Xlib. xcb has a much cleaner API and should be faster in quite a lot of situations.
  3. Implement multi-monitor correctly, that is by assigning each workspace to a virtual screen. Especially make sure that attaching and detaching new monitors like video projectors works during operation and does the right thing. Also provide support for rotated monitors.
  4. Use a tree structure to arrange windows, enabling more flexible layouts than the column-based approach used by other window managers.
  5. Implement different modes, like in vim. You can use different keybindings when in the 'resize' mode than when you are in the default mode, for example.
  6. Implement an IPC interface for other programs. Provide subscription to certain events and accept commands.
    This approach should be more lightweight than wmii’s usage of the 9P filesystem. Furthermore, core functionality does not depend on a separate program, so that i3 runs faster, especially when your system is under load.
  7. Be UTF-8 clean.
  8. The usual elitism amongst minimal window managers: Don’t be bloated, don’t be fancy (simple borders are the most decoration we want to have).
    However, we do not enforce unnecessary limits such as a maximum amount of source lines of code. If it needs to be a bit bigger, it will be.
  9. Do not add further complexity when it can be avoided. We are generally happy with the feature set of i3 and instead focus on fixing bugs and maintaining it for stability. New features will therefore only be considered if the benefit clearly outweighs the additional complexity, and we encourage users to implement features using the IPC whenever possible.
In addition to these stated goals, we try our best to uphold the following values when considering contributions to the project:

  • Never break configuration files or existing workflows. Breaking changes require a major version bump (v4 → v5).
  • Keep mental complexity low: once you know i3’s key features, other features should be easy to understand.
  • Only add features which benefit many people, instead of going to great lengths to support rarely used workflows.
  • Only documented behavior is supported. Clear documentation is a requirement for contributions.
 
i3 is a tiling window manager, completely written from scratch. The target platforms are GNU/Linux and BSD operating systems, our code is Free and Open Source Software (FOSS) under the BSD license. i3 is primarily targeted at advanced users and developers. Based upon the experiences we made when wanting to hack/fix wmii, we agreed upon the following goals for i3:

  1. Write well readable, well documentedcode. Create additional documentation on how to extend i3 by explaining its internal workings.
    This includes being modifiable by people who do know how to program but who are not necessarily familiar with all of X11’s internals. That is, document why things happen and when they happen so that the user gets a picture of the whole process a Window Manager is responsible of by just reading the source code.
  2. Use xcb instead of Xlib. xcb has a much cleaner API and should be faster in quite a lot of situations.
  3. Implement multi-monitor correctly, that is by assigning each workspace to a virtual screen. Especially make sure that attaching and detaching new monitors like video projectors works during operation and does the right thing. Also provide support for rotated monitors.
  4. Use a tree structure to arrange windows, enabling more flexible layouts than the column-based approach used by other window managers.
  5. Implement different modes, like in vim. You can use different keybindings when in the 'resize' mode than when you are in the default mode, for example.
  6. Implement an IPC interface for other programs. Provide subscription to certain events and accept commands.
    This approach should be more lightweight than wmii’s usage of the 9P filesystem. Furthermore, core functionality does not depend on a separate program, so that i3 runs faster, especially when your system is under load.
  7. Be UTF-8 clean.
  8. The usual elitism amongst minimal window managers: Don’t be bloated, don’t be fancy (simple borders are the most decoration we want to have).
    However, we do not enforce unnecessary limits such as a maximum amount of source lines of code. If it needs to be a bit bigger, it will be.
  9. Do not add further complexity when it can be avoided. We are generally happy with the feature set of i3 and instead focus on fixing bugs and maintaining it for stability. New features will therefore only be considered if the benefit clearly outweighs the additional complexity, and we encourage users to implement features using the IPC whenever possible.
In addition to these stated goals, we try our best to uphold the following values when considering contributions to the project:

  • Never break configuration files or existing workflows. Breaking changes require a major version bump (v4 → v5).
  • Keep mental complexity low: once you know i3’s key features, other features should be easy to understand.
  • Only add features which benefit many people, instead of going to great lengths to support rarely used workflows.
  • Only documented behavior is supported. Clear documentation is a requirement for contributions.
Call a publisher WE aren't reading that
 
.
 

Attachments

  • F48BC039-4FC3-453D-8A12-E3D394F1F261.webp
    F48BC039-4FC3-453D-8A12-E3D394F1F261.webp
    86.7 KB · Views: 8
why are there so many notover0
Notnotover0
Notnotnotover0
Notover0
where is the real over zero
they're not eachother, read the users
 
glad you didnt write foidslayer

that would be bad
dude deadass my handwriting is so trash my teachers force me to do my work on a laptop since they cant read my shit
 
  • Like
Reactions: i3
i was calling foidslayer an idiot, idiot.
What the fuck did you just fucking say about me, you little bitch? I'll have you know I graduated top of my class in the Navy Seals, and I've been involved in numerous secret raids on Al-Quaeda, and I have over 300 confirmed kills. I am trained in gorilla warfare and I'm the top sniper in the entire US armed forces. You are nothing to me but just another target. I will wipe you the fuck out with precision the likes of which has never been seen before on this Earth, mark my fucking words. You think you can get away with saying that shit to me over the Internet? Think again, fucker. As we speak I am contacting my secret network of spies across the USA and your IP is being traced right now so you better prepare for the storm, maggot. The storm that wipes out the pathetic little thing you call your life. You're fucking dead, kid. I can be anywhere, anytime, and I can kill you in over seven hundred ways, and that's just with my bare hands. Not only am I extensively trained in unarmed combat, but I have access to the entire arsenal of the United States Marine Corps and I will use it to its full extent to wipe your miserable ass off the face of the continent, you little shit. If only you could have known what unholy retribution your little "clever" comment was about to bring down upon you, maybe you would have held your fucking tongue. But you couldn't, you didn't, and now you're paying the price, you goddamn idiot. I will shit fury all over you and you will drown in it. You're fucking dead, kiddo.
 
What the fuck did you just fucking say about me, you little bitch? I'll have you know I graduated top of my class in the Navy Seals, and I've been involved in numerous secret raids on Al-Quaeda, and I have over 300 confirmed kills. I am trained in gorilla warfare and I'm the top sniper in the entire US armed forces. You are nothing to me but just another target. I will wipe you the fuck out with precision the likes of which has never been seen before on this Earth, mark my fucking words. You think you can get away with saying that shit to me over the Internet? Think again, fucker. As we speak I am contacting my secret network of spies across the USA and your IP is being traced right now so you better prepare for the storm, maggot. The storm that wipes out the pathetic little thing you call your life. You're fucking dead, kid. I can be anywhere, anytime, and I can kill you in over seven hundred ways, and that's just with my bare hands. Not only am I extensively trained in unarmed combat, but I have access to the entire arsenal of the United States Marine Corps and I will use it to its full extent to wipe your miserable ass off the face of the continent, you little shit. If only you could have known what unholy retribution your little "clever" comment was about to bring down upon you, maybe you would have held your fucking tongue. But you couldn't, you didn't, and now you're paying the price, you goddamn idiot. I will shit fury all over you and you will drown in it. You're fucking dead, kiddo.
this deserves an entire thread
but what copypasta is it
 
this deserves an entire thread
but what copypasta is it
it's just called the navy seal copypasta

Jfl this shit is hilarious.
 

Users who are viewing this thread

Back
Top