Deemo

joined 1 year ago
[–] Deemo@bookwormstory.social 2 points 3 weeks ago* (last edited 3 weeks ago)

I use the following with mobile version of YouTube in safari (not desktop version) on iPad 9.

Wiper adblock $1.99 one time payment (no subscription).

https://apps.apple.com/us/app/wipr/id1030595027

SponsorBlock $1.99 one time payment (no subscription).

https://apps.apple.com/us/app/sponsorblock-for-safari/id1573461917

[–] Deemo@bookwormstory.social 2 points 4 weeks ago

Percy Jackson

 

Edit: Kinda found a answer

Major versions of iOS are released annually. Apple significantly extended the cycle of updates for iOS-supported devices over the years. Usually, only the latest iOS release is supported by Apple. Starting with iOS 15, Apple started to support 2 major versions of iOS, for a short period of time.

https://endoflife.date/ios

Hi guys this might be a silly question, do ios and iPad OS devices have different number of years of major updates (think ios 16, 17, 18 etc) and years of security updates?

Or do devices that don't make the cut for the latest major update immediately loose access to security updates once a new incompatible major ios update is released?

2
submitted 2 months ago* (last edited 2 months ago) by Deemo@bookwormstory.social to c/selfhosted@lemmy.world
 

Hi guys for those of you that use pi-hole (or similar solutions like adguard home, etc) and wireguard how far away can you be from your wireguard/pi-hole server before latency becomes a major issue?

Also on a side note how many milliseconds of latency would you guys consider to be to slow?

Edit I meant dns latency sorry for not mentioning

[–] Deemo@bookwormstory.social 1 points 3 months ago

Again thanks for taking the time to help and explain this to me

[–] Deemo@bookwormstory.social 1 points 3 months ago

Yep this works

[–] Deemo@bookwormstory.social 1 points 3 months ago* (last edited 3 months ago) (3 children)

"origin=cloudsmith/caddy/stable";

Unable to parse Unattended-Upgrade::Allowed-Origins. An error occurred: not enough values to unpack (expected 2, got 1)


// Automatically upgrade packages from these (origin:archive) pairs
//
// Note that in Ubuntu security updates may pull in new dependencies
// from non-security sources (e.g. chromium). By allowing the release
// pocket these get automatically pulled in.
Unattended-Upgrade::Allowed-Origins {
        "${distro_id}:${distro_codename}";
        "${distro_id}:${distro_codename}-security";
        // Extended Security Maintenance; doesn't necessarily exist for
        // every release and this system may not have it installed, but if
        // available, the policy for updates is such that unattended-upgrades
        // should also install from here by default.
        "${distro_id}ESMApps:${distro_codename}-apps-security";
        "${distro_id}ESM:${distro_codename}-infra-security";
        "${distro_id}:${distro_codename}-updates";
//      "${distro_id}:${distro_codename}-proposed";
//      "${distro_id}:${distro_codename}-backports";
        "origin=cloudsmith/caddy/stable";
};

Edit:

Replacing 

"origin=cloudsmith/caddy/stable";

to

`"cloudsmith/caddy/stable:any-version";`

fixes error

I have no idea why ubuntu doesn't like the origin syntax

[–] Deemo@bookwormstory.social 1 points 3 months ago (5 children)

Firstly thank you so much for explaing this for me.

"origin=Zabbix,codename=${distro_codename}"; //Zabbix Agent repository

I tried using this as a template for caddy

 500 https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version/main arm64 Packages
     release o=cloudsmith/caddy/stable,a=any-version,n=any-version,l=source=none,c=main,b=arm64
     origin dl.cloudsmith.io

I assume origin is:

o=cloudsmith/caddy/stable

When adding this rule

"origin=cloudsmith/caddy/stable,codename=${distro_codename}"; //Caddy repository

I get this error

Unable to parse Unattended-Upgrade::Allowed-Origins.
An error occurred: not enough values to unpack (expected 2, got 1)
Traceback (most recent call last):

https://pastebin.com/raw/7gtkRw7c

When changing the syntax to:

"cloudsmith/caddy/stable:${distro_codename}"; // Caddy

The error goes away.

Any ideas?

11
unattended upgrades with caddy (bookwormstory.social)
submitted 3 months ago* (last edited 3 months ago) by Deemo@bookwormstory.social to c/selfhosted@lemmy.world
 

Edit: credit to exu@feditown.com

Assuming you installed caddy via Debian, Ubuntu, Raspbian method

https://caddyserver.com/docs/install#debian-ubuntu-raspbian

add "cloudsmith/caddy/stable:any-version"; to /etc/apt/apt.conf.d/50unattended-upgrades

Example:

// Automatically upgrade packages from these (origin:archive) pairs
//
// Note that in Ubuntu security updates may pull in new dependencies
// from non-security sources (e.g. chromium). By allowing the release
// pocket these get automatically pulled in.
Unattended-Upgrade::Allowed-Origins {
        "${distro_id}:${distro_codename}";
        "${distro_id}:${distro_codename}-security";
        // Extended Security Maintenance; doesn't necessarily exist for
        // every release and this system may not have it installed, but if
        // available, the policy for updates is such that unattended-upgrades
        // should also install from here by default.
        "${distro_id}ESMApps:${distro_codename}-apps-security";
        "${distro_id}ESM:${distro_codename}-infra-security";
        "${distro_id}:${distro_codename}-updates";
//      "${distro_id}:${distro_codename}-proposed";
//      "${distro_id}:${distro_codename}-backports";
        "cloudsmith/caddy/stable:any-version";
};

