drchaos

"I give you $50 if you vote for me, you'll get it when I win the ballot"

If someone is willing to sell their vote in the first place, they have zero incentive to vote for another candidate. They only have to trust the buyer to follow up on his promise (which is required in any other scenario also).

Not OP, but https://dawarich.app/ seems to do the same (open source and self-hostable, also has an iOS App).

> Consuming and training on the whole internet doesn't make you smarter than the average intelligence of the internet.

This is only true as long as you are not able to weigh the quality of a source. Just like getting spam in your inbox may waste your time, but it doesn't make you dumber.

This is pretty interesting, I think you should do two things right now:

1. add a message box stating that it is experimental and has only a very small set of companies right now

2. add an option to get notified when you have a more complete dataset (just use a Google form to collect email addresses)

Reason: Searched for my company, no result, ok, we're too small. Searched for some DAX companies, no results either => site looks broken.

Additional ideas:

* Add information from insolvenzbekanntmachungen.de, it's a major PITA to find someone there * Provide a (paid) API so it can be integrated into shop systems etc.

A Creditreform membership is quite expensive, probably worth it for larger shops, but for small enterprise your solution might come in handy.

If npm or Ubuntu would deliberately replace a package with their own implementation, without giving you notice or making this opt-in, would you call that a supply-chain attack? I would, unless the original package contained malicious code (which is not the case with WPE's custom fields plugin)

It's standard for Euro amounts and before that for many (most?) European currencies.

One could argue that at least this specific tactic would not be possible without the state granting a monopoly on "intellectual property". Without that, nothing would hinder AMD from just shipping their already existing implementation.

alias wget='curl --wget', then?

How do you handle downtime due to project/package/os upgrades?

I do run a pretty similar setup for some projects, and in general I tend to agree with the author, especially when bootstrapping cloud services can cost quite some bucks for mediocre performance.

There is, however, one big disadvantage one should be aware of, and that is downtime. There will be downtime when you

* push a new version of your project

* install package updates for docker, postgres, ...

* install a new kernel and need to reboot

* need to upgrade the base OS because you can't stay on Ubuntu 16.04 for the next 10 years (this one can take hours)

Of course there are projects which can live with that. If your target audience is 9-5 office workers, some downtime at night might be acceptable. At least if you don't have customers in other timezones.

IMHO, the sweet spot would be to have two identical servers with automatic failover, but I did not find a good solution for that yet. Would be very interested if someone here has a solution for that and is willing to share.

Technically true, but still misleading, as the total production has gone down significantly:

2022: 491,8 TWh 2023: 436,8 TWh

So Germany is not replacing fossil fuels with renewables, it just produces less electricity overall. Which might be caused by the fact that electricity is so expensive nowadays, that especially energy-intensive industries are getting less and less economical, so they lower their production or even shut down completely and move elsewhere.

The actual title is "0x4 reasons to write and publish", probably it got mangled somehow.

Yeah, surely prohibition will work this time. /s

"I also have an account with xyz and there I don't have this problem" might be an effective addition.

It's absolutely possible to automate an "attested" phone with a physical robot finger, which is neither extremely complicated or expensive tech. It might be too expensive for mass-scale DDOS, but it would still be cost-effective for more interesting things like click fraud.

AI companies can just scrape the content, and since the sites don't have an exclusive license to it (it's user-generated, after all) there is little they can do against that.

Actually, I'm not even sure the AI companies don't do this already. If I'd start such a company, I'd invest in a generic crawler once, instead of building countless integrations for all the different, proprietary APIs or dump formats.

There are quite a few potential replacements for Reddit, but of all the projects I've seen so far, nostr checks the most boxes:

1.) They got identity right. In nostr, your identity is a key pair, which is not bound to a server like in the fediverse (e.g. Mastodon, Lemmy).

2.) They got decentralization right. Everything in nostr is a signed message, published to one or more relays. Since relays don't do anything more but store and forward signed messages, they can easily be replaced without losing your identity or data. Also, no blocking drama ("fediblock").

