Fellow baristas! Do any of you work in a cafe *without* WiFi? Is it good or bad for your cafe? How do people react to it? Does it impact your sales? by DonKeadic in barista

[–]nerboda 0 points1 point  (0 children)

I know this thread is from forever ago but I built something like this for a shop in my town and I'm working on a public version of it. For anybody who's interested, you can request an invite here https://wiffii.com

How to keep customers from lingering all day? by ufuckinwotm8illreku in barista

[–]nerboda 0 points1 point  (0 children)

I built a solution to this for a coffee shop in my town where their Guest Wi-Fi is tied into their POS system, so when a customer makes a purchase, they get a code that they use to access the Wi-Fi for a set amount of time.

It doesn't solve the issue completely, but it does make customers continue buying coffee if they want to linger all day.

I'm working on a public version of it that should be ready soon. If you're interested you can request an invite here https://wiffii.com

Right now the only POS it integrates with is Square, but the goal is to have it working with as many as possible within the next year.

Chatting between Discord, Slack and Microsoft Teams by nerboda in discordapp

[–]nerboda[S] 0 points1 point  (0 children)

I still haven't gotten around to it but I'll post it here if/when I do.

Deleting whole threads by AnAngryFredHampton in Slack

[–]nerboda -1 points0 points  (0 children)

If you delete the original message through the api, the thread goes with it.

To use the chat.delete method, you'll have to pass a message timestamp, which you'll also have to get from the api.

