[-] cyberwolfie@lemmy.ml 3 points 9 months ago

It is fairly recent, as the solo dev of DivestOS and its applications (including Mull and Mulch) stopped development. I moved to Fennec for now.

[-] cyberwolfie@lemmy.ml 3 points 10 months ago

That is also my understanding. It has some ventilation in the back that helps with this.

[-] cyberwolfie@lemmy.ml 3 points 10 months ago

I think this is exactly what happened to spotify wrapped this year - instead of doing the data analysis, they tried to have an llm/rag agent do it - and it’s hallucinating.

Interesting - I don't use Spotify anymore, but I overheard a conversation on the train yesterday where some teens were complaining about the results being super weird, and they couldn't recognize themselves in it at all. It seems really strange to me to use LLMs for this purpose, perhaps with the exception of coming up with different ways of formulating the summary sentences so that it feels more unique. Showing the most played songs and artists is not really a difficult analysis task that does not require any machine learning. Unless it does something completely different over the past two years since I got my last one...

[-] cyberwolfie@lemmy.ml 3 points 11 months ago

I use ledger. I have not automated so much outside of autocomplete macros in my text editor, but it doesnt't take too much time and forces me to look over my spend, so I like it. I will eventually attempt to build some kind of Dash-application for visualisation of the output, but have only started on the parsers so far.

[-] cyberwolfie@lemmy.ml 3 points 1 year ago

Are you me? Except I use FreeTube instead of Piped. I am so happy with this solution. Years of discontent of watching services going through the enshittification cycle... everything just becoming so underwhelming. This has given me back freedom over my own media consumption. No ads. No endless scrolling through bullshit content. Just a nicely personally curated selection of movies and TV shows (on Jellyfin) and an ad-free YouTube-experience with sponsorblock and dearrow enabled, and blocking of live chats and shorts.

[-] cyberwolfie@lemmy.ml 3 points 2 years ago

Just keep in mind that security through obscurity is not considered secure in itself.

Do you consider it to not be a helpful measure to take at all?

I have fail2ban configured - since it is reading from the auth.log, I guess I would not have to make any changes to the configuration there to have it work with a new port?

[-] cyberwolfie@lemmy.ml 3 points 2 years ago

Yes that’s the right way to block root login. An added filter you can use the ‘match’ config expression to filter logins even further.

Not sure what you meant about the 'match' config expressions here. Could you elaborate a bit further?

If you’re on the open network, your connection will be heavily hit with login attempts. That is normal. But using another service like Fail2Ban will stop repeated hits to your host.

Hehe, yeah, I've noticed... The reason I get a little anxious whether I did this correctly, is that 95% of the login attempts are to root, so I want to make sure it is disabled. I have set up Fail2Ban, but I am using default settings, which may be a bit laxer than they need?

I've also been advised and considered moving to ssh keys, but I have not gotten to that yet.

Ssh listens on port 22, as soon as a connection is made the host moves the connection to another port to free up 22 for other new connections.

Makes sense. One question that comes from this is: is it possible to disable that? I would never need two ssh-logins at the same time on my server. And the second question is what I asked above regarding whether I should change the port ssh listens to in order to reduce unwanted malicious login attempts?

[-] cyberwolfie@lemmy.ml 3 points 2 years ago

Yes, this is something I did when setting up the server some time ago, and as a step in the process I rebooted the system after changing the config.

[-] cyberwolfie@lemmy.ml 3 points 2 years ago

Ok, thanks - so if I understand correctly then, it is listening on port 22 as a default, and not accepting traffic on any port.

That brings of the question: wouldn't I be better off changing the SSH-port? And is that so easy as to uncomment the #Port 22 line in the config file and changing the port number to something random, and saving that somewhere? Would I then be able to connect by running ssh myuser@mydomain.com:, or would I need to do anything else to successfully connect?

[-] cyberwolfie@lemmy.ml 3 points 2 years ago

Don’t you love when you give in and go to get help for something and you can no longer reproduce it after you ask?

It's almost like it's a law of nature...

[-] cyberwolfie@lemmy.ml 3 points 2 years ago

That looks very similar to mine, except I don't have AAC and aptX. I guess the WH1000MX5 only supports SDC and LDAC? As far as I know, I need to use the Headset Head Unit to get microphone input. After a system update some time back, it would switch automatically if I e.g. was on a Signal call. Prior to this, I would have to switch manually to get microphone input.

By the way, I am not entirely sure if I am running PulseAudio or PipeWire, as I get the confusing output below, but it seems to be PulseAudio. Is it likely to improve things if I were to switch to PipeWire?

$ pactl info | grep "Server Name"
Server Name: PulseAudio (on PipeWire 0.3.80)

As for my Windows issue, it seems LDAC is not natively supported in Windows 10, so I guess it is using SDC. Could my problems simply be that I am trying to stream a too high bitrate? I will need to recheck my settings for stream quality.

[-] cyberwolfie@lemmy.ml 3 points 2 years ago

Agreed. I made the switch after Mendeley pushed their online manager with only a new limited desktop client, which was awful. Couldn't believe I hadn't gone with Zotero in the first place. Originally only used for my thesis, now I use for work and personal interests as well.

view more: ‹ prev next ›

cyberwolfie

joined 2 years ago