New Feature: What Links Here
1 direct reply — Read more / Contribute
|
by jdporter
on Mar 18, 2024 at 14:15
|
|
Alrighty, folks! I've got another steaming-new feature for you: What Links Here
There is a new nodelet you can enable, if you are interested in this feature. Go to your Nodelet Settings and find "What Links Here" somewhere near the top of the list.
Then, whatever node you're on, this nodelet will show what other nodes link to the current node.
It caps out at 100, so for some nodes, such as PerlMonks FAQ, it will just show "too many results".
The database table behind this feature is not automatically maintained (yet), so I'll need some volunteers from pmdev to occasionally visit Update Userspace Links. Doing so will cause a delta update to the table.
I was inspired by this old quote from Rob Malda:
The thing that I always thought was the most interesting in Xanadu is the idea that links are bi-directional. And the Everything Engine was designed around that.
|
Visited links in nodelets are rendered invisible
1 direct reply — Read more / Contribute
|
by Anonymous Monk
on Mar 09, 2024 at 04:02
|
|
For a few weeks and for AM only (I guess), links in "boxes" on the right (nodelets they are called?) that have been already visited are now rendered as invisible text. I'm not too good with HTML/CSS to know why. Seen in different browsers/OSes/platforms. Maybe not very important and affects despicable AMs only, but still kind of broken window perspective.
Also, I have put "boxes" into quotes above, they used to be nice clean boxes with strict lines to serve as borders, now without these lines it's amorphous pile with huge gaps of invisible text, but I understand that march of modernity/design is unstoppable, this latter complaint is just imho.
|
Recent threads - Show toggle on the left: indentation
2 direct replies — Read more / Contribute
|
by Danny
on Mar 07, 2024 at 12:01
|
|
Having the +/- on the left side seems like the natural place for showing/hiding a sub-tree. However, when you do this, the + is left aligned with sub-trees at the same depth. This is fine if all sub-trees have descendents, and thus a +/-. But, if a sub-tree without descendents is above a sub-tree with descendents at the same level it appears as though the lower sub-tree is a descendent of the upper instead of a sister. For example, if the following are at the same level it looks like this:
Re: Great subject[^19] 24 hours ago [him]
+/-Re: Great subject(1) 11 hours ago [her]
But it would be more natural if the subjects at the same depth were aligned like this:
Re: Great subject[^19] 24 hours ago [him]
+/-Re: Great subject(1) 11 hours ago [her]
|
Ability to mark specific "newest nodes" nodes as read
3 direct replies — Read more / Contribute
|
by Danny
on Mar 01, 2024 at 14:22
|
|
Currently you can clear your "newest nodes" list up to the current time. However, it might be useful if you could remove specific nodes that you no longer want to show up. The "Newest Nodes" node is where I usually go so it would be nice for it to be more configurable.
|
New Feature: Thread Watcher
4 direct replies — Read more / Contribute
|
by jdporter
on Feb 29, 2024 at 14:54
|
|
I am pleased to announce a new feature: thread watching. This lets you receive notification whenever someone posts a comment in a thread of interest.
More specifically, you can get notified when someone replies directly to a specific node of interest, or when someone replies anywhere under a node of interest, no matter how many reply levels below the node. These two modes are called 'direct' and 'any'. The node of interest doesn't have to be a root node in one of the sections; it could be any reply as well, in case you're only interested in a subthread under some post.
To register for notifications, click one of the new links you'll find by each node, near the "Comment on" link. For a node you're viewing directly (that is, the 'root' of a (sub)thread you're viewing), the new text looks like:
Watch for: Direct replies / Any replies
For all other nodes in a (sub)thread you're viewing, the new text looks like:
Watch: Dir/Any
If you have already registered interest in a node in this way, these links will not be present. In their place, there may be an indication that you are already watching the node.
To see a list of all the nodes you are currently watching, go to My Watched Nodes.
Next to each watch listed, you'll see a "button" (like [X]) which you can click to delete that watch.
In addition...
You can watch a user, i.e. receive notification whenever a specific user posts.
To set up this kind of watch, go to the user's homenode, where you will see a link like Watch for posts by this user.
|
Basic syntax displayed up front
2 direct replies — Read more / Contribute
|
by Danny
on Feb 20, 2024 at 05:37
|
|
I think it would be really good for new users to have a prominent link to basic syntax for posting. It could be like a mini-faq that has the most common things people might want to use. It would be very helpful. This site can be challenging when new.
|
New feature: copy/pastable self referential backlink [id://...] for every node
2 direct replies — Read more / Contribute
|
by LanX
on Feb 05, 2024 at 10:40
|
|
Two weeks ago I provided a patch Re: node_info_string - (patch) to change the linking of the ID in the header of all nodes to [id://...] style.
The idea is to facilitate linking to nodes by simple copy&paste.
NB: Some browsers facilitate this further by providing a "copy link text" entry
in the context menu (right-click/long touch)
Explicitly
==== BEFORE:
The links in the page headers below the title looked like
- on Jan 25, 2024 at 13:46 CET ( #11157250 =pmdevnote: print w/replies, xml )
==== AFTER:
Now they display [id://...] around the link
- on Jan 25, 2024 at 13:46 CET ( [id://11157250] =pmdevnote: print w/replies, xml )
History
This patch was experimental, but so far nobody complained. I'd even say almost nobody noticed. :)
Linking with id:// has many advantages, like avoiding lock-outs and displaying the nodes title.
I hope this will make proper linking easier.
On a side note: I personally used this for over a decade already, changing the link was one of my first Nodelet hacks in JS.
Implementing it for PM proved to be far more complicated tho.
Related posts
Related docs
Updates
Added:
- Highlighting
- Better examples
- Links
|
We have gotten onto the scammers' radar
No replies — Read more | Post response
|
by erzuuli
on Feb 05, 2024 at 08:18
|
|
Look at this ridiculous BS email I just got — the first such, and hopefully the last:
From: bk3587110@gmail.com
To: vroom@********
Bcc: johndporter@********
Fri, Feb 2 at 3:18 PM
Greetings,
Qeitiqwe Sykes here from Next Publisher. We've been monitoring perlmonks.org and see great potential for a partnership.
We connect esteemed sites like yours with advertisers seeking quality placements. Could you share your advertising rates and any special packages for bulk deals?
Your insight will enable us to tailor our services to meet your needs and preferences.
Thank you for your attention to this proposal.
Kind regards,
Qeitiqwe Sykes
Next Publisher
I tried g**gling the various names and found nothing.
|
Priorities perhaps?
3 direct replies — Read more / Contribute
|
by Bod
on Feb 01, 2024 at 16:58
|
|
Looking back over the patches for the last few years, it strikes me that despite lots of patches, mostly from jdporter, there has been lots of good fiddling around the edges. The biggest flaws in The Monastery remain. I believe these are turning people away from The Monastery.
I would like to propose what I think are three priorities that would be a step change for The Monastery without removing any of it's existing strengths:
- WISIWIG editor for posting along the lines suggested by cavac in WYSIWYG editor
- A revamp of the main menu navigation bar
- Address the issue of unencoded passwords
I am not suggesting someone else does the work to make these happen. They are all things that I have implemented on other sites multiple times. However, I don't have the knowledge of PM's codebase or sufficient access for some of these. So I would need help to make them happen.
We only have to look across to Everything2 to see how relatively small changes can have a big impact on user experience
Javascript
I'm going to preempt an objection...that 1 and 2 would require Javascript and not everyone has it enabled.
A few years I ran a test on one of my sites to see how many people have JS switched off. After over 700k visits, less than 0.2% has JS off. But, I accept that PM is mostly frequented by older developers (me included) who are more likely to switch off JS.
But whilst JS is needed to make WYSIWYG functionality, we can have a user setting to switch back to the existing raw-HTML editor and also do that switchback automagically if JS is not enabled on the user's browser.
None of this is new...but is there any mileage or appetite for addressing it now?
|
Docs for enhanced linking style with '<' for '|' ?
3 direct replies — Read more / Contribute
|
by LanX
on Jan 25, 2024 at 08:57
|
|
Hi
since I'm trying to patch some linking stuff for better convenience I need to know where this feature is documented for users
[id://1169071< Node=%N — Author=%A — Date=%d]
--> Node=[id://1169071] — Author= — Date=
Already looked into
, but no avail.
Thanks! :)
PS: I can only imagine eyepops using it for is extensive link collections ;-)
|
Why is the site response time so incredibly slow?
3 direct replies — Read more / Contribute
|
by Danny
on Jan 23, 2024 at 20:36
|
|
The response time for requests on this site is super slow. At times it takes 30 seconds for a page to load. Why is that?
|
209.197.123.153 Down
6 direct replies — Read more / Contribute
|
by choroba
on Jan 23, 2024 at 14:06
|
|
www.perlmonks.org is timing out for me. 209.197.123.153 seems to be down. 66.39.54.27 pings and runs without problems, as does 216.92.34.251.
map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
|
Total writeups sometimes incorrect
1 direct reply — Read more / Contribute
|
by hippo
on Jan 11, 2024 at 06:37
|
|
|
RFC: "Today I Learned" page
9 direct replies — Read more / Contribute
|
by jdporter
on Jan 10, 2024 at 23:40
|
|
Some time in the last year or two I suddenly realized that I should be keeping a log of the interesting things I learn from day to day.
A couple months ago I was talking with my brilliant young nephew about how I didn't have a really satisfactory solution, and he suggested Notion.
He set up a Notion workspace where we can both enter our #TILs. It works really well. Notion is amazing.
But I can see how it might not scale too well with a large number of contributors.
Long story short — I have created Today I Learned, a page where anyone (meeting certain minimum elibility requirements) can share interesting factoids.
Please check it out. What do you think? Is it worthwhile? If not, could it be made better? If so, how? If snot, blow?
I also want to note that the extant page, Today I Learned, is based on a generic mechanism which can be easily leveraged for other similar tasks. The main configurable parameters are: who can view the page, who can add entries, and who can delete entries. (readers/writers/deleters, in short.) These can be based on a user group (such as janitors or breathers of fire), or on monastic level (such as Level 10: Hermit). Can you think of a use for such a feature?
I thank you, and Paco thanks you.
* On the Today I Learned page, entries can be deleted by the Janitors, and the Editors Nodelet contains a link to that page labled 'TIL'.
When there is a new entry on that page, a little flag (*) is appended to the 'TIL' link.
Today's latest and greatest software contains tomorrow's zero day exploits .
|
Hacker News titles using U+2013 EN DASH
3 direct replies — Read more / Contribute
|
by kcott
on Jan 09, 2024 at 02:29
|
|
Many Hacker News titles use U+2013 EN DASH.
When listed in the "HackerNews nodelet" these are rendering as "–" instead of "–".
Would it be possible to convert these?
I know nothing of the code behind the scenes. Here's a couple of potential options:
$ perl -Mutf8 -C -E '
my $HN_title = "Show HN: Auto Wiki – Turn your codebase into a Wiki";
say $HN_title;
say $HN_title =~ s/–/\N{EN DASH}/gr;
say $HN_title =~ s/–/–/gr;
'
Show HN: Auto Wiki – Turn your codebase into a Wiki
Show HN: Auto Wiki – Turn your codebase into a Wiki
Show HN: Auto Wiki – Turn your codebase into a Wiki
Using – is possibly the better option; but I'm just guessing.
|