Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge and SMF directions
« Reply #30, on July 21st, 2011, 12:14 AM »
The Friends board being referred to wasn't SMF Friends, but the board reserved for team members and ex team members, notionally for the benefit of the project but it ended up mostly as an echo chamber for those who for whatever reason didn't carry a team badge. (The one Nao was barred from, that is, after last autumn's events)

If you mean trackbacks in the context I think you mean, there is only one way to actually do it since it's an established standard used by WordPress. The fact that WP basically created it and it causes more spam than you would begin to imagine (of the spam on InI, I get 10-12 trackback spam per spam post)
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Wedge and SMF directions
« Reply #31, on July 21st, 2011, 12:43 AM »
Ah, trackbacks... The only blog feature I failed to add to Noisen.com, really. I don't even remember why I didn't look further into it ;)

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge and SMF directions
« Reply #32, on July 21st, 2011, 01:08 AM »
Because what sounds like a really neat idea really isn't so neat? It's not like it's forgeable or anything *yawn*

live627

  • Should five per cent appear too small / Be thankful I don't take it all / 'Cause I'm the taxman, yeah I'm the taxman
  • Posts: 1,670
A confident man keeps quiet.whereas a frightened man keeps talking, hiding his fear.

Re: Wedge and SMF directions
« Reply #34, on July 21st, 2011, 01:34 AM »
Yes, trackback.  You already know it by another name via a person who shall not be named because he usually gets banned. ;)
(click to show/hide)
The Russian

I have a use for that capability, and already 3 boards I've been active on are boards--boards that I wish had had that capability.--are  now defunct and all that research is gone. Trackback capability would have preserved discussions/information of interest by making them portable, making the threads movable to another board before the plug got pulled.
Re: Wedge and SMF directions
« Reply #35, on July 21st, 2011, 01:47 AM »
Quote from Arantor on July 21st, 2011, 12:14 AM
The Friends board being referred to wasn't SMF Friends, but the board reserved for team members and ex team members, notionally for the benefit of the project but it ended up mostly as an echo chamber for those who for whatever reason didn't carry a team badge. (The one Nao was barred from, that is, after last autumn's events)

If you mean trackbacks in the context I think you mean, there is only one way to actually do it since it's an established standard used by WordPress. The fact that WP basically created it and it causes more spam than you would begin to imagine (of the spam on InI, I get 10-12 trackback spam per spam post)
Well, worrying about how pretty a board's urls look to a search engine bring in the spammers too, so I don't know how avoiding a capability is going to get you less spam. One way or the next, spammers are on a mission to find you. There is no escape. The best defense is to not let 'em in when they do find you. And ceding the code to WordPress means that there's no other way than the way WordPress does it. There's always a better way to make a better mousetrap, IMHO.
Posted: July 21st, 2011, 01:40 AM
Quote from Nao/Gilles on July 21st, 2011, 12:43 AM
Ah, trackbacks... The only blog feature I failed to add to Noisen.com, really. I don't even remember why I didn't look further into it ;)
Just ask a researcher why it's important. :)
Posted: July 21st, 2011, 01:44 AM
Quote from Arantor on July 21st, 2011, 01:08 AM
Because what sounds like a really neat idea really isn't so neat? It's not like it's forgeable or anything *yawn*
What have you got against researcher community forums? Are only gamers real people? :P
I shall continue to be an impossible person as long as those who are now possible remain possible

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge and SMF directions
« Reply #36, on July 21st, 2011, 10:32 AM »
To answer that...

1/ You misunderstand my contention regarding search friendly URLs. It is my contention that they do not help search engines, but the converse is also true: *not* having them doesn't help search engines either. The absence or presence of said feature, then, is virtually pure aesthetics. I'm not against pretty URLs provided that there is an awareness that they are purely aesthetic - to claim they have any kind of SEO benefit is BS.

2/ I didn't say that it was WP's code that was the issue, because it isn't. There is an established protocol for trackbacks where you have inter-site communications, which must be implemented for it to work. A trackback facility that only one system uses isn't much help unless that one system is by definition, everywhere.

Gri's discussions aren't about trackbacks, they're about having the same discussion physically *duplicated* in two separate places so that there is no ability of one party to edit them.

