Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Nao
8221
Other software / Re: "Paid for" shit & shame on the SMF team
« on August 6th, 2011, 09:45 AM »
http://www.bryandeakin.com/index.php/topic,941.msg9366.html#msg9366 (follow up)Quote from Arantor on August 5th, 2011, 10:45 AM "My hands are tied! I've got an executive job, but I can't do a thing without a 97% majority, meaning we're stuck in a time loop, SMF2 isn't coming out before 2027 and I don't know what's the point of my entire life! I'm drowning, help!"Quote Yup... I'm in the process of removing the updating. Well, it's done but I'm a bit lost with all the language strings :PQuote Yes.Quote YOU do that. :P I have to admit I don't go to these places, unless told to. :^^;:Quote Nobody will. The only realistic (?) solution would be for vblamer to resume work on SGL. But it's not in his interest!Quote Yes. Otherwise it's $50.
And add another $50 for copyright removal. (But since I don't allow copyright removal from the free version of AeMe, I don't count that one in the price.)Quote Hmm... Yeah.Quote If they do end up deleting all Wedge links (also see the topic at Runic's place), then it's war (again), and I'll remove AeMe and all of my other mods.Quote Don't forget that out of all their members, 99% only visited a couple of times to ask a support question... And the vast majority of SMF admins doesn't even have an account at sm.org. They just (happily) lurk, like I lurked for 2 years before finally using my account over there. And the people currently looking into installing SMF2 and setting it up are poised to find out about AeMe because of the mod site, and thus hear about Wedge.Quote Yuh.Quote They could then say the same about Aeva Media -- except that it has its own license.
So why couldn't I have my own 'license' for posts?
Especially posts not related to SMF support...
I don't honestly care what his actual intentions were, but it seemed to me for much of the time as though it were lip-service.
On the subject of the sitelist, I'm inclined to agree with you; while it could be folded into the scheduled tasks, it seems like it should just be removed.
Just a case of keeping eyes on the prize, you know?Quote SMF flames are just an aside for me, eh
Sure you can, we both know that.Quote I can reply in plenty of places -- Bryan's place, SMF-friends, etc...
True enough. I half wonder if someone else will take up the mantle of a new gallery mod as, if and when Aeva Media disappears from SMF's ecosystem, but realise it isn't my problem.
Is it $80 when you include the video addon module?
And add another $50 for copyright removal. (But since I don't allow copyright removal from the free version of AeMe, I don't count that one in the price.)
So it being over there only benefits them, then?
I know there's an argument about promoting Wedge, but you know as well as I do that they're only going to continue censoring.
Sure it does. But only if the team doesn't keep censoring it. Most people don't leave sm.org, heck I'm not even that sure how many of them visited Noisen or here to be honest...
What you've been doing isn't "totally legal" - that's the point. It's fallen foul of several of the unwritten laws of SMF, for which the penalty is censure. Just because it doesn't fall foul of their published and public laws, doesn't mean it is legal, you know how good they are at reinventing and reinterpreting their own rules.
They can and will argue that the posts document an extension to the SMF project and thus fall under the CLA.
So why couldn't I have my own 'license' for posts?
Especially posts not related to SMF support...
8222
Features / Re: Core/Not Core
« on August 6th, 2011, 08:24 AM »
We're miserable, that's what we get.
That's the problem with being smart. You think too fast and you're unhappy.
That's the problem with being smart. You think too fast and you're unhappy.
8223
Features / Re: These two bytes may not matter to you...
« on August 5th, 2011, 09:09 PM »
$(window).load(function) is really a jQuery way of adding a load event to the onload queue. So it effectively solves the multiple trigger issue ;)
Basically, anywhere I can use jQuery, I'll try to use it. (Except on performance critical functions. But I have yet to see a real one in SMF/Wedge :P)
Hey Karl, I was just working on your PM! I've got a large backlog of long PMs and posts to answer to... Can't work... ahhh >_<
Basically, anywhere I can use jQuery, I'll try to use it. (Except on performance critical functions. But I have yet to see a real one in SMF/Wedge :P)
Hey Karl, I was just working on your PM! I've got a large backlog of long PMs and posts to answer to... Can't work... ahhh >_<
8224
Features / Re: These two bytes may not matter to you...
« on August 5th, 2011, 05:40 PM »
Eheh.
(Committed in rev 907.)
Posted: August 5th, 2011, 05:27 PM
(Committed in rev 907.)
8225
Features / Re: New revs
« on August 5th, 2011, 05:39 PM »
rev 907
(7 files, 11kb) <-- much less than the time spent on it, comparatively :P
- Deleted stupid addLoadEvent() and rewrote the last couple of items that still used it to use better equivalents ($(window).load() and add_js). (install.php, upgrade.php, Subs.php, script.js, theme.js)
! When hovering out of a top-level menu entry with no submenus attached to it, it would remain highlighted for a second because the hover class was being removed from the wrong element. (script.js)
! Fixed one remaining occurrence of a wrong $.trim() implementation. (script.js)
* Simplified version retrieval at install time. (install.php)
* Changed the default minification process to Packer. I figure if modders can't make it work on a default install, they'll be more cautious about this whole semicolon issue, and I'd rather have to deal with modder issues than with user issues once they enable Packer. (install.sql)
- Removed outdated holidays from the calendar. (install.sql)
* Keep-alive timeout should be using a function name rather than a string. Same for the toggler object and menu_hide_me at one point. (script.js)
* Plenty of minor cleanup operations. (editor.js, script.js)
(7 files, 11kb) <-- much less than the time spent on it, comparatively :P
- Deleted stupid addLoadEvent() and rewrote the last couple of items that still used it to use better equivalents ($(window).load() and add_js). (install.php, upgrade.php, Subs.php, script.js, theme.js)
! When hovering out of a top-level menu entry with no submenus attached to it, it would remain highlighted for a second because the hover class was being removed from the wrong element. (script.js)
! Fixed one remaining occurrence of a wrong $.trim() implementation. (script.js)
* Simplified version retrieval at install time. (install.php)
* Changed the default minification process to Packer. I figure if modders can't make it work on a default install, they'll be more cautious about this whole semicolon issue, and I'd rather have to deal with modder issues than with user issues once they enable Packer. (install.sql)
- Removed outdated holidays from the calendar. (install.sql)
* Keep-alive timeout should be using a function name rather than a string. Same for the toggler object and menu_hide_me at one point. (script.js)
* Plenty of minor cleanup operations. (editor.js, script.js)
8226
Features / Re: These two bytes may not matter to you...
« on August 5th, 2011, 03:31 PM »
addLoadEvent, as of now, is simply an alias to $(window).load(), which also carries the task of converting a string into a function (through new Function()). I was parsing the script.js file through JSHint (not JSLint) and wanted to fix a few of the notes (although on a performance note, this doesn't help at all so I won't use JSHint on all scripts in the end), and it did point out that Function() was compiled at execution time, and that it was bad, etc etc. So I went and looked for addLoadEvent calls, and it turned out I'd already converted all strings to functions, so this was only left in as emulation code. However, *Wedge is friggin' not compatible with SMF* to begin with. So I don't really see the point in having this function anymore... I'd rather encourage the use of other solutions ;)
8227
Features / These two bytes may not matter to you...
« on August 5th, 2011, 12:31 PM »
(I decided I'd make this into a general purpose topic about my stupid micro-optimizations :P)
I had a look at addLoadEvent() in Wedge, and I can confirm that none of the calls use a string format at all. Heck -- it's actually used only 3 times in the entire codebase by now: to resize avatars on the fly, to resize images when clicking them, and to fix the code box sizes in FF, WebKit and IE. This last one I don't think even deserves being called through .load() but simply directly... Heck, I don't even know if the bug is still a valid one!
Thus, it even seems a bit odd to be using it when we could simply call $(window).load, although it's two bytes longer, but well, it also saves a function alias and declaring the function to begin with in script.js :P
Of course there's the possibility of modders calling addLoadEvent themselves, but... err... Since we're not compatible anymore... Maybe it'd be time for them to determine whether they want to use add_js() or DOMContentReady instead (i.e. anything that doesn't require images to finish loading...)
What do you think?
I had a look at addLoadEvent() in Wedge, and I can confirm that none of the calls use a string format at all. Heck -- it's actually used only 3 times in the entire codebase by now: to resize avatars on the fly, to resize images when clicking them, and to fix the code box sizes in FF, WebKit and IE. This last one I don't think even deserves being called through .load() but simply directly... Heck, I don't even know if the bug is still a valid one!
Thus, it even seems a bit odd to be using it when we could simply call $(window).load, although it's two bytes longer, but well, it also saves a function alias and declaring the function to begin with in script.js :P
Of course there's the possibility of modders calling addLoadEvent themselves, but... err... Since we're not compatible anymore... Maybe it'd be time for them to determine whether they want to use add_js() or DOMContentReady instead (i.e. anything that doesn't require images to finish loading...)
What do you think?
8228
Features / Calendar dates
« on August 5th, 2011, 12:26 PM »
As I mentioned in another post (in the team boards), I think it'd be nice to be able to translate holidays into other languages.
Most of these holidays are English-centric though -- e.g. St Patrick's Day? I think 95% of the planet doesn't have a clue what it's about... I think it's Irish or something. It's all I know. I would tend to either delete this one (and maybe a few others like Halloween), or add more. Why does the database have the national days for the US and Mexico, but not other countries? It always seemed to me like it was an unfinished feature...
We could these dates out of the default package, and offer add-ons that will simply insert dates in the database. We could then have a US date database, a French one, a Zimbabwean one, etc...
Or maybe we could add a field to the dates, specifying which country/culture should be able to see a date.
Opinions welcome on these matters!
Most of these holidays are English-centric though -- e.g. St Patrick's Day? I think 95% of the planet doesn't have a clue what it's about... I think it's Irish or something. It's all I know. I would tend to either delete this one (and maybe a few others like Halloween), or add more. Why does the database have the national days for the US and Mexico, but not other countries? It always seemed to me like it was an unfinished feature...
We could these dates out of the default package, and offer add-ons that will simply insert dates in the database. We could then have a US date database, a French one, a Zimbabwean one, etc...
Or maybe we could add a field to the dates, specifying which country/culture should be able to see a date.
Opinions welcome on these matters!
8229
Other software / Re: "Paid for" shit & shame on the SMF team
« on August 5th, 2011, 10:28 AM »I would suggest to remove the files, blank the page, then delete, no,sorry, remove it from the list. Possibly even wipe the actual post, if a post-ban didn't remove that ability. So as to maximise the damage, so to speak.
8230
Other software / Re: "Paid for" shit & shame on the SMF team
« on August 5th, 2011, 10:26 AM »There was communication for a while. I did spend a while trying to talk Kindred round, far, far more than was ever really known.
But these discussions came into a dead-end. We were so frustrated that, after another issue with credits, I did the only thing I could to show my discontent -- moving the SMF copyright to the credits page, which led him (and not anyone else) to remove me from the site credits.
So-- whatever he has to say about this... I don't see WHERE exactly he put much effort into helping us. To me, it seems like he never planned to help, and decided to hide behind the 'SMF team majority' crap to justify not helping.
:lol: This is the SMF team we're talking about here. Making rules clear? The only time I ever saw clarity in the rules are when there was a fuss made about mods that had adult site links, and Unknown understandably got very annoyed with it.
[OT] Oh, and which makes me think -- I don't know if there's still a point in having the sitelist auto-update itself. The online video landscape has shown a few clear leaders (YouTube, Dailymotion...), they're the ones that we should be careful about. Other sites, well, if they break, people can afford to wait for a few weeks to get a new Wedge update with new links...
I have nothing to disagree with here, except what we should do about it. Instead of any further retaliation, let's instead do the one thing they can't prevent from doing: making Wedge better and better.
SMF flames are just an aside for me, eh ::)
I think the difference is, because you'd been post-banned, you wouldn't have been able to reply to a message, so they figured they wouldn't bother.
Of course it does. It also means there is a free competitor to vbgamer's paid stuff. I wonder whether he will be encouraged to make it free once AeMe disappears.
Anyway---- SMG was out, and quickly surpassed the 'quality' level of SMF Gallery Pro -- we saved SMF users a grand total of $80 by giving them an alternative to that piece of crap[1]. And that's what is making SMF look good these days, too -- none of the free forum software offers a free gallery system that is as complete as SMF's Aeva Media. That's the whole thing, the whole point. None of the other free devs was crazy enough to spend two years on a project that could not be monetized in a realistic way.
That's one of the major strengths of SMF, and they're not willing to lose it. Otherwise I'd have been perm-banned all the same...
Neither do I.Quote Fuck. I don't even know why I still have AeMe online over there...
1. It's not a piece of crap because of its feature list, which is actually pretty much on par with SMG/AeMe when it comes to SMF Gallery Pro, but because of the crappy code. Erk. An abomination.
What do you think! They can keep Aeva Media as long as they also give me free reigns to advertise its upcoming upgrade. What I've been doing on that page is totally legal, heck. *AND* it breaks absolutely none of their Core Values (to which they could pretend I'm tied to, even though I never was made an official teamie), and none of their written rules.
The rest is ego wars and solo decisions -- like Kindred's decisions to censor me.
The team will argue that they are contributions under the CLA. I already had this argument with them.Quote Even my posts. They're not contributions. Give that to a lawyer, anyone will laugh at them.
Remove my 6000 posts, guys. It's my right. I wrote them, I own them. I don't owe you shit.
No, they still don't own my stuff. They can own my posts written on the dev boards, my posts on the beta page, all of my posts related to SMF's development, no problem. But posts related to Aeva Media and stuff? No thanks. I own them. And if I ever take down AeMe from their page, I don't see why these posts should remain online.
8231
Other software / Re: "Paid for" shit & shame on the SMF team
« on August 5th, 2011, 07:25 AM »
In 20 days will be the anniversary of Wedge.
8232
Other software / Re: Nao in SMF2 Credits
« on August 5th, 2011, 07:23 AM »
Finding Wedge is no problem. I took the most generic domain name for it after all. The hard part is knowing it exists...
8233
Other software / Re: "Paid for" shit & shame on the SMF team
« on August 4th, 2011, 10:05 PM »
You don't need to defend me. I could care less about my future at smf. I only care about the fact that they censor me, and without any notice.
8234
Features / Re: Core/Not Core
« on August 4th, 2011, 09:11 PM »
It's just that there's so much to do/add... :^^;:
I've pretty much given up on it for Wedge 1.0 (otherwise we're sure to release in 2012...), but there are things I'd like to implement in 1.1 at least: the thought system, personalized profiles, etc...
I've pretty much given up on it for Wedge 1.0 (otherwise we're sure to release in 2012...), but there are things I'd like to implement in 1.1 at least: the thought system, personalized profiles, etc...
8235
The Pub / [Archive] Re: Logo Madness
« on August 4th, 2011, 09:10 PM »
Well it looks a bit like the 'Milky Way' chocolate bar logo, come to think of it... :lol: