Show Likes

This section allows you to view all posts where this member received or gave a like to.

1
The project / Re: Definitive name for fork
Farjo « on August 30th, 2013, 03:04 PM »
Well there's weaverboard (in English sounds like "weave a board") which has most domains except com available.

But I'll argue below that changing the name is harmful and unnecessary.
Quote from Powerbob on August 30th, 2013, 03:09 AM
I know what you mean, why change something that ain't broken? Who gives a shit about Facebook likes anyway!
:hmm: I like Wedge, but I'm pretty sure I've never liked anything on FB ever. It's not a sound method to judge popularity.

As I said in the other thread the name Wedge is slowly becoming known as a long-term concern; changing the name will throw that recognition away.

A name change now will make the product look unstable, and who wants to run their board on an unstable product? Highlighting internal difficulties to the majority who aren't really paying attention yet is another way of keeping people away.

For people using SMF the easy route is to switch to ElkArte, and if you want more than us few to try Wedge you need to 1. inspire them, which you've done very well. And 2. give as few reasons as possible not to change - as argued above a name change will make the product seem short-term and unstable, two reasons not to switch.
2
The project / Re: Lost in a sea of uncertainty
Farjo « on August 28th, 2013, 12:05 AM »
Quote from Nao on August 27th, 2013, 01:04 AM
...but I probably don't know your work as well as I do theirs ;)
Oh I'm not a coder, it was just a stupid joke - mocking my lack of programming skills. Difficult to do on the web, more so on an international one.

I see what you're saying about Pete :( So why not leave it as 'Wedge'? After all when you leave and others take over you wouldn't expect them to name change. Microsoft didn't change their name when Bill Gates stepped down; Apple is still called 'Apple'.
3
Features / Improving search
Arantor « on August 9th, 2013, 07:40 AM »
So I've been thinking about searching and the way searching works and I've concluded a number of things.

1. I want Sphinx and ElasticSearch in the core
Both Sphinx and ElasticSearch are pretty mature. Both have live update features now, so there's no reason we can't support them both with a sort of push mechanism (rather than Sphinx's pull mentality, like the old API was geared for)... the API needs rewriting to support either anyway and I might as well do it all together.

2. I want to natively support other types of data than posts.
The current setup doesn't support anything other than posts and I want to natively offer support for other stuff - calendar, helpdesk etc. The backend can support these extra things with some work, and pushing these also allows nice support in both ES and Sphinx.

3. It adds some nice feature parity with other systems without adding a ton of headaches for support.
XenForo offers ES with a $60 plugin, though I'm not entirely sure why. IPB has Sphinx in the core. Neither appears to have a huge support overhead because of them. And for the most part once they're done, they're done from our point of view.

4. The most controversial aspect of this is what I want to propose last: ditching unindexed searching.
Right now, the default searching method in Wedge is as it is in SMF: no index. It's slow, and doesn't scale beyond a few tens of thousands at peak. In fact, where we are right now on wedge.org is probably about the limit of what we can do with an unindexed DB before performance starts to go nuts. (40k is really the upper limit)

Now, partly this is because we've never configured it to be anything else, and most people just wouldn't know to do so because they wouldn't know any better. Now that's fine, because we know that people don't generally touch the settings unless they're directed - but using the search index would deliver better search performance from about 1k posts and up (and largely a push in performance terms for where things are right now for fresh installs)

I see no reason why 'no index' ever needs to be a valid search type. I'd suggest dropping that entirely and using the 'no index' option to mean 'no searching'. And then leaving the other index types to be actual index types, which would simplify the search code as well (and properly allow for it all to be segregated back to the APIs, some of which has already occurred but plenty more still to do)

This would leave us with three working search types (standard - formally known as custom, ES, Sphinx), of which 'custom' would be set as default on installation and would be populating posts as they are created (rather than having to deal with a huge index creation at once)

ES and Sphinx are both VPS level options, but there's no reason we can't have people pushing content to these indexes while using the custom index - plus of course there are always options for rebuilding indexes.


Does any of this make sense? Any questions?
4
Other software / Re: SM.org compromised
Arantor « on August 4th, 2013, 07:01 PM »
OK, so here's the point I don't get. If the account was 'compromised' and someone else took it over, changing the password should have fixed that entirely. It seems funny that that never happened.
5
Features / Re: Calendar
Arantor « on November 15th, 2012, 05:04 AM »
Just going to leave this here :whistle:
6
Archived fixes / Re: Linktree
Nao « on October 19th, 2012, 11:28 PM »
And... Nailed!! (It was a clip issue. I forgot to account for the shadow width and resorted to an inset out of laziness...)
7
The Pub / Re: Bloc Madness
Nao « on August 9th, 2012, 11:55 AM »
I posted a long answer over there... Since it's a pre-moderated message (meh), I'm posting it here in case Bloc doesn't approve it...
Quote
Quote from Xarcell on August 9th, 2012, 01:19 AM
I really hate to hear it Bloc. I was waiting for viennabbs also. I even resigned from Dream Portal. Oh well, it is what it is.
I'm curious to see how long it will take you to innocently come back to wedge.org and discuss the upcoming release when you didn't exactly have nice words to say about it just last month when you had ViennaBBS to look forward to ;)
Don't forget about EosAlpha, either...

