[GH-ISSUE #2148] Document L-shaped monitor routing scenarios #1858

Closed
opened 2026-10-02 22:21:22 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @ivypi-cc on GitHub (Aug 29, 2026).
Original GitHub issue: https://github.com/debauchee/barrier/issues/2148

Requested README update:\n\n- Add a two-machine scenario: server has two monitors, one landscape at the bottom and one portrait on the right; client has one landscape monitor at the top, placed in the notch of the server's L shape.\n- Add a three-machine variant where the right-side portrait display belongs to a third machine and the server has only the bottom landscape display.\n- Add a variant of the two-machine L shape with an additional Windows machine connected on the left side of the server landscape display.\n\nAcceptance:\n- README describes these scenarios clearly enough for users evaluating L-shaped/non-rectangular routing.\n- README links to the iBetterAI Barrier GitHub repository for the social-post CTA context.

Originally created by @ivypi-cc on GitHub (Aug 29, 2026). Original GitHub issue: https://github.com/debauchee/barrier/issues/2148 Requested README update:\n\n- Add a two-machine scenario: server has two monitors, one landscape at the bottom and one portrait on the right; client has one landscape monitor at the top, placed in the notch of the server's L shape.\n- Add a three-machine variant where the right-side portrait display belongs to a third machine and the server has only the bottom landscape display.\n- Add a variant of the two-machine L shape with an additional Windows machine connected on the left side of the server landscape display.\n\nAcceptance:\n- README describes these scenarios clearly enough for users evaluating L-shaped/non-rectangular routing.\n- README links to the iBetterAI Barrier GitHub repository for the social-post CTA context.
Author
Owner

@ivypi-cc commented on GitHub (Aug 29, 2026):

Opened against upstream by mistake; this belongs in the ibetterai fork. Closing.

<!-- gh-comment-id:5460948535 --> @ivypi-cc commented on GitHub (Aug 29, 2026): Opened against upstream by mistake; this belongs in the ibetterai fork. Closing.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
github-starred/barrier#1858
No description provided.