patrick.net

Dan8267 says

@Patrick, you got rid of ban. Tolls being ignored can still comment on the author's thread. Ignore is a worthless function. We need ban.

I disagree, it is so much better to just hit ignore and remove all the noise from the excess posters (spammers). A reasonable adult is capable of ignoring trolls. Patnet doesn't need to cater to the safe space crowd.

He switched to Arm and Hammer back when the russkies rigged the elections...

PeopleUnited says

Dan8267 says

@Patrick, you got rid of ban.

PeopleUnited says

Dan8267 says

@Patrick, you got rid of ban. Tolls being ignored can still comment on the author's thread. Ignore is a worthless function. We need ban.

I disagree, it is so much better to just hit ignore and remove all the noise from the excess posters (spammers).

Ignore and ban are not mutually exclusive.

@Patrick, bring back ban.

marcus says

Some of us prefer not to see a few people's posts.

Speak for yourself!

ban
noun: official forbiddance
synonyms: boycott censorship embargo injunction prohibition refusal restriction interdiction limitation proscription stoppage suppression taboo a thou-shalt-not don't

I love the fact that on Patnet the above are used very sparingly and the snowflakes can't hide in a safe zone but rather must be held accountable by the other users for what they say by allowing anyone to respond in a civil manner like people do in a civilized world. The ban was always a bad idea and the ultimate form of incivility. Ignore is the epitome of civility on the other hand, allowing the children and the immature throw their tantrums and allowing us the civil people of Patnet to not respond to their idiocy or stoop to their level. This isn't a court room or a church service. It is a website for the exchange of ideas free from censorship. It is one of the last hold outs in an age of increasing censorship, intolerance and opposition of true free thinkers. Thank you for bringing back ignore and retiring the ban.

I liken it to this, suppose the KKK had a rally and the media didn't cover it. Hardly anyone would notice and therefore there would be no disturbance. Just let the racists have their puny rally and then be on their way. Suppose black lives matter had a march and the media didn't cover it it. Hardly anyone would notice and therefore there would be no disturbance. Just let the racists have their puny rally and then be on their way. Ignorance is bliss in these cases. There is NO NEED TO BAN people or comments just because you disagree with them, even if they are vile and hateful comments. Just ignore them. Or shun them with a strongly worded civil comment if you must virtue signal, but banning is not the answer. Tolerance is.

Hashtags don't work.

#example

Dan8267 says

Hashtags don't work.

#example

Thanks, will fix today.

Unignore does not work for user "null". Possible SQL injection vulnerability. Normally, I'd take advantage of something like this, but I'm too busy.

What's up with

please edit this and post just one video at a time, thanks

Multiple videos per post makes sense. Why prevent that? How are multiple posts better?

It was just simpler to implement. I suppose I should allow several, but not, say, a dozen.

Patrick says

Dan8267 says

Hashtags don't work.

#example

Thanks, will fix today.

OK, hashtags are fixed, with the requirement that the hashtag be the first thing on a line. When first on a line #housing will get transformed into a live link to the topic housing.

A hashtag added to a post will classify that post as within that topic. If there is no hashtag, the post will go into 'misc' until the author adds a tag.

Topic links (prev, index, and next) will be at the top of each post. So you can easily flip to the previous or next post within a single topic.

Site is still mostly not working on my phone. Android using Chrome or Dolphin.

Booger says

Site is still mostly not working on my phone. Android using Chrome or Dolphin.

Crap, what happens? Do you see nothing, or does the submit button for comments fail to work, or what?

BTW, I have fixed * for making things bold and underscores for making things italic and two (yes, two) double quotes around text to make it show up as a

blockquote

#first #second #third
#secondLine

So one hashtag per line then.

Patrick says

Crap, what happens? Do you see nothing, or does the submit button for comments fail to work, or what?

Usually the page just doesn't load, and I see nothing. On some occasions, the first page loads, but nothing else works.

Dan8267 says

So one hashtag per line then.

Only tags which start a new link will be linkified, and in a post (as opposed to a comment), the first one will set the post topic.

I tried to do more, but the regexp processing is kinda nasty because the hashmark could be part of a url, say. So it was simplest for now just to match a hashtag at the beginning of a line: https://github.com/killelea/node.patrick.net/blob/master/node/patrick_net.js#L302
Also, here are the currently acceptable html tags in a comment or post:

https://github.com/killelea/node.patrick.net/blob/master/node/patricknet.js#L340

Booger says

Patrick says

