Wiki/Projects: Difference between revisions
→Meta: add example invocation markup |
→Meeting Notes: Next/Prev links: add section with explantion |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 34: | Line 34: | ||
===Non-duplication=== | ===Non-duplication=== | ||
[[:discord_link|:discord_link]] -> [[Template:Discord_link#Usage]] | <nowiki>{{</nowiki>[[:discord_link|:discord_link]]<nowiki>}}</nowiki> -> [[Template:Discord_link#Usage]] | ||
=Headerboxes= | =Headerboxes= | ||
| Line 43: | Line 43: | ||
==Headerbox template links== | ==Headerbox template links== | ||
<code>[[Wiki/Projects#Headerbox template links]]</code> | <code>[[Wiki/Projects#Headerbox template links]]</code> | ||
{{box5}} ... | |||
|| <small>[[:Wiki/Projects#Headerbox template links|V]] · [[:Talk:Wiki/Projects#Headerbox template links|T]] · [[Special:EditPage/Wiki/Projects#Headerbox template links|E]]</small> | |||
{{boxend}} | |||
Use the mnemonic '''V'''iew · '''T'''alk ''page'' · '''E'''dit, in the template, referring to the template's page itself. See the [[wp:Template:Hackerspace]] template box on Wikipedia for use of this Template box idiom on Wikipedia where it's well-established, after being arrived at though extensive experimentation and modification. It's an idiom, but a standard one. [[wp:WP:Navigation_template#Types]] | |||
Matching wikipedia's Navbox templates | Matching wikipedia's Navbox templates | ||
| Line 53: | Line 58: | ||
* <code><nowiki>[[:Template_Talk:About|T]]</nowiki></code>: talk page, for discussions in context, capturing design wishes & thoughts, at time of use | * <code><nowiki>[[:Template_Talk:About|T]]</nowiki></code>: talk page, for discussions in context, capturing design wishes & thoughts, at time of use | ||
* <code><nowiki>[[Special:EditPage/Template:About|E]]</nowiki></code>: edit link functioning with on-wiki links. Cribbed knowledge of the MediaWiki function from wikipedia's use | * <code><nowiki>[[Special:EditPage/Template:About|E]]</nowiki></code>: edit link functioning with on-wiki links. Cribbed knowledge of the MediaWiki function from wikipedia's use | ||
==Template Gateways== | |||
e.g. <code><nowiki>{{t}}</nowiki></code>, <code><nowiki>{{t/div}}</nowiki></code>, <code><nowiki>{{t/div/use}}</nowiki></code> so editors can type a short easy to remember template, hit preview, and get help on page for how to proceed further in more specific use. Similar in spirit, analogous, to the [[ext:Previews]] or [[ext:Navigation Popups]], but with render preview during edit instead of mouseover during browse. Fast feedback loops. | |||
{{t}} | |||
Trying to use these for styling, but also for date labeling [[Template:asof]] {{asof/2025}}. | |||
==Semantic-styled & -colored template wrappers== | |||
From [[Wiki/Ontology#Styling_Proposal:_Boxes_&_Colors]], let's implement these. | |||
I want to embed these into the [[Template:T]] hierarchy linked in [[#Template Gateways]] | |||
=Anti-crawler= | |||
<!-- note [[Anti-crawler]] page relies on this header format for deep-link --> | |||
With rate limits (per IP block at the moment, could improve with user agent--as honest, or filter improbable) helps smooth and reject traffic from excessively aggressive crawlers from a wide variety of web scrapers, especially for LLM training data, in 2024 and since. The quality of the scrapers vary, and hit the site heavily even when requests timeout, or only a small fraction succeed. What matters most from this, is the scraping activity makes the site unusable for our community. We would like representation of our conversations in training data, the next stage of internet-scale human knowledge, but we're still building it, living it, and scraping has interfered with that. I'm sure this is true for many other parties as well, but these are the major factors and considerations we've identified. | |||
==Log== | |||
* 14:55, 23 February 2026 (PST) -- updates to [[gh:noisebridge/infrastructure]], caddy configuration for the web server that serves the wiki, added rate limits per /24 IP range, limited to 30 requests per 5 second period. | |||
=Meeting Notes: Next/Prev links= | |||
On every meetings related page, see the [[Template:Meetings]] headerbox. Embedded there is the [[Template:WeeklyEventLinks]], a template that invokes [[Module:WeeklyEvent]] custom lua code for quick date calculations & text formatting for the wiki. | |||
{{meetings}} | |||
[[Template:WeeklyEventLinks]]: | |||
<blockquote>{{WeeklyEventLinks}}</blockquote> | |||
There are ideas about how to implement updating of the wiki pages by embedded forms, [https://chatgpt.com/c/699ce322-9090-832e-bcdd-19868c2f7ed6 here from chatgpt post]. | |||
It's worth calling out there are 2 uses of '''next meeting''' and '''previous meeting''', which are distinct and should be maintained clearly separate in mind, perhaps even given separate evocative names (or also meta-evocative—evoking the ambiguity and which side each label sits on). | |||
* Embedded in some wiki pages, you want a link with text '''Next meeting''', that always points to the next meeting. | |||
** evergreen next | |||
** Could use a template, e.g. especially ''but not limited to'' calling the module that calculates page names for the next date in the series. | |||
* On many many wiki pages, by observed volume, one more each week, you want Next and Prev meeting links that point to the page for the next and previous events in the sequence of events. | |||
** fixed relative Next + Prev, or local static Next + Prev | |||
** relative to loaded page, fixed in text link... Could be copied from a template instantiation, but could not embed a template to do this. | |||
Latest revision as of 18:49, 23 February 2026
| Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Stuff | Events | Projects | Meetings | Donate | E |
| Guilds (Volunteer) | Maintainers | Meta | Code | Electronics | Fabrication | Games | Sewing | Music | AI | Neuro | Philosophy | Funding | Art | Security | Ham | WGs | E |
| MetaGuild | Recruiting Guilds | Volunteer | Documentation | Outreach | Working Groups | CommunityWG | Badges | E |
| Documentation | Wiki | Signage | LED Signage | Posters | Labels | QR Codes | Note-taking | NoiseFacts | NoiseManual | Nb.wtf | V · T · E |
| Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Stuff | Events | Projects | Meetings | Donate | E |
| Communications Channels | Wiki | Discord | Slack (by invitation) | Jitsi | Pad | Meetup | Github | VR | 5MoF | YouTube | Blog | Zine | Contacts | Guestbook | BBS | V ·T · E |
| Wiki (c) | WikiWG | Templates | Proposed wiki changes | /Projects | Orphans | Oldest | CSS | JS | V · T · E |
This page tracks specific projects, long running, organized efforts to improve the wiki.
Badges & Userboxes
[edit | edit source]Badges, inspired by [1]. First implemented locally as WikiWG/badge. Also, more generally, Userboxes.
- https://www.noisebridge.net/wiki/Template:Userbox
- https://www.mediawiki.org/wiki/Template:Userbox
- https://commons.wikimedia.org/wiki/Commons:Userboxes
- https://www.mediawiki.org/wiki/Category:Userboxes (dry)
- https://codesnippets.fandom.com/wiki/Userboxes (3rd party)
Draft idea categories
[edit | edit source]Category:Badges Category:Headerbox Category:Userbox Category:Usergroups template:usergroups
Templates
[edit | edit source]Creating, maintaining (updating), & educating about templates available & how to use them. For easily signaling participation in one of the space's activities.
template:usergroups <== {{usergroups}}
Meta
[edit | edit source]template:linkshere <- {{linkshere}} template:subpages <- {{subpages}}
Non-duplication
[edit | edit source]{{:discord_link}} -> Template:Discord_link#Usage
Headerboxes
[edit | edit source]Tree hierarchy of template:home, for navigation.
Styling hierarchy for that tree layering template:boxes.
Headerbox template links
[edit | edit source]Wiki/Projects#Headerbox template links
| ... | V · T · E |
Use the mnemonic View · Talk page · Edit, in the template, referring to the template's page itself. See the wp:Template:Hackerspace template box on Wikipedia for use of this Template box idiom on Wikipedia where it's well-established, after being arrived at though extensive experimentation and modification. It's an idiom, but a standard one. wp:WP:Navigation_template#Types
Matching wikipedia's Navbox templates
|| <small>[[:Template:About|V]] · [[:Template_Talk:About|T]] · [[Special:EditPage/Template:About|E]]</small>
||: moves the rest of the line to the right<small>: de-biggens[[:Template:About|V]]: "[V]iew" mnemonic, nice for mouseover, or click to visit and see other users of template·: special character used as separator, between 1/2 and paragraph-S-mark, in edit footer, mw:extension:charinsert & on wiki settings for MediaWiki:EditTools[[:Template_Talk:About|T]]: talk page, for discussions in context, capturing design wishes & thoughts, at time of use[[Special:EditPage/Template:About|E]]: edit link functioning with on-wiki links. Cribbed knowledge of the MediaWiki function from wikipedia's use
Template Gateways
[edit | edit source]e.g. {{t}}, {{t/div}}, {{t/div/use}} so editors can type a short easy to remember template, hit preview, and get help on page for how to proceed further in more specific use. Similar in spirit, analogous, to the or , but with render preview during edit instead of mouseover during browse. Fast feedback loops.
Template:t {{t}}: This is the root page, of a collection of pages, as mw:help:subpages for easy, convenient use while editing. Include {{t/[subpage]}} to include reference instructional text in the page preview, Ctrl-Shift-p, while using source editing of wikitext.
Trying to use these for styling, but also for date labeling Template:asof Category:asof/2025.
Semantic-styled & -colored template wrappers
[edit | edit source]From Wiki/Ontology#Styling_Proposal:_Boxes_&_Colors, let's implement these.
I want to embed these into the Template:T hierarchy linked in #Template Gateways
Anti-crawler
[edit | edit source]With rate limits (per IP block at the moment, could improve with user agent--as honest, or filter improbable) helps smooth and reject traffic from excessively aggressive crawlers from a wide variety of web scrapers, especially for LLM training data, in 2024 and since. The quality of the scrapers vary, and hit the site heavily even when requests timeout, or only a small fraction succeed. What matters most from this, is the scraping activity makes the site unusable for our community. We would like representation of our conversations in training data, the next stage of internet-scale human knowledge, but we're still building it, living it, and scraping has interfered with that. I'm sure this is true for many other parties as well, but these are the major factors and considerations we've identified.
Log
[edit | edit source]- 14:55, 23 February 2026 (PST) -- updates to gh:noisebridge/infrastructure, caddy configuration for the web server that serves the wiki, added rate limits per /24 IP range, limited to 30 requests per 5 second period.
Meeting Notes: Next/Prev links
[edit | edit source]On every meetings related page, see the Template:Meetings headerbox. Embedded there is the Template:WeeklyEventLinks, a template that invokes Module:WeeklyEvent custom lua code for quick date calculations & text formatting for the wiki.
| Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Stuff | Events | Projects | Meetings | Donate | E |
| Meetings (c) [Prev · Next T] | Templates: Process (1st/mo) -- Discussion (non-1st/mo) | Current Consensus: edit -- History | Archive | Metaguild Archive | Announcements | Facilitation | Note-taking | V · T · E |
There are ideas about how to implement updating of the wiki pages by embedded forms, here from chatgpt post.
It's worth calling out there are 2 uses of next meeting and previous meeting, which are distinct and should be maintained clearly separate in mind, perhaps even given separate evocative names (or also meta-evocative—evoking the ambiguity and which side each label sits on).
- Embedded in some wiki pages, you want a link with text Next meeting, that always points to the next meeting.
- evergreen next
- Could use a template, e.g. especially but not limited to calling the module that calculates page names for the next date in the series.
- On many many wiki pages, by observed volume, one more each week, you want Next and Prev meeting links that point to the page for the next and previous events in the sequence of events.
- fixed relative Next + Prev, or local static Next + Prev
- relative to loaded page, fixed in text link... Could be copied from a template instantiation, but could not embed a template to do this.