flatpak please
148 karma · joined March 3, 2018
The "better" journals are listed in JCR. Nearly 40% of them have impact factor less than 1, it means that on average papers in them are cited less than 1 times.
Conclusion: even in better journals, the average paper is rarely cited at all, which means that definitely the public has rarely heard of it or found it useful.
Check https://apex.oracle.com/ which does that.
The best arguments for a long-term mail storing solution - it keeps your emails and all your mail settings, in a form that is truly portable, so that you can easily move it from computer to computer
I am trusting it with 22 GB of emails (many tens of thousands of emails) organized in many folders.
You can have it connected to many online mail services, so it will sync (and keep an offline copy of your mail) and keep all of them separate. Or, you can configure it to sort all your email in a single place and folder hierarchy.
You can have various types of filters, separately per mail account.
If you are right handed, and have a practice to write the joins in the direction one->many (or person->children, or in the opposite direction of a foreign key) then you will always write the join as:
from person join children
Then, if you are not a beginner and know a bit about nulls and their side-effects, the best thing that you can do to prevent the risk of missing data is:
from person left join children
Why? Because this will help so that you will never miss those persons that do not have children.
So, depending on the type of the application, it may be the case that outer joins are nearly always needed and it maybe be a part of quality assurance policies to always do a left join, so that most queries are easily readable by most of the team.
If you are left handed, then perhaps you will write the same query as:
from children right join person
full outer join is not needed at all if you have enforced referential integrity everywhere - you will only need a left (or right) outer join (depending on the left-to-right or right-to-left reading preference)
in databases that do not have referential integrity enforced on all true foreign keys, full outer join will probably be the only right type of join. Otherwise, you will have problems with many scenarios.
ACM has an authorizer service that allows you as an author, to publish special links on your personal website, that will offer all visitors of your personal web-site free downloads of your papers.
Those who are interested in your paper don't need an account, they just need to click on the special links published on your website and the paper will be free to download in PDF.
Some conferences are institutions, have a formal organization that stands behind them and it is well organized so has some of these costs figured out and planned well in advance. Many are not. Many conferences are organized by different institutions each year, and are organized in turns by the hosting institution at locally available venues.
Imagine a small conference organized by a small department and it's total budget: - 100 presenters * $500 registration + 100 attendees * $100 registration = $60000
You need a venue. Many departments do not have resources to organize conferences in a presentable manner (lack of space, lack of rooms/halls). So you need a venue. Plus if the conference is in a nice venue, for a cheaper price - it will certainly be attended more.
Let's say that you were lucky and that some hotel accepted to be exclusive venue and they offered all of their equipment and halls, if at least 50 participants decided to book a room for the duration of the entire conference and there were 50 such participants. That way, you don't have to rent the hotel's halls and their projectors/laptops/screens/microphones.
You will still need to pay for this:
- costs to get respectable keynote lecturers and pay for their travel fees, room, meals, etc.
- organizing teams costs (even if they volunteer their time, they still have traveling expenses to visit the venue at least several times and organize local issues)
- hosting for a dedicated web-site for many years to come + web designer to support it 24/7 during the call for papers and during the conference
- print/publish the proceedings + editor
- venue for either the opening or the closing ceremony or some joint excursion or museum visit or all of these if you want to leave an impressiong that you are a host that wants to pamper their guests (if you don't pay for at least some of these, most people will not come next year, as the point of the event is to be a socializing trigger, and socialization always happens in the margins of the conference, at these social events, so the whole point of the conference will be lost if you don't take care for at least several such events)
- at least 2/3 photographers to cover social events and parallel sessions
- finger food / coffee / drinks / even water during breaks, maybe lunch for all participants
- banners, badges, posters, ...
I have organized an international conference and I can say that this is just the surface. If you organize an IT conference, you need to take into account that each participant will have at least 2 online devices, maybe more. So you will need wifi access points and routers capable of peaks in new wifi associations ranging from 200-300 per minute, or more. You will need a lot of electricity cables and plugs, power convereters etc. Most hotels doing small gatherings for 100-200 persons, are in fact organized to accomodate weddings and not IT professionals and their net streaming needs.
Do you own total, depending on wherever you are. In some countries this will cost much more than the budget, in some less so their might be something left to pay the organizers and even volunteers for their effort. Not much, but at least something so they do not avoid you when you decide to organize another conference in two years.
- check lists as todo lists
- daily log
- drafting slides for presentations (using export to Presentation option and S5 option)
Primary way of syncing to other devices - shared nextcloud folder.
Pro: plain text files - can be edited by any available text editor in case I want to edit notes on an unsupported devices.
Cons: I don't like when it automatically creates notes for all phrases written in CamelCase. It is a wiki, but i don't use it as a true wiki, but as a bunch of notes.
I use DBeaver for nearly everything SQL. It is also open-source.
Create a New Database connection, choose CSV, choose the folder with the CSV files, and you will get a database connection to a "database" where each CSV file is a table.
"The group found that pass rates in introductory programming courses appear to average about 75%; that there is some evidence that they sit at the low end of the range of pass rates in introductory STEM courses; and that pass rates both in introductory programming and in other introductory STEM courses appear to have remained fairly stable over the past five years. All of these findings must be regarded with some caution, for reasons that are explained in the paper"
Here's a compelling irrefutable argument.
Let's start the discussion from a couple of scenarios. These scenarios are not the definitive and complete set of use-cases, but are enough to prove a point.
Scenario 1: User manually searches for a song and clicks play. Again the following day. Again and again for a couple of weeks/months. The user forgets about the song after that period.
Scenario 2: User creates a playlist and clicks play. Then uses that same playlist again, and again and again for years. Alterantive scenario: users searches for a published album/compilation and plays that playlist again and again for years.
Scenario 3: Streaming service generates a new generic infinite playlist every day, based on a biased algorithm that upvotes some artists and downvotes some other artists. E.g. Playlist called - Discover Daily/Weekly.
Scenario 4. Streaming service generates a new generic infinite playlist every day, but personalized to the users taste and interests, again based on a biased algorithm that upvotes some artists and downvotes some other artists. E.g. Playlist called - Recommended for you today.
Scenario 5. User hits random play and a truly random algorithm decides what will be played next, no matter of musical style, language, culture or any other aspect. Truly random, no biases whatsoever.
So I will argue why not all streams are equal or should not be treated equal.
The difference is the specificity of intent. Whether the user wished to listen to some specific song, or if the user was force-fed some song. For the initial discussion I am assuming force-feeding, later I will discuss alternative scenarios (clicking skip).
In scenario 1 and 2 there is intent from the user what should be streamed, and this means that the user is interested in the music to be streamed. It can not be refuted that the authors of that specific song should be paid for the stream.
In scenario 3 and 4, the user just wishes to have something making noise, not anything specific, but not random. This is fine, if the user is satisfied, but the problem is all algorithms have biases. If the algorithm favors the most popular authors, and the user could be satisfied with anything in the same style and tempo without preferences, than the streaming service is not fair to the authors who are less popular and never gives them a standing chance to compete. This creates a boosting effect so that the most popular become force-fed to the audience involuntarily and they become even more popular. This is a well-known side-effect in all platforms that use popularity as ranking or rating metric. So here, not all streams can be considered equal, since some had higher probability to be present in the playlist due to inherent algorithm biases.
Scenario 5 is the only scenario where the user is force-fed music, but in a manner that is irrefutably unbiased and irrefutably fair to all authors and songs. In such a scenario all get a chance and all such streams are equal. Unfortunately, users that would prefer such a scenario do not exist. Nobody would endure the torture of a truly random playlist for more than 3 songs.
So we have use cases where the users know what they want, and use-cases where the users don't know what they want, but know what they don't want and the streaming service tries to guess what it is that they want next, without truly knowing.
How do the streaming services know what a user does not want? By measuring the % of the stream that went through. If the user managed to suffer only <5 secs before clicking skip, then that stream should not be counted at all towards payment to the musician. If it was 60 secs than it's a different case. If the song went through entirely it's even better. If the user streamed the entire song, and was actively using the app during the whole time than it is an indicator that the user appreciates the song even more than if a passive encounter occurred.
So they try to guess what to play next. With a biased recommender algorithm that tries to recommend what would be a good fit to play next, and as I said the algorithm might favor some musicians over others.
This is a hard problem and is always discussed at research conferences, both by researchers from the streaming services, and by independent researchers. The topics of bias, randomness, satisfaction are always present. Some authors are even using personality traits to discover the type of music that should be streamed next, which is a very very deep breach in user privacy. I imagine that some services might consider eaves dropping on their customers to evaluate if there is true interest and appreciation of the served content - whether the customer is eating, dancing, smiling, chatting, ..., having sex, during the stream. To gather as much data as possible on what is the context, to offer a better aligned next song (if you are a paying customer) of better aligned ads (if you are a non-paying customer).
This is why all streams must not be treated equal, and the streaming services must find a way to be as fair as possible towards musicians (having in mind that no-one likes a random playlist).
As this is a hard problem, I suspect that more and more services will divert their research towards automatically generated music, so nobody will care if the algorigths are fair and if the authors are paid. Music is most susceptible to this, as it is easy to generate music that sounds good enough to a fairly large audience without realizing it is all auto-generated.
Advertisers pay for a radio and tv service, not users, right?
My theory is that it is obviously because there is a way how to run Eclipse, without any issues and without the need of an officially tested debian package, so there is not huge demand.
If you are an active developer in the language that is used it will be easier, but you can do it even if you are not.
Example. Todays news here, is the latest release of Kodi. Debian does not have the most recent version. Some months ago I had an issue with the Kodi from the debian multimedia repo, so I decided to build it from source. It took me the better part of a day to have all the build tools installed and set-up everything, starting from zero. But in the end I had the latest Kodi running and it was running like that for 5 months and I even forget that I built it.
I managed to do that without even looking into the source code. In fact if you ask me what programming language is used to develop Kodi - I really don't know and don't remember.
Package maintainance is more about testing than about building.
So a list like this can serve as a guide in the process of choosing where to help. Just sort by number of users that use the software and go down the list until you find something that you use daily and where you would like to have the most recent version available and would volunteer your effort for 2-3 years (it is not really helpful if maintainers change every couple of months).
First, choose a package that really matters to you. On a daily basis. A package that you yourself would NEED to have it up2date the next day a new version is out.
Get the source deb and try to build it. Usually it's not very hard.
Then, try to do the same on all the debian variants (unstable, stable, ...)
If you succeed and the package works, you have the prerequisite competencies, at least as a beginner.
Then, these are some of the things that you will need to do, quite often.
Change the configuration of the package description so that you can build it with a later version of the source. For all variants of the distro.
Then try the same with the package dependencies, where those dependecies are not needed for other packages.
Then try to push it as close towards the latest source version, as you can without breaking stuff.
Once you do all that without issues and you are confident that you can use the version you built from source as a daily driver and you are not bothered by that, contact the original maintainer directly and offer help, sharing the details what you did as proof that you are competent enough.
If the maintainer is uncollaborative or unresponsive, put up your own repo for public use, and invite the public to install the package from your repo, so that the public will see some benefit and you will receive zillion of bug reports to further streghten your competence level.
I have been using it like that almost every day for 15 years now.