Bloc, I just wanted to register to make something clear on your forum -- because in the end, it's always about two communities not talking to each other and having preconceived opinions about one another.

So, without further ado:

- Yes, I rejected your last suggestions about Wedge, and no, it doesn't mean I'm a bad guy.

- Yes, Pete and I always have the last word on Wedge. But because we're the decision makers, we also have a huge responsibility to deliver on our word. And I'd much rather be 'powerless' at this point, and not have that responsibility. The stress level would be totally different.

- No, just because I rejected your suggestions, it doesn't mean I rejected you.

- And just because you have ego issues, it doesn't mean we don't respect you either. We do have ego issues, ourselves.

- I'd just like for it to make it clear that I have the utmost respect for your work and your skills, but that I don't think you're being fair -- to us, to your users, and to yourself. If you're going to make ViennaBBS, then do it silently like we did for a year with Wedge. Don't mention it, then say you're giving up, then resuming work, then giving up again. Just say it's something you don't have plans to release before 2015 or something, and people will lose immediate interest, while still trying to follow what you're doing. It'll be less messy.

- If you're going to complain about Wedge, say anything you like because it's a free country (well, France and Norway are free countries anyway), but I can't let you say it's a "developer-centric SMF" that is not thought out for themers. I spent many, MANY months of my life working on the CSS preprocessor for Wedge. It's a work of art in itself. I may not be as good a designer as you are, but I certainly know what designers need to make their life easier. And you even agree yourself to a point -- recently you mentioned how SMF required of themers that they overwrite index.css to replace some stuff in it, and you pushed towards being able to add on top of it. Well, as you know it's a feature that's been in Wedge for over a year and a half now...

So, I'm simply asking of you to be fair to us. We really liked having you onboard. Just because you didn't feel comfortable not having any actual control over Wedge itself doesn't mean we disrespected you in any way. You're in the same position as everyone else but Pete and I... Had you joined the project on day one, it might have been different, but at that point we were already the two-headed entity that became known as Wedgeward and we locked everything for everyone, including our close friends like Dragooon or live627 (who will gradually get more power over Wedge).
We made Wedge because we weren't happy with SMF's direction and lack of commitment of its team, not because we hated the software as it was at the time. Effectively, we left because the SMF team was too narrow-minded per se, what you're accusing us of being. And you were part of the team at the time.

I'm just wondering... What does 'narrow-minded' mean to you? Someone who doesn't think your way?

(Shamelessly inspired from Eugène Labiche's "An egoist is someone who doesn't think about me.")
8
This is something that's annoyed me a bit about SMF in the past, curious to know what people think.

At the foot of the board index, you get icons indicating whether a board has new posts, no new posts or is a redirect board.

Even if you don't have any redirect boards, it still shows up. I figure it should hide that if there's no redirect boards. It's a trivial enough matter to do since we'll know by that point if we've had any redirect boards.

Thoughts?
9
OK so I just finished my first run-through of the signature file for ZB Block, was able to make sense of it without dissecting all of it (which is nice, but note that it is not possible to do that so easily in Wedge's code, heh)

Some interesting flourishes, some very interesting hard-coded blocks implemented there, makes BB look tame. To put it in context, our BB implementation is using about 300 lines of logic to handle all its checks, some of which are multi-line for readability, as opposed to ZBB which uses ~1500 lines at one rule per line... it's a massive piece of work and not surprising that it is more effective at stopping things.

After looking through the list I did also then start looking at the main code, mostly to see how the strikes system works; it has the ability to see if an IP hits a block three times and if it does, it then starts throwing a 503 error instead of a 403, smaller and more minimal and likely to encourage a bot to go away. But I really don't like how it handles such caching, it's all done with files instead of a DB which gets into writability/permissions (yay) and I'm not entirely convinced that it is faster than using a database.

What I will say is that the blocklists for bad hostnames, IP addresses and user agents is very thorough, some of the malicious URL types are a bit vague but it is trying to be a generic solution rather than one like BB which was written for WordPress first and foremost and anything else is something of an afterthought.
10
The Pub / Re: The Cookie Law (in the UK at least)
godboko71 « on June 20th, 2012, 06:38 AM »
How is asking users if its okay to store a cookie a stepping stone to limiting free speech? I don't follow the logic. It is in no way limiting you, about all it does is maybe add a small amount of work.

If you or the software you use ask the question, you know it was asked, so you have proof, so they can't come after you just because they have cookies from your site. Say you let the browser do the work, you have zero proof that they clicked I accept, so they turn you in and you get fined. Oh yeah the user turned off the the cookie question because they didn't read the check mark that says don't ask again.

Do you really trust browser makers to implement a standard that works worth a darn.

Plus, your site still have to interact with the browser, yes send them the cookie, okay you get to sign in, no don't send cookie. Send them to a page that explains why they can't use that part of your site. So at the end of the day you have the same extra work, it still have to play nicely with the big four.

All your freedoms are limited already anyway, your freedom can't encroach on Tims freedom over there. You can say you don't like red heads, that's your right. You can refuse to interact with redheads, that's your right. You have no right to limit what Tim the redhead does. Your right to not like him ends when you don't want.

You can still do whatever you want with your site, this law and others like it in no way limit what you as a site owner can do.