Link to comment chain (not sure how to add links in a federated way)

https://feditown.com/comment/1221458

https://bookwormstory.social/post/2100056/4136035

Origional post:

Hi guys anyone know how to use un attended upgrades with caddy.

I have ubuntu server 22.0.4.

The part that stumps me is caddy uses a external repository cloud Smith making ot difficult to setup.

I installed caddy via Debian, Ubuntu, Raspbian

https://caddyserver.com/docs/install#debian-ubuntu-raspbian

The closest example I could find to unattended upgrades with a external repo was this example using docker.

/etc/apt/apt.conf.d/50unattended-upgrades

"Docker:${distro_codename}";

https://blog.coffeebeans.at/archives/1299

I'm not sure if it's as simple as

/etc/apt/apt.conf.d/50unattended-upgrades

"Caddy:${distro_codename}";

Edit:

One more question affect would adding

APT::Unattended-Upgrade::Package-Blacklist "";

/etc/apt/apt.conf.d/20auto-upgrades

have?

Edit2:

I just removed this I only found this from google gemini (which probably isn't the best source of info)

APT::Unattended-Upgrade::Package-Blacklist "";
[–] Deemo@bookwormstory.social 1 points 4 months ago (1 children)

Update regarding virtual files has more quirks.

  • You cannot move files or folders. If you try nextcloud will simply copy the files to new destinaiton while not moving.
  • the nextcloud sync and virtual files refresh/update independently (a change may propigate to sync but not files and vice versa).

Also turns out the reason it was a github release was it is still in alpha 😅 .

[–] Deemo@bookwormstory.social 1 points 4 months ago (3 children)

Update the stable client does have proper virtual file sync.

Regarding the previous virtual file sync system (.nextcloud) you had to enable experimental features to get it. The latest stable just has both versions of syncing and I missed the obsious vfs sync option.

The only downside to the new system is there isn't a make file/folder available offline always option in the context menu (you can get around this by manually setting up synced folders but it is a little inconvient).

[–] Deemo@bookwormstory.social 1 points 4 months ago* (last edited 4 months ago)

Nextcloud desktop client 3.13.0

Edit 2:

You need to grab the release from https://github.com/nextcloud-releases/desktop/releases/tag/v3.13.0

Specifically the vfs version Nextcloud-3.13.0-macOS-vfs.pkg

brew doesn't really work

[–] Deemo@bookwormstory.social 1 points 4 months ago (5 children)

This is how it shows up for me on Nextcloud desktop client 3.13.0

[–] Deemo@bookwormstory.social 2 points 4 months ago

It sorta does. Nextcloud creates a list of placeholder files with a .nextcloud extension and when you open it nextcloud will auto download the realfile and open it.

[–] Deemo@bookwormstory.social 1 points 4 months ago (7 children)

Unfortunatly like syncthing nextcloud mac app also has the same file extension sync issue (they use .nextcloud).

 

Hi guys do you guys know any selfhosted cloud solution that has a combined sync and filestream option?

Context when you use seafile on macos there is seadrive (mounts external cloud like a drive) and seafile sync which syncs files to local folders. The problem is the two clients sort of act seperatly from one other (you cant make seadrive make files offline for instance neither can you preview files in seafile sync).

By contrast onedrive and google drive both have client apps which can sync on demand (file stream) and optionally make files available offline with a simple right click in context menu.

~~Side note I have tried nextcloud on mac but its experimental mount mode just keeps a placeholder .nextcloud file.~~

Edit:

Nextcloud does have proper virtual file sync. Only limitation is you can't make files availble offline via the context menu and instead need to set up manual folder syncs

Edit 2:

You need to grab the release from https://github.com/nextcloud-releases/desktop/releases/tag/v3.13.0

Specifically the vfs version Nextcloud-3.13.0-macOS-vfs.pkg

 

Edit 2: Fdroid Version 3.0 allows read only acess to files writing to files seems to not work

Edit: Tldr install version 3.0 from fdroid or github. Plastered version out of date.

Hi guys not sure if this is the right place to ask, but anyone having issues using the file browser integration for seafile?

The android app by itself seems to work but the files integration only seems to be broken.

By contrast the ios version of seafile the app and its files app integration both work with no issue. Additionally the webdav, browser, and mac apps (seadrive) have no issues.

Other context:

  • Running Seafile server 11.0.9 on Ubuntu 22.04.4 LTS using tailscale
  • Seafile android app version 2.3.7 running on Android 14
 

Hi guys I was wondering if there is a streamlined way to disable remote acess to a selfhosted service (say at a reverse proxy level) if a published security vunerability is present.

I know, ideally you want to keep all your selfhosted services up to date. However on certain selfhosted service auto updates may not be viable (due to major changes between updates) and you being unavailable 24/7 to respond to vunerabilities.

Curious on your thoughts and suggestions. So far the only middle ground I can find is realying on a vpn wireguard, tailscale, etc.

Page regarding homeassistant remote ui autodisable: https://www.nabucasa.com/config/remote/

view more: next ›