3.) They got extensibility right. Since signed messages are the only building block, and clients are only views over messages, new functionality can be added unilaterally. Just write a new client, and everyone can use it instantly with the existing identity and data - zapddit is a good example.

What's missing yet are moderated groups and an algorithm to sort your feed. But this can (and probably will) be implemented at any time by anyone, and there can (and probably will) be competing implementations, which is a big plus IMHO.

In the medium/long term, this would just train people to ignore those popups. Or to use a patched browser.

There is simply no way to suppress content as long as there's enough demand. Somebody's always going to find a way to deliver. That's even true for really illegal stuff like drugs, copyright infringement or child abuse material, but so much more for content which is legal.

Gitlab CI can build a docker image whenever you push code to your repo, and host said image in the builtin docker registry.

It's not a replacement for Docker, but a very useful companion.

> "How do you stop people obtaining it and using it through their buddies on the internet" - quite simply, by telling them they'd go to jail, or get a hefty fine, for doing that.

That method does not work very well for e.g. weed.

Solo SaaS app dev here. I found Sentry[1] to be the most valuable tool for monitoring what's going on inside my (Django/React) app. Sentry catches every exception/error in front- and backend, then collects and aggregates them, so I get a single ticket/notification for every type of issue, instead of thousands of those for every instance of the same problem.

For me, that's much simpler than trying to log each error and analyze the log later on. I still create application logs, but only read them if I need more information about a problem logged by Sentry (most of the time I don't need that at all, because Sentry collects a lot of context already).

Another plus for Sentry is that it can be self-hosted, which makes GDPR compliance a little bit easier.

Besides that, I use Monitor Scout[2] for checking that my app is still up, and fail2ban[3] to get rid of script kiddies trying to brute-force passwords and stuff.

[1] https://sentry.io/ [2] https://www.monitorscout.com [3] https://www.fail2ban.org/

I drive A8 (Stuttgart - Munich) and A9 (Nuremberg - Munich) regularly and don't see much to complain about. Compare that to A5 here in southwest and you see what I mean...

Anyway, if Saxony really has better Autobahns than Bavaria, I need to go there soon ;) Any specific recommendations?

It should be noted that not all Autobahns are equally well built and maintained. Even though they are called "Bundesautobahn" (federal highway), it's actually the states who are responsible for construction and maintenance. Some do a good job with that, others not so much.

For the best driving experience I'd recommend Bavaria. They have well maintained roads and less congestion, also only few speed limits. Avoid Baden-Württemberg and especially the Stuttgart area, unless you really like traffic jams.

Here's a map of Autobahn sections without speed limit: http://autobahnspeedhunter.de/routes_de/

But does it really have to be that difficult? It's absolutely possible to build a system where you can deploy a docker container with a single click and host your own content on that. Add federation into the mix, and you'll get some kind of meta-Youtube or -Bandcamp, comprised of thousands of individual instances, which do not even need to be on the same hosting service.

The blogosphere was similar to that, before everyone gave up and went to Facebook.

Those services do not necessarily need to be publicly accessible. Think of a federated network of private servers with closed user groups, which allow to share stuff easily with selected users on other servers. The directive would probably not even apply to this, but even if it does, it would be pretty hard to go after you, ay long as you don't share critical material with people you don't know.

You'd have to audit the source code first, though, which is not a trivial thing to do.

Any plans for a web frontend? Letting my mobile remind me of things based on location is something I wanted to have for a long time, but typing stuff and organizing things is much more comfortable with a real screen + keyboard.

A better example would be a Wordpress installation. Hello World means skipping much of the important stuff, like storage and persistence.

As a bonus, show how to use Gitlab for deploying and managing the app. Gitlab + Kubernetes could be the holy grail for modern, self-hosted development, however a good, complete tutorial/documentation is very hard to come by. One has to pick the pieces from a lot of different places with sometimes conflicting information.

I'd happily pay 100 Euros for such a course.

Not open source per OSI criteria, however they claim the source is available and can be inspected:

https://help.vivaldi.com/article/is-vivaldi-open-source/

Why that? A decent mobile site should be fine, there are quite some people (including me) who even prefer this over apps.