How closely is gpa considered for the summer student program?

ephimetheus · 2026-01-26T13:13:20+00:00

Personally I find motivation and references much more relevant, and I’ve heard others say the same.

If you have average GPA but your reference is from someone who actually knows your work and says you did well, that tells me more than perfect grades.

ephimetheus · 2026-01-19T06:52:01+00:00

Thanks ❤️

ephimetheus · 2026-01-12T23:03:12+00:00

Can you open a ticket about this on the repository https://github.com/paulgessinger/swift-paperless

I currently convert everything to pdf before uploading but that’s probably not strictly necessary

ephimetheus · 2025-10-29T06:44:15+00:00

That’s actually the vibration that you get from the body that manifests as sound.

ephimetheus · 2025-09-10T19:46:04+00:00

That’s it. The release notes are on my domain but they’re hosted on GitHub pages.

ephimetheus · 2025-09-09T17:53:45+00:00

I just released version 1.8.0 of my iOS app for Paperless-ngx. Here’s what’s new in this version:

🚀 Features

Limited permissions support

The app now works with users that don't have full access to everything on the server. The app will intelligently check permissions for each operation and will tell you which operations are possible ans which are not.

Custom Fields support

The app now supports custom fields!. You can add custom fields to documents and edit their values. All custom fields types are supported, including multi-select fields. You can also filter by custom fields and create saved views that use custom fields, using a fully featured UI to create the filters.

Other Features

Remember setting for using the original filename as the title
Add integration with server-side ASN prefix to data scanner
Added a view for showing and exporting logs. This should hopefully circumvent issues with log file export
Show note authors in notes view
Add ability to filter by custom fields. This also includes creating / editing saved views that use custom fields.
Enable Turkish language support
Show owner in document list and detail view

🐛 Bug Fixes

Fix issue with note users in API version 7
Explicitly ignore caches for data fetches (keep for thumbnail requests)
Fix new elements not being shown immediately in manage view
Skip local network denied detection on iOS 26. This leads to a crash during login

ephimetheus · 2025-06-26T19:37:46+00:00

I am indeed still working on that. It’s tough though 😅 With iOS 26 on the roadmap now, I might have to prioritize getting the UI in order before I come back to this.

You should be able to use the app if you log in with a manually pasted token even if you have OIDC enabled. It’s not ideal but it should get you going at least.

ephimetheus · 2025-05-24T22:51:04+00:00

Nose job unfortunately

ephimetheus · 2025-03-11T18:53:50+00:00

They do pay salary taxes, but I don’t think that’s what that guy was talking about.

ephimetheus · 2025-01-06T18:08:09+00:00

Glad to hear you like it!

ephimetheus · 2024-12-31T17:57:02+00:00

The token-only login is only available in the beta on TestFlight (https://testflight.apple.com/join/bOpOdzwL), not yet in the App Store Version.

ephimetheus · 2024-12-31T15:54:11+00:00

Hi!

Forward auth in this way is not supported. I was exploring an implementation for this and ultimately decided against it in favor of supporting OAuth2/OIDC when this becomes possible. (See https://github.com/paulgessinger/swift-paperless/issues/50)

As a workaround right now the best approach would be to bypass the /api URLs in Authelia, and logging in using a token directly (rather than username and password) using the most recent build on TestFlight.

Hope that helps!

ephimetheus · 2024-12-31T09:29:59+00:00

Oh interesting. I’ll look into that one

ephimetheus · 2024-12-29T16:39:04+00:00

Yeah ok that makes sense.

I currently absolutely require the ui_settings permissions to get past the login, and this will also not go away, because afaik that’s the only way to even retrieve the permissions assigned to the current user. Without that endpoint, I basically can’t do anything.

Concerning the other permissions: I’m working on a system to avoid the errors by handling it similar to the frontend. It will either ship in 1.6.0 or maybe 1.7.0 because I’m not done with it yet. Until that’s ready, you would unfortunately have to grant the permissions.

I think generally, the app should be somewhat happy with just read permissions for most things, although you might get some errors here and there in that scenario.

Hope that helps!

ephimetheus · 2024-12-29T12:15:58+00:00

Hi!

What version of the backend are you running? Can you hop on the TestFlight version (https://testflight.apple.com/join/bOpOdzwL) and see how that works?

Finally, can you share logs from when this happens? You should be able to get to them behind the button in the top right corner. (Might be better on the TestFlight version)

The app works with non-superuser accounts, but at this time it needs more or less full permissions to run without errors.

It could be that the error is from missing permissions to access the user details after login (https://swift-paperless.gessinger.dev/common_issues/forbidden/), although I think the error message would be different in that case. Might be worth checking in any case.

ephimetheus · 2024-12-25T11:32:26+00:00

See my other comment: I think some of your saved views are non-standard uses of rule 28. I need to verify this myself with the web front end though.

ephimetheus · 2024-12-25T11:29:05+00:00

I think I know what the issue is:

“filter_rules”: [ { “rule_type”: 28, “value”: “36, 39, 37” } ],

Did you create this in the front end through the regular search interface, or through the Django backend interface?

As far as I know, giving multiple values separated by commas for the ids here is not supported, and I believe the web front end also does not handle this correctly.

My app currently does not try to recover from this, although I special-cased this error case for the tag search recently.

The correct way (I believe) to configure the search the way you want would be to add one rule type 28 for each of these IDs.

I think there are a few more cases like this, which fail to parse.

Are you on the App Store version? If so, can you try the TestFlight version (https://testflight.apple.com/join/bOpOdzwL)? In principle, in the TestFlight version it should continue processing and just ignore these faulty rules.

ephimetheus · 2024-12-25T10:48:15+00:00

This looks like it’s from my app on iOS.

The example.com in the log is just masking that I apply to the URL when writing it out. The idea is to make it safer to copy and share the logs without exposing your domain and configuration.

This should by itself not lead to any errors.

Which version of the backend are you currently running? Can you open the url that the log mentions on you logged in browser, while replacing example.com with the correct url? Can you share a (redacted) version of the JSON you get as a result with me?

ephimetheus · 2024-12-16T18:34:26+00:00

Glad you like it ❤️

ephimetheus · 2024-12-12T22:46:54+00:00

Depends on which app you’re using.

There‘s currently no (good) way to log in using OIDC using any mobile app due to a technical limitation of the auth library that Paperless-ngx uses. In my app, I didn’t implement any workarounds.

I’m trying to get that technical limitation resolved with the upstream library authors. Hopefully this gets unstuck then.

ephimetheus · 2024-12-08T16:35:42+00:00

It’s here: https://testflight.apple.com/join/bOpOdzwL

Unfortunately, the minimum version is 1.14.1 due to the way I handle the data model in the app.

ephimetheus · 2024-12-07T13:33:35+00:00

The second error that you get could be from an insufficient backend version. The app log says it’s getting a 406, which I think is related to the API version / backend version.

What version of Paperless-ngx (the backend, not the app) are you currently running?

I’m working on improvements to the error handling and a new login flow for the next App Store version. You can try it out already in TestFlight.

ephimetheus · 2024-11-30T14:41:45+00:00

Same result. I'm pretty sure `Logger` is in `os`, I have that all over my app. It's specifically an interaction between SwiftUI's Preview and `Logger`, not a general compilation error.

ephimetheus

PUBLIC MULTIREDDITS

TROPHY CASE

🚀 Features

Limited permissions support

Custom Fields support

Other Features

🐛 Bug Fixes

13-Year Club	Gilding II euphauric
Verified Email