well there’s a firmware selector page, wherr you can request additional packages. maybe it can also be used for removing some?

but if you build it yourself you can do any changes you want, too

Don’t expect good Wi-Fi if you went with devboards like OpenWrt One.

why is that?

it could be easier though to make a slimmer custom build, without luci and other noncritical things

payment system: GNU Taler

but adoption is really, really slow

it already works in browsers. other clients would need to implement it themselves. I have no idea if this is viable with battery powered devices on a data cap

that’s disingenuous. you don’t need to feed google with money to support creators who want to be supported, they’ll have multiple channels for donations

but also you don’t need to pay google, or watch youtube at all, to participate in society.

an automatic ATM machine, no less!

I’m torn in how to feel about this. it was stupid to turn to a chatbot for things you know nothing about, as you then can’t even verify anything. and when you are a beginner, you probably shouldn’t start with SAS hardware either because it’s more complicated with the added enterprise features.

port 7657 is to the router console, do you really want that? if no, you need to check the tunnel manager for the port configured for your eepsite. its in the I2P Hidden Services list. the default entry uses port 7658

if you followed the advice of others to change the advanced config, you should probably revert this change because you don’t need it.

btw sometimes it may be useful to also expose the router console. but since that’s only for you, you don’t want others using it, configure an encrypted leaseset for it, which makes the router console’s eepsite invisible to others on the network. you should keep the router console’s authentication when you do this. https://geti2p.net/en/blog/post/2021/09/07/Level-Up-Encrypted-Leasesets

I think that’s misleading. I doubt OP wants to access the router console with this name.

I hate it that systemd is so quick to shut down sshd when shutting down the system. it does that in the very first “round”, while it could really just keep it running till the end…

to be fair, that’s because of codec licensing issues. fedora could not safely (legally) distribute some codecs for free

it starts to become comical that any time I see you around you are just stirring shit

my point is that at least most of your points don’t make sense.

then go ahead and explicitly define the type of every variable. rust wont stop you from doing that

well if you are recompiling thousands of crates with a single thread, for a simple webapp no less, then you are doing something wrong. multiple things, actually, I count 3.

you are better off without remote control systems like that

seems right. actually you were just not responding to the questions of anyone in this chain, but always responding with irrelevant things. and thanks for the downvotes! please bring some more.

and where does forgejo support federation for issues, PRs?

if the server is compromised, all the data it stores is at risk of getting drleted or modified. so I don’t think a VPS really solves the problem.