Crap, what happens? Do you see nothing, or does the submit button for comments fail to work, or what?

Usually the page just doesn't load, and I see nothing. On some occasions, the first page loads, but nothing else works.

Damn. Usually?

I have an old Android phone with Firefox and it works OK there. Are you on wifi or the phone data plan when this happens, or both?

Patrick says

I tried to do more, but the regexp processing is kinda nasty because the hashmark could be part of a url,

Wouldn't that be solved simply by requiring whitespace, newline, or start of string to be before the hashtag?

I solved it by requiring the hashtag to be the first thing on a line:

let hashtagPattern = /^#(\w+)/gim

How would the regexp look to match whitespace, newline, or start of string?

/(?<=[\s>]|^)#(\w*[A-Za-z_]+\w*)\b(?!;)

It's a bit longer, but it handles start of string, end of string, start of line, in mid-sentence, and filters out where # is not the start of the word (that's the \b). See this demo.

Patrick says

I have an old Android phone with Firefox and it works OK there. Are you on wifi or the phone data plan when this happens, or both?

Works on Wi-Fi, not when using mobile data.

OK, that's really interesting!

Maybe your mobile provider is blocking patrick.net. I'm on TMobile and that works. Who are you on?

Cricket. It's working right now. Difference is that it was trying to go to Patrick.net, so I tried typing in www.Patrick.net and it started working again. I have no fucking idea why this seemingly fixed it.

Very, very minor thing, but I don't think the comment count on the user profile is accurate. See these screen shots. My comment count has stalled since the switch to node I believe.

WookieMan says

don't think the comment count on the user profile is accurate

You're right. Will fix. Thanks for pointing it out.

Patrick says

WookieMan says

don't think the comment count on the user profile is accurate

You're right. Will fix. Thanks for pointing it out.

OK, comment counts are now updated correctly on user pages.

For some reason still not working for me. Cleared cache and restarted browser and comment count on user homepage is still the same. Click on the comments link and the pagination or whatever it's called for the comments shows 202 on that page vs. 129 on my user homepage.

It's only on the users page when they are logged in that it doesn't add up. Again not a big issue at all. I can go to another user and their comment counts are correct. So it's only when you're looking at yourself logged in.

@WookieMan thanks for telling me. Maybe I failed to push the new code to the server!

What if you make one more comment? Does that update the count correctly?

Let me check.

Yes, the comment count from users own perspective is correct now. I appreciate your work here. But you've just solved one of the most useless things I've ever requested to be fixed. Kidding aside, thanks.

Happy to help. Tell me more important things to fix too.

Damn, registrations were broken for a week. Fixed now.

Again, not a huge deal and not sure how I didn't catch it when comments weren't counting correctly, but posts don't seem to be adding up either. See screenshot. 5 on the screen and more below. Only 4 counted in my total.

For me, computational physics - python + fortran or C++

Personally I think it's all over and Javascript is coming to everywhere, soon.

It has some flaws, but it's otherwise elegant, very high performance, and has a monopoly on the biggest platform in the world, which is all the browsers in the world.

Patrick says

Personally I think it's all over and Javascript is coming to everywhere, soon.

It has some flaws, but it's otherwise elegant, very high performance, and has a monopoly on the biggest platform in the world, which is all the browsers in the world.

For web stuff for sure. However core backend technologies will stay with strongly typed and better structured languages such as C(#++)/Java/Scala/Erlang/Python/Go. You can't write a massive scalable, safe, and mostly bug-free project in JS. Also multi-threading is cheap today and making a come-back. Also the survey is questionable as SQL and HTML are choices next to major programming languages. I would expect JS to be first since it is used heavily in front and back-end and even in some middle-ware. If you were only talking backend-technologies it would not be at the top.

mell says

strongly typed and better structured languages

@mell You can always use https://flow.org/ to have strong types in Javascript, or assert() the typeof parameters at the beginning of each function.

For structure, yes, callbacks make code very hard to follow, but now that Javascript has async/await, you can write code that looks procedural. It's great and I use it all the time.

Patrick says

mell says

strongly typed and better structured languages

@mell You can always use https://flow.org/ to have strong types in Javascript, or assert() the typeof parameters at the beginning of each function.

For structure, yes, callbacks make code very hard to follow, but now that Javascript has async/await, you can write code that looks procedural. It's great and I use it all the time.

Love async/await would not touch JS without it. Still stuff like flow or coffee feel like crutches. I would avoid it for very larger and non-web projects, for small to medium web-projects it's great.