The trackback protocol, as designed, is endemically flawed: it has no mechanism for authentication, consequently any site can generate a trackback, which means any site can *spam* you with trackbacks. Imagine a system able to post that doesn't require registration, doesn't require to enter a name but only has to posts a small snippet of text and a link back to their site. I have deleted many many spam trackbacks from InI but have yet to see one that wasn't actually spam.

3/ The concept of a trackback is cute, but as explained, the moment you start applying real life to it, it starts to fall apart. If you then proceed to implement a new trackback scheme, it's only valid as far as Wedge installs go: until Wedge is ubiquitous, implementing it in a new form is basically useless.


Trackbacks do NOT make discussions portable if you listen to what the specification actually provides for: all it does is provide for a method for one discussion to reference another. Essentially it's the equivalent of an unregistered user saying "My post referenced yours, come read mine at <link>"

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Wedge and SMF directions
« Reply #37, on July 21st, 2011, 10:55 AM »
Suggestion. Trackbacks viewable by post author and moderators only.

Done through analysis of referred, rather than the usual protocol.
Bit like the google keywords mod here, but from other places as well.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge and SMF directions
« Reply #38, on July 21st, 2011, 10:59 AM »
So you'd record the different ways people find a given thread? Could be fun, could be a royal PITA as the log inevitably grows.

Being visible to author+moderators solves the problem of it being generally visible and problematic, doesn't quite so much solve the issue of it being generated in the first place.

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Wedge and SMF directions
« Reply #39, on July 21st, 2011, 11:57 AM »
Quote from Arantor on July 21st, 2011, 10:59 AM
So you'd record the different ways people find a given thread? Could be fun, could be a royal PITA as the log inevitably grows.
Obviously search engines would have to be logged separately from regular sites. We could either limit logs from search engines, or only keep the most recent logs as well as the top 10 ones, etc... Anyway, of course it's going to be a huge backlog, but it's also interesting. There could be a 'reset log' button, things like that... But it's never going to be as big a problem as 'regular' trackback spam.
Quote
Being visible to author+moderators solves the problem of it being generally visible and problematic, doesn't quite so much solve the issue of it being generated in the first place.
But what's the point in generating them *if no search engine can actually see it*? That's the whole point of spam... They don't particularly target human users, they mostly target spiders.

I'm sure there are PLENTY of places where we could eliminate user data from Google's eyes, and thus discouraging spammers from attempting to hijack Google's attention on a Wedge site. We're already doing it for signatures and website links through a permission, but maybe it should be a big on/off button saying, basically, "make spammers go away by limiting search engine options"...

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge and SMF directions
« Reply #40, on July 21st, 2011, 12:38 PM »
OK, look at it this way: while the onward effect of spam (it being visible to Google and regular users) can be curtailed, it's still there and it's still something that has to be cleaned up by the moderators in some way, and it's a source of incoming stuff that wasn't there before.

As it happens, there is actually a small module of Bad Behaviour tied specifically to trackback spam...

Just because spammers don't get any payoff, doesn't mean they won't spam, it just  means that human spammers are discouraged (doesn't stop them trying!) and bots will do what they do anyway.l

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Wedge and SMF directions
« Reply #41, on July 21st, 2011, 12:45 PM »
Quote from Arantor on July 21st, 2011, 12:38 PM
OK, look at it this way: while the onward effect of spam (it being visible to Google and regular users) can be curtailed, it's still there and it's still something that has to be cleaned up by the moderators in some way, and it's a source of incoming stuff that wasn't there before.
That's my point: there is *no* way a spambot author is going to waste time pinging Wedge-based websites because they'll just waste their bandwidth and their time.
Quote
Just because spammers don't get any payoff, doesn't mean they won't spam, it just  means that human spammers are discouraged (doesn't stop them trying!) and bots will do what they do anyway.l
But bots need to be written/modified to account for Wedge... And if they do -- they'll look at the source code and see it's pointless.

Also, if we don't use XML-RPC to implement trackbacks, we definitely can't get hit by bots randomly trying to spam any single domain name...
Of course we still get hit by random referrer bots (i.e. bots that simply browse the web with their 'referer' set to a spam page), but maybe BB can deal with that.
Posted: July 21st, 2011, 12:44 PM

Or we could scrape the original pages when the referrers hit us, and see if they have a link to us indeed. If they do -- add them to the list!

Re: Wedge and SMF directions
« Reply #42, on July 22nd, 2011, 06:54 AM »
Hmmm...much to consider here...and a few things to clarify as well....
Quote from Arantor on July 21st, 2011, 10:32 AM
To answer that...

1/ You misunderstand my contention regarding search friendly URLs. It is my contention that they do not help search engines, but the converse is also true: *not* having them doesn't help search engines either. The absence or presence of said feature, then, is virtually pure aesthetics. I'm not against pretty URLs provided that there is an awareness that they are purely aesthetic - to claim they have any kind of SEO benefit is BS.
The misunderstanding isn't mine, actually; it's an explanation I got from 2 different people who run other SMF boards. I don't personally know one way or another if that's a fact. I daresay that the bump we've hit here is a difference in level of experience/expertise and I, the taker of advice from numerous quarters, am at the bottom of the skill level scale.  What I've said is what I've heard--not what I know.  And so take your opinion as a valuable one in this respect (I'm still learning).
Quote
2/ I didn't say that it was WP's code that was the issue, because it isn't. There is an established protocol for trackbacks where you have inter-site communications, which must be implemented for it to work. A trackback facility that only one system uses isn't much help unless that one system is by definition, everywhere.

Gri's discussions aren't about trackbacks, they're about having the same discussion physically *duplicated* in two separate places so that there is no ability of one party to edit them.
I know that, and submit that this is why Gri sticks with only SMF boards. He hasn't (that I know of) attempted any of this on any other type of boardware. It is conceivable that what Gri thinks is possible is due to his own code skill level (not quite at your level but certainly better than mine). My interest in Gri's quest is similar but not identical--Gri's confinement to SMF boards only rather suggests that what he's after can be applied to a research discussion community, set of communities all of which use SMF, to allow cross-pollination, as it were, of interdisciplinary discussions.  A scenario would be a precision mechanical community cross-talking with a sensor-focused community, both of which cross talk with a GUI community, and what you get out of this is that each "team" focuses on their specialty while the cross-talk results in a robot.

You can't develop robots without being  interdisciplinary, and being too interdisciplinary results in a lack of focus due toward each component. It seems that you, as a member of a development team, can see the need for the specialties of core, themes, and add-ons but also see where it's critical that they all work together seamlessly.

Gri just wants  Freedom of Moving Thoughts because he gets his discussions interrupted by getting banned a lot. Me, I have other uses for this sort of capability, and have been on boards where I have wished THEY had this capability because of my going back to old posts and lines of discussions which have had to jump to a different board only to find that they've had to repeat themselves.  A board-to-board trackback of a discussion would mean that people didn't have to repeat themselves when jumping to a different board.

I'm in the process of reconstituting a thread of discussion that appeared on the now-defunct PBS Discussions board, and it's a helluva lot of work; had those discussions been portable, this task would be a helluva lot easier (although still a lot of work); having specific trackback links would be able to produce individual posts in, say, a Google cache. Conceivably.
Quote
The trackback protocol, as designed, is endemically flawed: it has no mechanism for authentication, consequently any site can generate a trackback, which means any site can *spam* you with trackbacks. Imagine a system able to post that doesn't require registration, doesn't require to enter a name but only has to posts a small snippet of text and a link back to their site. I have deleted many many spam trackbacks from InI but have yet to see one that wasn't actually spam.
I hadn't thought of that angle...thanks for bringing that to my attention.  However, I get spamming anyway. I don't see how anything I do reduces the spam attacks. All I can do is hope to have the tools to disallow them. Seems to me that right-clicking a post should produce the trackback without permitting you to post as if you'd hit the quote button as only registered members can do. Under the scenario you submit here, I agree that's a major vulnerability. I just wonder if it has to be a vulnerability when given more thought/design. "Make a better mousetrap spammertrap and the world will beat a path to your door", as it were.
Quote
3/ The concept of a trackback is cute, but as explained, the moment you start applying real life to it, it starts to fall apart. If you then proceed to implement a new trackback scheme, it's only valid as far as Wedge installs go: until Wedge is ubiquitous, implementing it in a new form is basically useless.
It doesn't have to be ubiquitous, and Gri's focus on exclusively SMF boards rather illustrates that point vividly. I'm certain he's aware that his Freedom of Moving Thoughts extends no further than only SMF boards and not across the whole of cyberspace.
Quote
Trackbacks do NOT make discussions portable if you listen to what the specification actually provides for: all it does is provide for a method for one discussion to reference another. Essentially it's the equivalent of an unregistered user saying "My post referenced yours, come read mine at <link>"
Well, that's the utility that Gri seeks, being a guy who gets banned a lot and who still wants to carry on whatever discussion got interrupted by the banishment. Shoot, I've been in that spot myself in the political debate arena and don't blame him a bit for looking for a work-around.  But like I said, my interests in his quest have a different application in mind, as outlined by the hypothetical robotics engineering teams talking with each other.

From what I've read about the ongoing friction between the fork and SMF prime, I have to wonder if such a capability would have resulted in a smoother sense of team operation.  But what do I know--I'm just an outside spectator.
Posted: July 22nd, 2011, 06:49 AM
Quote from Arantor on July 21st, 2011, 12:38 PM
OK, look at it this way: while the onward effect of spam (it being visible to Google and regular users) can be curtailed, it's still there and it's still something that has to be cleaned up by the moderators in some way, and it's a source of incoming stuff that wasn't there before.

As it happens, there is actually a small module of Bad Behaviour tied specifically to trackback spam...

Just because spammers don't get any payoff, doesn't mean they won't spam, it just  means that human spammers are discouraged (doesn't stop them trying!) and bots will do what they do anyway.l
Exactly. Thank you.
I would prefer to PM you about a slick li'l thing Gri did about spammers that I think is a minor stroke of genius. Don't want to talk about it in public, for now, but it's worthy of consideration, IMHO. If I implemented the scheme, I'd get into major trouble with my host...still...genius.

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Wedge and SMF directions
« Reply #43, on July 22nd, 2011, 11:04 AM »
I don't really see this as a realistic feature for gri...
If all he wants is to avoid the 'discomforts' of being banned, a 'trackback' conversation isn't going to help.
- Either he wants to prevent his posts from being deleted... Well, they're still going to be deleted from the remote thread, aren't they? One would have to know about his website to go there and read the rest...
- Or he wants to keep being able to answer posts on his site, even though he can't them on the remote site. What's the point? He can do it without 'trackbacks' or whatever...

In any case, when someone bans someone, generally it's with the intent of no longer being 'bothered' by said user. And that includes deleting all of their 'guest' posts or whatever posted after the ban took effect, generally...

As for non-banning trackback methods, I don't really see much of a point either. I do have a sort of trackback system as per my 'latest posts' box at cynarhum.com pointing to noisen.com messages (different servers really), but it's a hack, and I did that only as a way to easily redirect people.
It would actually be, uh... Simpler to implement a RSS->post/RSS->topic function, and have people post feeds to remote threads.

Anything more elaborate would encompass transmitting user details for each post though the pipeline, so that the remote forum can try and associate posts with its local members. It's hit or miss. But having guest posts for non-guest users is not desirable to me.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Wedge and SMF directions
« Reply #44, on July 22nd, 2011, 11:28 AM »
Let me clarify something, as I did have a few meaningful conversations with Gri a while ago and the only reason I issued him a moderation-level warning on arantor.org was because he didn't understand the concept of 'no.'

Trackbacks are designed solely for pointing between posts, so that if one blog post refers to another, the later post automatically notifies the original and appears as a reply with a snippet of the post, and the link to the newer post - the idea that the later post will "continue the discussion" and interested parties can continue the discussion elsewhere, but the reality ends up being "oh, I found this post, it's cool, isn't it?" and generating not-quite-spam.

Freedom of Moving Thoughts is something else entirely, it physically copies posts between forums so that two independent forums have the same actual discussion going on, this way there is no risk of sanctions being levied.

I'll reply to most of this later, but the one thing I will add is that the concept you're referring to at the end is a honeypot, something that have been set up to log spammers by the httpBL project...