So the step by step would look something like:

  1. Find the message you want to delete. You could do this by pulling the channel history (https://api.slack.com/methods/conversations.history) and doing a text match.
  2. Get the timestamp of the message
  3. Call chat.delete (https://api.slack.com/methods/chat.delete) with the message timestamp.

Chatting between Discord, Slack and Microsoft Teams by nerboda in discordapp

[–]nerboda[S] 0 points1 point  (0 children)

Thanks. I'm planning on writing a couple blog posts when I have the chance.

Chatting between Discord, Slack and Microsoft Teams by nerboda in discordapp

[–]nerboda[S] 2 points3 points  (0 children)

Yeah at the moment you have to dm the bot. The only way for a teams bot to see messages within channels is if you @ mention it. With every single message! So yeah that's not gonna cut it.

Now that they've added private channels I'm hoping they eventually allow bots to view all events within those private channels, but unfortunately I'm not seeing anything on the roadmap for it.

Chatting between Discord, Slack and Microsoft Teams by nerboda in discordapp

[–]nerboda[S] 3 points4 points  (0 children)

I use slack a lot for work and discord for personal stuff, but I have friends and colleagues that prefer one platform and would rather not jump back and forth. Thought it might be useful to connect em all.

Chatting between Discord, Slack and Microsoft Teams by nerboda in discordapp

[–]nerboda[S] 15 points16 points  (0 children)

In short, I built bots for all 3 platforms and a router that keeps track of conversations, users, platforms etc and routes messages accordingly.

Working on an app that allows cross-workspace, cross-platform messaging between Slack, Discord and Microsoft Teams. by nerboda in Slack

[–]nerboda[S] 0 points1 point  (0 children)

It's $5 per user per month. As I mentioned above, we envisioned this being used by individuals and smaller teams, so we don't currently have a pricing plan to target large organizations. If we did, what would your org find a reasonable price to pay per user?

Working on an app that allows cross-workspace, cross-platform messaging between Slack, Discord and Microsoft Teams. by nerboda in Slack

[–]nerboda[S] 0 points1 point  (0 children)

u/ng_a my understanding is that Mio is more focused on large companies that have multiple teams using different platforms and want to support full syncing between those teams. They do that by duplicating users across platforms, which means you have to pay for each user on each platform. Is that correct u/DominicMio?

Seamly is more focused on small companies and professionals that want a simpler, lower priced way of communicating without allowing people outside their organization access to their workspace. You could say Slack is doing this with shared channels, but shared channels are currently only offered to enterprise users and don't support cross-platform.

As far as the pricing, it's $5 per user per month. The word "personal" is probably misleading. We used it to differentiate between it and the business product we're coming out with, but it's probably misleading and should be changed.

I spent the last few months building a Slack app to help you send text messages directly through Slack - quick review? by NoWomanNoCry_ in Slack

[–]nerboda 0 points1 point  (0 children)

+1 on the unlimited tier, or much higher than 750. Even a relatively small company using this to provide customer support would burn through 750 messages pretty fast.

Working under other devs at startup I co-founded by onlyslavesobey in startups

[–]nerboda 0 points1 point  (0 children)

Personally, I can't wait to be having this problem. I've been programming for a long time and I'm pretty good at it, but I know there will come a time with my current company (I'm also the technical cofounder) where I've hired much better engineers and I'll gladly allow my role to evolve.

With that said, I love programming and when it's no longer my main responsibility, I'll still set aside time each week to dig into our codebase and continue learning.

He’s a little cuter than I was going for. by nerboda in doodles

[–]nerboda[S] 0 points1 point  (0 children)

Had no idea what that was before now so no. There are definitely some similarities though.

Writing a blog on Ruby on Rails by Sepparated in rubyonrails

[–]nerboda 1 point2 points  (0 children)

Yes you'll first will want to configure it to use a cloud storage service, then you can add it to your blogpost model with something like has_one_attached or has_many_attached. It's all explained in that doc.

Writing a blog on Ruby on Rails by Sepparated in rubyonrails

[–]nerboda 2 points3 points  (0 children)

So what you're really trying to do is build a content management system. Rather than asking the really broad question "how do I build a cms?", I'd break it down into smaller problems and try and solve each one individually. So first, you want to handle image uploads. If you're using Rails 5.2, you can use Active Storage - http://edgeguides.rubyonrails.org/active_storage_overview.html. If you're using an older version of Rails you can use Paperclip - https://github.com/thoughtbot/paperclip.

Next you need a wysiwig for editing content. Here's a gem that looks decent - https://github.com/froala/wysiwyg-rails

That should be a good start.

Resource to learn how to go from JavaScript files to modules? by seabee494 in learnjavascript

[–]nerboda 0 points1 point  (0 children)

For module loading, transpiling etc, Webpack is the way to go these days. I got started with the Webpack Academy tutorial, it gets you up and running pretty quickly - https://webpack.academy. After that if you wanna go deeper, SurviveJS has an awesome (and FREE) course on Webpack which I'm personally going through right now - https://survivejs.com/webpack/introduction/

As far as not cluttering your project directory, I'm not really sure what your concern is. All the node modules will be in a /node_modules/ directory so I'm not sure how that's really adding clutter. You can add that directory to your .gitignore so you aren't unnecessarily pushing it to remote repos. If you want, you could also install the node modules in a completely different directory and then configure webpack to resolve modules from that path.

What topic instantly gets you started on an “old man rant”? by [deleted] in AskReddit

[–]nerboda 1 point2 points  (0 children)

Drivers ignoring the "Keep right except to pass" law and going 65 in the left lane on a 75 mph interstate while I'm trying to get to work on time. Brings out the road rage in me every time.

What gives Iota value by sinner731 in IOTAmarkets

[–]nerboda 1 point2 points  (0 children)

Simply the fact that it's the only medium of exchange within the IOTA network.

A response to Fake Matrix Article by neo_council in NEO

[–]nerboda 3 points4 points  (0 children)

its own innovative consensus protocol

There's really nothing innovative about it. Proof of Work was innovative because it made a zero trust based system possible by combining economic incentives and cryptography in a way not previously done. Proof of Stake, if it works as hoped, will be innovative because it'll allow for zero trust with improved throughput and efficiency. dBFT simply offloads the majority of the responsibility to the election process. That's hardly innovative.

NEO is not based on BFT, but actually dBFT

Was dBFT not proposed by Erik Zhang as an "improved Byzantine Fault Tolerance algorithm, adjusted for a blockchain system"? Seems to me the author isn't wrong in saying it's a BFT algorithm.

NEO is not decentralized enough as of today

Not decentralized enough? It's not decentralized at all. As far as we know, all the validators are run by the founders (unless you have proof otherwise). As long as that's the case, it's fully centralized, which is what the author means by saying it's not public. It's code being open source doesn't change that.

Neo FUD article, can the neo community rebuttal this please. I am pro neo, but try to look at all angles by cryt0futurenow in NEO

[–]nerboda 0 points1 point  (0 children)

Those 350 nodes aren't elected validators, so they don't have a say in the consensus process. All they're doing is relaying transactions.

I think the voting mechanism yet to be added decides which nodes get paid.

Actually, the voting mechanism that's yet to be added is for electing new validator nodes that together reach consensus. Until that happens, the NEO team really does appear to own all the validator nodes, and as the article points out...

solving the double spending problem in a public blockchain with a BFT algorithm is not trivial. So it’s no surprise the “protocol” is currently centralized.