

Your Lemmy instance blocks the lemmygrad instance where IHave69XiBucks resides. My instance does too.
Your Lemmy instance blocks the lemmygrad instance where IHave69XiBucks resides. My instance does too.
You can look at the /boot/grub/grub.cfg file for details as to what each option is on the grub menu. It’s not the prettiest file though.
Search for menuentry
, that should be followed by the name of the entry and below details for what kernel and options it uses.
deleted by creator
There’s an option labeled Use AI to suggest tabs and a name for tab groups.
On 141 it’s listed in Settings under the General => Tabs section.
It changes browser.tabs.groups.smart.userEnabled.
Looking at it further, either option will disable it. Here’s the code that checks both values, https://github.com/mozilla-firefox/firefox/blob/FIREFOX-ANDROID_141_0_3_RELEASE/browser/components/tabbrowser/content/tabgroup-menu.js#L481
The ?ref
tag is from the Ghost blogging platform. https://forum.ghost.org/t/remove-ref-from-links-in-posts/37701/2
This is called “Outbound link tagging” - you can configure this on the Analytics Settings page (/ghost/#/settings/analytics)
And yeah, they do the same as GamingOnLinux with not including the content in the RSS feeds.
Forgot to give my opinion. The ref tag doesn’t bother me because it’s not giving any private information up, besides where I am from just like the referrer header does. I am kind of conflicted with the RSS feeds because I personally use them for many things, however I understand that these places need to advertise to make money (though I block ads too).
So I am not entirely sure. I did find the code for it however if you want to take a look.
In Firefox it uses the variable for the neqo library, which is the the Mozilla Firefox implementation of QUIC in Rust.
code:
let mut params = ConnectionParameters::default()
.versions(quic_version, version_list)
.cc_algorithm(cc_algorithm)
.max_data(max_data)
.max_stream_data(StreamType::BiDi, false, max_stream_data)
.grease(static_prefs::pref!("security.tls.grease_http3_enable"))
.sni_slicing(static_prefs::pref!("network.http.http3.sni-slicing"))
.idle_timeout(Duration::from_secs(idle_timeout.into()))
// Disabled on OpenBSD. See <https://bugzilla.mozilla.org/show_bug.cgi?id=1952304>.
.pmtud_iface_mtu(cfg!(not(target_os = "openbsd")))
// MLKEM support is configured further below. By default, disable it.
.mlkem(false);
In the neqo library it’s used here: https://github.com/mozilla/neqo/blob/9e52e922343609dba5171c0adb869cff7bd8d3a0/neqo-transport/src/crypto.rs#L1594
code:
let written = if sni_slicing && offset == 0 {
if let Some(sni) = find_sni(data) {
// Cut the crypto data in two at the midpoint of the SNI and swap the chunks.
let mid = sni.start + (sni.end - sni.start) / 2;
let (left, right) = data.split_at(mid);
// Truncate the chunks so we can fit them into roughly evenly-filled packets.
let packets_needed = data.len().div_ceil(builder.limit());
let limit = data.len() / packets_needed;
let ((left_offset, left), (right_offset, right)) =
limit_chunks((offset, left), (offset + mid as u64, right), limit);
(
write_chunk(right_offset, right, builder),
write_chunk(left_offset, left, builder),
)
} else {
// No SNI found, write the entire data.
(write_chunk(offset, data, builder), None)
}
} else {
// SNI slicing disabled or data not at offset 0, write the entire data.
(write_chunk(offset, data, builder), None)
};
I am looking forward to the new homestead. Also the new elite specs look interesting, can’t wait until we hear more.
I’m not sure if you know, you can craft and use two Conflux. The new Skimmer masteries have me interested as well!
It’s probably this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1955112
It’s a bug specifically on Wayland.
Try grabbing the tab and moving it and letting go, you don’t have to move it’s tab slot.
Looking at the changes lists many Wayland patches: https://github.com/GloriousEggroll/proton-ge-custom/tree/master/patches/wine-hotfixes/pending/wine-wayland
Searching through that list for “cursor” returned 3 results.
Here’s the pull requests on the WINE HQ GitLab.
From the Nobara changelog: https://nobaraproject.org/category/changelog/
plasma-discover and gnome-software have both now been replaced with flatpost. Flatpost is a new in-house developed one-stop shop for flatpaks. It is able to handle installation, removal, upgrading, and permissions of flatpaks as well as flatpak repository management. You should find it provides all of the same permission toggles as flatseal. It is a simple application built on python and gtk, and is meant to be a desktop environment agnostic solution (meaning it should run in any DE). We did this because while we only support Gnome and KDE, we understand users still want to install their own environments and will do so regardless of whether or not it’s supported. If they are going to do that, again we prefer users to install flatpaks where possible for their software needs, and not all environments have a flatpak shop. For example if I’m using hyprland or labwc, now I have a shop I can use with them: https://github.com/GloriousEggroll/flatpost. Users can still manually install plasma-discover or gnome-software if they prefer.
Looks like someone asked Ethan about posting to Lemmy, and they replied “Thanks for sharing – adding it to the list of places to post!”.
Unfortunately that’s one area I am bad with, I tend to use reverse_proxy for most such as Baikal running with the ckulka/baikal Docker image (which runs Nginx or Apache), otherwise I only static sites.
I’d start by looking at Baikal’s config for Apache and Nginx, https://sabre.io/baikal/install/ and comparing to the directives for Caddy, https://caddyserver.com/docs/caddyfile/directives and
Since it uses PHP, it will need that, https://caddyserver.com/docs/caddyfile/patterns#php
Upon my searches I came across this, it talks about running Baikal with Caddy specifically. https://github.com/caddyserver/caddy/issues/497
I hope that this provided some helpful directions.
I use Caddy for this. I’ll leave links to the documentation as well as a few examples.
Here’s the documentation for wildcard certs. https://caddyserver.com/docs/automatic-https#wildcard-certificates
Here’s how you add DNS providers to Caddy without Docker. https://caddy.community/t/how-to-use-dns-provider-modules-in-caddy-2/8148
Here’s how you do it with Docker. https://github.com/docker-library/docs/tree/master/caddy#adding-custom-caddy-modules
Look for the DNS provider in this repository first. https://github.com/caddy-dns
Here’s documentation about using environment variables. https://caddyserver.com/docs/caddyfile/concepts#environment-variables
A few examples of Dockerfiles. These will build Caddy with DNS support.
FROM caddy:2-builder AS builder
RUN xcaddy build --with github.com/caddy-dns/duckdns
FROM caddy:2
COPY --from=builder /usr/bin/caddy /usr/bin/caddy
FROM caddy:2-builder AS builder
RUN xcaddy build --with github.com/caddy-dns/cloudflare
FROM caddy:2
COPY --from=builder /usr/bin/caddy /usr/bin/caddy
FROM caddy:2-builder AS builder
RUN xcaddy build --with github.com/caddy-dns/porkbun
FROM caddy:2
COPY --from=builder /usr/bin/caddy /usr/bin/caddy
This is what to add the the Caddyfile, I’ve used these in the examples that follow this section. You can look at the repository for the DNS provider to see how to configure it for example.
https://github.com/caddy-dns/cloudflare?tab=readme-ov-file#caddyfile-examples
tls {
dns duckdns {env.DUCKDNS_API_TOKEN}
}
https://github.com/caddy-dns/cloudflare?tab=readme-ov-file#caddyfile-examples Dual-key
tls {
dns cloudflare {
zone_token {env.CF_ZONE_TOKEN}
api_token {env.CF_API_TOKEN}
}
}
Single-key
tls {
dns cloudflare {env.CF_API_TOKEN}
}
https://github.com/caddy-dns/porkbun?tab=readme-ov-file#config-examples Global
{
acme_dns porkbun {
api_key {env.PORKBUN_API_KEY}
api_secret_key {env.PORKBUN_API_SECRET_KEY}
}
}
or per site
tls {
dns porkbun {
api_key {env.PORKBUN_API_KEY}
api_secret_key {env.PORKBUN_API_SECRET_KEY}
}
}
And finally the Caddyfile examples.
Here’s how you do it with DuckDNS.
*.example.org {
tls {
dns duckdns {$DUCKDNS_TOKEN}
}
@hass host home-assistant.example.org
handle @hass {
reverse_proxy home-assistant:8123
}
}
Also you can use environment variables like this.
*.{$DOMAIN} {
tls {
dns duckdns {$DUCKDNS_TOKEN}
}
@hass host home-assistant.{$DOMAIN}
handle @hass {
reverse_proxy home-assistant:8123
}
}
*.{$DOMAIN} {
tls {
dns cloudflare {env.CF_API_TOKEN}
}
@hass host home-assistant.{$DOMAIN}
handle @hass {
reverse_proxy home-assistant:8123
}
}
*.{$DOMAIN} {
tls {
dns porkbun {
api_key {env.PORKBUN_API_KEY}
api_secret_key {env.PORKBUN_API_SECRET_KEY}
}
}
@hass host home-assistant.{$DOMAIN}
handle @hass {
reverse_proxy home-assistant:8123
}
}
Retroid Pocket Official(@Retroid0fficial) posted
10:21 AM ET · Feb 13, 2025 · 67.1K Views
It can be used as a VPN router, any VM that needs a VPN can be connected to a network bridge that is forward through the VPN. This could also be done on the primary router and a VLAN.
Thanks! Here they are listed below.
Oops, looks like that’s the wrong URL. I found it on Hacker News, here’s the post https://news.ycombinator.com/item?id=42431065 https://hostyourgif.live/
It says no such command found.
Make sure you use a back slash and not a forward slash. oobe\bypassnro
Try contacting the Forgejo admin, they can enable the HTTP meta refresh challenge, though it does have a higher false positive rate. https://anubis.techaro.lol/docs/admin/configuration/challenges/metarefresh