Ephera

I believe, Icecast ticks at least some of your criteria. It’s been around since forever, so it’s probably the most stable option and even a Pi1 is likely overkill for it. No idea how it holds up in terms of UI, app and Docker, though.

They do have a mirror on GitHub, but the main repo is on a self-hosted GitLab.

You’d have to rewrite the Git history to pseudonomize the author, which yes, is pretty bad, but I don’t see why you’d need to remove the code, unless they genuinely checked in their home address or such.

It’s a Linux concept. Basically, imagine you could have a Windows 11 PC with the Windows XP GUI or with the macOS GUI. In Linux, these kinds of different GUIs are just desktop environments, which you can install as you see fit.
Conversely, you can also have an OS without a desktop environment, which is basically what’s used on Linux server PCs.

Yeah, I don’t like when corporations put stuff like that into their ToS, but at the same time, I 100% understand why every open-source license under the sun has it. You’re giving it away for free, so you don’t want people to sue for more than you’re providing for free.

Mastodon.social is currently very much in the latter camp of giving things away for free. I also understand that a service is yet another beast than a piece of software, since they hold your personal data and may leak/sell it. But yeah, at this point in time, I wouldn’t want someone to be able to sue Mastodon.social out of existence. I guess, it depends a lot on how it’s formulated in the end…

It should be noted that theoretically, we don’t know how this external API is implemented. The vast majority of APIs are REST APIs and with REST APIs, there’s a decent chance that you can download an OpenAPI definition from the server which provides the API.

REST APIs are basically APIs which use HTTP(S) for transport and then there’s some specific rules how the API should be designed. Often times, these rules are not strictly followed and people still refer to such an API as “REST”, because they assume that any HTTP API is a REST API. But yeah, similarly the guides you’ll find will likely also work with general HTTP APIs.

Sounds to me like they’re not trying to create a website for now, but rather just process some data, which they can later display in a static webpage.

So, I’m guessing something like this:

+--------+     +---------+     +----------+
| Static |     | Their   |     | External |
| Web    |---->| Own     |---->| API      |
| Page   |     | Backend |     |          |
+--------+     +---------+     +----------+

But yes, unless there’s a lot of data to crunch, the design one would usually go for is rather:

+-----------+     +----------+
| *Dynamic* |     | External |
| Web       |---->| API      |
| Page      |     |          |
+-----------+     +----------+

So, the data calculations would happen in the user’s browser. You would still need some hosting for that webpage, but there’s lots of free services to put a simple webpage up.

And yes, when you go with that latter design, then JavaScript would be the typical choice. It’s still possible to do it with Rust, using WebAssembly (e.g. a colleague of mine has built a small statistics webpage which gets data directly from GitHub, using the Leptos framework), but it is definitely the less beaten path.

Having said all that, frankly, fuck the usual way of doing things. If you’re comfortable with Hugo for frontend work, then I think it’s legit to build a little backend to take over the dynamic part. Better to build a useful project and learn something than to get stuck trying to learn the ‘correct’ path of doing it. Especially if you’d rather learn about Rust than JS.

I’ve never used Facebook, but I’ve seen people say that Friendica is quite similar to Facebook (in case you care about that).

Yeah, the wording is confusing. A long time ago, there was no paid software, there was only software where you got the source code and other software where e.g. it was pre-installed on some hardware and the manufacturer didn’t want to give the source code.

In that time, a whole movement started fighting for software freedom, so they called their software “free”.

https://join-lemmy.org/ can help you find an instance based on your interests.

If they couldn’t find/trust additional admins, I don’t see how they could’ve handed it off entirely…

I don’t have much experience with IPv6 yet either, but as I understand, the primary benefit is that you can get rid of a lot of the crappiness of IPv4, which you might just deem ‘normal’ at this point, like NAT and DHCP. It does happen quite a bit, for example, that we’d like a unique identifier for a host, but with IPv4, you need to store a separate UUID to accomplish that.

Original link (in Spanish): https://www.xataka.com/servicios/foros-internet-estan-desapareciendo-porque-ahora-todo-reddit-discord-eso-preocupante

Well, any software needs to include a license of some form, if you want it to be usable by others. But if it’s not an open-source or libre license, then it’s a proprietary license. That’s not necessarily a bad thing. At that point, it depends on what’s actually written into the license. But it’s also not a good thing, as you miss out on various open-source benefits due to there being no proven legal compatibility with open-source licenses. Well, and if I remember correctly, FUTO’s license actively prohibits reuse of the code anyways.

I’m not sure, I understand the question, because there’s tons of languages that are basically just a superset of another, such as C++ for C, TypeScript for JavaScript, Crystal for Ruby. Heck, the whole family of LISP languages kind of matches your question, because they all use most of the syntax of LISP.

I expect Rust to be inevitable in embedded development, but yeah, that space moves slow, so give it another ten years or so. I will say that embedded is practically jumping on Rust, compared to how glacially it normally moves. You’ve got big vendors committing to offering Rust APIs, because many of their customers just don’t want to code C/C++ anymore.

There’s no real mobile app for it, is kind of my personal main reason why I didn’t pick it up…

Fine, sure, but to pretend that a language from half a century ago is the be-all and end-all of human wisdom, is ridiculous. The field is progressing, so on average newer languages improve compared to old ones.

Hmm, I don’t know anything about Whoogle, but from other privacy-conscious search engines, I would expect it to work when you use that URL in your bookmark.

Three things I can imagine:

• Something in your hosting stack strips the URL parameters, like maybe your reverse proxy, if you use one. You might be able to see in the Whoogle or web server logs, which URLs actually reach it. Might need to set it to debug/trace logging.
• Maybe there’s a flag in the Whoogle configuration you need to enable to accept these preference URLs.
• It’s a bug in that Whoogle version.

If you’ve got specific accounts you want to follow, you can get an RSS feed containing their public posts.

In terms of native clients, the closest such feature I know of, is that Fedilab (for Android) can remember your position in the timeline, so that you can resume reading.
If you primarily use one timeline, then you wouldn’t re-encounter already read posts, because they’re in the past from the remembered position.
I have to say, though, that it’s not the most reliable feature in the world…

I don’t know, if there’s any hosted instances of it, or how mature it is, but one of the Lemmy devs has experimented with using the frontend of phpBB (basically the software for old-school forums) with a Lemmy backend: !lemmybb@lemmy.ml

To my knowledge, they had some pretty quick successes with it and one might be able to just slap this onto a server right now…