How about The Likes Bots Thread? Where the bots post and we like?
Spencer
@Spencer
Best posts made by Spencer
-
RE: The Backup Likes Thread - Because it's not the same, now with semi(?)-mandatory likes and questions?
-
RE: The Backup Likes Thread - Because it's not the same, now with semi(?)-mandatory likes and questions?
Huzzah!
@SummonBot, do the honours please? -
RE: The Backup Likes Thread - Because it's not the same, now with semi(?)-mandatory likes and questions?
This one was started back in July after some comment that threads should be recreated once they become long (might've been Jeff that said that, I don't remember). It didn't survive long (not even to the following month). It was necroed just recently, first to lure @Luhmann away from the Likes thread (so he wouldn't overtake @boomzilla), and then to pay the ransom to @royal_poet for the safe return of @Arantor.
It will be kept alive for gamification for a little while before it's allowed to die again.
-
RE: The Backup Likes Thread - Because it's not the same, now with semi(?)-mandatory likes and questions?
Oh yeah, that's right. Because @Arantor wasn't able to come and post to defend his position.
It's been a long day.
-
RE: The Backup Likes Thread - Because it's not the same, now with semi(?)-mandatory likes and questions?
This may be acceptable. Disgust escaped for now.
-
RE: Please ease up with the bots
It's only now that I've posted it that I realise I inadvertently created "emotse"
-
RE: The Backup Likes Thread - Because it's not the same, now with semi(?)-mandatory likes and questions?
Mind sharing for our approval/disgust?
-
RE: The Backup Likes Thread - Because it's not the same, now with semi(?)-mandatory likes and questions?
Posting here in the hope that this thread hasn't been added to the Mediocre Poster badger blacklist yet and I can finally get said badger
-
RE: The censor feature is discoursistent
Getting this feature working "perfectly" is probably a month of engineering work. (deal with permutations, maybe dash in a bit of OCR
I can see why it might take a month, particularly with the OCR.
You have to develop an automated system of taking a screenshot of the post, printing it, putting it on a wooden table, taking a photo, scanning the result back in and performing the OCR. Quite a bit of robotics involved there.
Latest posts made by Spencer
-
RE: Microsoft is limited to receiving 100 emails per day?
@tsaukpaetra said in Microsoft is limited to receiving 100 emails per day?:
@spencer said in Microsoft is limited to receiving 100 emails per day?:
It literally costs you nothing but a little time to sign up
I tried just now. I guess I'm just special because I happen to use shared hosting, but it's literally impossible to sign up, therefore it costs infinite time to sign up.
Granted, this is not the same situation as @quijibo, but "literally costs" is very subjective here.
"Literally costs nothing" because the service is free. Do we still flag posts for pedantry around here?
Anyway, shared hosting is fine. From the Access Control page
So, other than I don't see what's preventing you.
-
RE: Microsoft is limited to receiving 100 emails per day?
@quijibo said in Microsoft is limited to receiving 100 emails per day?:
We only send receipts to our customers when they pay for a service. [...] What is most likely happening is that Microsoft's spam filter is automatically tagging our receipts as junk because they all look similar to each other, and even worse SNDS then uses the feedback from their spam filter false positives to trigger on.
Implying Microsoft's spam filter has never seen a receipt before. Or a newsletter. Or any other legit templated email.
That's why I asked for specific emails that users have submitted and not what some filter thinks is spam (before getting the reply about SNDS).
Why should that be my problem to figure out why SNDS is alerting our ISP? If I am confident that our server is not sending spam (and I realize that there are lot of servers that do get compromised) then I don't really care if my ISP wants to subscribe to SNDS. Just stop forwarding them on to me and everyone is happy.
These two statements seem incongruous with each other. Either you want to know why your emails are being considered spam, or you don't. I daresay a number of your potential customers may not have an alternative, non-Hotmail address and may be frustrated enough at not being allowed to use (and having to set up another somewhere else) it that they'd take their sale elsewhere. It literally costs you nothing but a little time to sign up, you'd get to learn why they're being filtered and improve your service for everyone. Not to mention bragging rights within your company for being the one that worked it out.
-
RE: Microsoft is limited to receiving 100 emails per day?
I don't think preventing Hotmail addresses would be enough, as there are other domains that go to the Hotmail servers, eg. @live.com, @outlook.com, including domains with the country-level code (@live.co.uk).
A quick search turned up some similar results about Outlook and Gmail send limits,but also this from https://postmaster.live.com/snds/FAQ.aspx
IP Address
This is the IP address of the machine that caused the activity displayed. In some cases, this may be the public address of a Network Address Translation (NAT) system, in which case there may be one or more machines behind that IP and there's no practical way for our systems to distinguish them. Be aware that mail traffic and spam data may not be present for IPs which sent less than 100 messages on the given day.From https://postmaster.live.com/pm/services.aspx#Section1, to me it sounds like warnings are only generated when a significant number of emails you've sent are being marked as junk
Smart Network Data Services
A free service that provides high-level insight on how users are rating the email they receive and the health of your IP space as viewed by the Outlook.com system- Provides easy online registration and access to data
- Improves understanding of how our filters rate your email
- Reveals how many users complained about your email
- Learn more at [ the link is missing. Seems like it's meant to be http://postmaster.live.com/snds, as below in the ISP Section]
Seeing as it's free, you could possibly sign up on SNDS and get access to better reports/data on why you're getting the warnings. While not the best solution, I get the feeling that having additional SMTP servers at other (different public) IP addresses would skirt around the issue.
-
RE: Xamarin's contiuing barrel of cross-platform, XML-encoding fut the wuckery
@bulb said in Xamarin's contiuing barrel of cross-platform, XML-encoding fut the wuckery:
@spencer said in Xamarin's contiuing barrel of cross-platform, XML-encoding fut the wuckery:
btw, since @Lorne-Kates is an ASP.NET dev, has anyone suggested doing whatever app this is all for as a PWA?
Yes, of course I did
@bulb said in Xamarin's contiuing barrel of cross-platform, XML-encoding fut the wuckery:
Effectively you can chose between: Cordova(+Ionic)/Electron (mobile/desktop), […] Since you did web, I suspect you would have much easier time with the first […]
That sounds like a web app. Not a PWA (distinct difference). PWA can be (and in a lot of cases, will be) an actual responsive web site, written in whatever you fancy, with javascript service workers for any background tasks, and converting/packaging it as a PWA. Even though they're web sites, a PWA is completely able to be run offline.
Google and Microsoft are actually working together on making sure this is supported on Android and Windows in their stores, and Apple may be coming to the table too.
-
RE: Xamarin's contiuing barrel of cross-platform, XML-encoding fut the wuckery
btw, since @Lorne-Kates is an ASP.NET dev, has anyone suggested doing whatever app this is all for as a PWA?
-
RE: "My double life as a software developer... and luddite"
@steve_the_cynic
yeah, I could've had a reasonable, logical guess at all those things. But it was more fun to come up with the silliest-yet-still-believable answers I could. -
RE: "My double life as a software developer... and luddite"
@polygeekery it was the last one, wasn't it?
-
RE: Xamarin's contiuing barrel of cross-platform, XML-encoding fut the wuckery
@mrl said in Xamarin's contiuing barrel of cross-platform, XML-encoding fut the wuckery:
my first reaction was "I have to write so much convoluted crap to bind a label???".
what convoluted crap are you doing that this doesn't work?
<Label Caption="{Binding TextToDisplay}" />
Or are you talking about building the MVVM framework by hand?I'll admit the Command boilerplate is a bit more than I'd like, but I don't think this is really too much
private RelayCommand _myCommand; public RelayCommand MyCommand => _myCommand ?? (_myCommand = new RelayCommand(MyAction)); private void MyAction() { // ... }
That Command boilerplate is the extent of any repeated code I ever write while using XAML. I like the Value Converters because they're independently testable, and very reusable across products. Instead of repeated code defining those converters again and again in each window/control/frame/page's resource dictionary, they instead go into either the app.xaml resource dictionary or a shared one. Same with data templates, styles etc. XAML in WPF and UWP lends itself very well to reuse.
-
RE: "My double life as a software developer... and luddite"
@polygeekery said in "My double life as a software developer... and luddite":
Wolverine's knuckledusters
scissors for making ruffled edges on banners/streamers
for people too retarded to use a pizza wheel
nit-comb, or getting those itches really good
pencil sharpener
someone decided to "improve" the kiwi spoon-knife and just fucked up
one of those drain strainers you see in urinals -
RE: Xamarin's contiuing barrel of cross-platform, XML-encoding fut the wuckery
@mrl said in Xamarin's contiuing barrel of cross-platform, XML-encoding fut the wuckery:
You are doing the same crapton of work, with a lot of repeated code, plus you type kilometers of xml. But it's placed in front xml and 'view model', so it's not 'codebehind'. And you don't do 'events', but 'commands', so it's automatically great.
Well no, I'm not. Binding takes care of that, all I have to do is assign values to properties in my ViewModel. XAML also means I have to do less work to adjust to window size changes, because that's automatically handled by the built-in layout engine and the container controls you've placed the other controls in.
There's no need to type kilometres of xml; it can all be done using Blend. Better yet, you can hand that off to an actual designer who just builds to the view models you've built with design-time data while you focus on the rest of the actual application logic.
I could go on about the virtues of MVVM in WPF/UWP, but it's also possible to use MVVM with WinForms, but again that requires more work - the bindings have to be set up manually in the codebehind, not to mention handling control's changed events (eg SelectionChanged) for things like ComboBox and ListBox.